SAP ISP_PLZ_PLAUSI_CHECK Function Module for IS-M/SD: Plausibility Check if PCd Entered Is Possible for City
ISP_PLZ_PLAUSI_CHECK is a standard isp plz plausi check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Plausibility Check if PCd Entered Is Possible for City processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for isp plz plausi check FM, simply by entering the name ISP_PLZ_PLAUSI_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JSS2
Program Name: SAPLJSS2
Main Program: SAPLJSS2
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_PLZ_PLAUSI_CHECK pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ISP_PLZ_PLAUSI_CHECK'"IS-M/SD: Plausibility Check if PCd Entered Is Possible for City.
EXPORTING
LAND1 = "Country
ORTSNR_KEY = "
PLZ = "
EXCEPTIONS
PLZ_KONFLIKT = 1
IMPORTING Parameters details for ISP_PLZ_PLAUSI_CHECK
LAND1 - Country
Data type: JSTSTRPRO-LAND1Optional: No
Call by Reference: No ( called with pass by value option)
ORTSNR_KEY -
Data type: JSTSTRPRO-ALORTOptional: No
Call by Reference: No ( called with pass by value option)
PLZ -
Data type: JSTSTRPRO-PLZ_ZSTROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PLZ_KONFLIKT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_PLZ_PLAUSI_CHECK Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_land1 | TYPE JSTSTRPRO-LAND1, " | |||
| lv_plz_konflikt | TYPE JSTSTRPRO, " | |||
| lv_ortsnr_key | TYPE JSTSTRPRO-ALORT, " | |||
| lv_plz | TYPE JSTSTRPRO-PLZ_ZSTR. " |
|   CALL FUNCTION 'ISP_PLZ_PLAUSI_CHECK' "IS-M/SD: Plausibility Check if PCd Entered Is Possible for City |
| EXPORTING | ||
| LAND1 | = lv_land1 | |
| ORTSNR_KEY | = lv_ortsnr_key | |
| PLZ | = lv_plz | |
| EXCEPTIONS | ||
| PLZ_KONFLIKT = 1 | ||
| . " ISP_PLZ_PLAUSI_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISP_PLZ_PLAUSI_CHECK
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single LAND1 FROM JSTSTRPRO INTO @DATA(ld_land1). | ||||
| "SELECT single ALORT FROM JSTSTRPRO INTO @DATA(ld_ortsnr_key). | ||||
| "SELECT single PLZ_ZSTR FROM JSTSTRPRO INTO @DATA(ld_plz). | ||||
Search for further information about these or an SAP related objects