SAP ISP_POSTAL_CODE_CHECK Function Module for IS-M/SD: Check Correctness of PCd Data - Copy FM: POSTAL_CODE_CHECK









ISP_POSTAL_CODE_CHECK is a standard isp postal code 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: Check Correctness of PCd Data - Copy FM: POSTAL_CODE_CHECK 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 postal code check FM, simply by entering the name ISP_POSTAL_CODE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: JSS1
Program Name: SAPLJSS1
Main Program: SAPLJSS1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISP_POSTAL_CODE_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_POSTAL_CODE_CHECK'"IS-M/SD: Check Correctness of PCd Data - Copy FM: POSTAL_CODE_CHECK
EXPORTING
COUNTRY = "
* ONE_TIME_ACCOUNT = ' ' "Indicator for one-time transactions (one-time account)
* POSTAL_CODE = ' ' "Postal Code
* POSTAL_CODE_PO_BOX = ' ' "PO Box Postal Code
* PO_BOX = ' ' "
* REGION = ' ' "
* X_PLZ_STR_MUSS = ' ' "

IMPORTING
INFO_T005 = "
E_POSTAL_CODE = "Postal Code

EXCEPTIONS
NOT_VALID = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJSS1_001 IS-M/SD: DB Optimization
EXIT_SAPLJSS1_010 Find Street Using Short Text from Street File

IMPORTING Parameters details for ISP_POSTAL_CODE_CHECK

COUNTRY -

Data type: KNA1-LAND1
Optional: No
Call by Reference: No ( called with pass by value option)

ONE_TIME_ACCOUNT - Indicator for one-time transactions (one-time account)

Data type: T077D-XCPDS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POSTAL_CODE - Postal Code

Data type: KNA1-PSTLZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

POSTAL_CODE_PO_BOX - PO Box Postal Code

Data type: KNA1-PSTL2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PO_BOX -

Data type: KNA1-PFACH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

REGION -

Data type: KNA1-REGIO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PLZ_STR_MUSS -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_POSTAL_CODE_CHECK

INFO_T005 -

Data type: T005
Optional: No
Call by Reference: No ( called with pass by value option)

E_POSTAL_CODE - Postal Code

Data type: KNA1-PSTLZ
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_VALID - Check not successful

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISP_POSTAL_CODE_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_country  TYPE KNA1-LAND1, "   
lv_info_t005  TYPE T005, "   
lv_not_valid  TYPE T005, "   
lv_e_postal_code  TYPE KNA1-PSTLZ, "   
lv_one_time_account  TYPE T077D-XCPDS, "   SPACE
lv_postal_code  TYPE KNA1-PSTLZ, "   SPACE
lv_postal_code_po_box  TYPE KNA1-PSTL2, "   SPACE
lv_po_box  TYPE KNA1-PFACH, "   SPACE
lv_region  TYPE KNA1-REGIO, "   SPACE
lv_x_plz_str_muss  TYPE KNA1. "   SPACE

  CALL FUNCTION 'ISP_POSTAL_CODE_CHECK'  "IS-M/SD: Check Correctness of PCd Data - Copy FM: POSTAL_CODE_CHECK
    EXPORTING
         COUNTRY = lv_country
         ONE_TIME_ACCOUNT = lv_one_time_account
         POSTAL_CODE = lv_postal_code
         POSTAL_CODE_PO_BOX = lv_postal_code_po_box
         PO_BOX = lv_po_box
         REGION = lv_region
         X_PLZ_STR_MUSS = lv_x_plz_str_muss
    IMPORTING
         INFO_T005 = lv_info_t005
         E_POSTAL_CODE = lv_e_postal_code
    EXCEPTIONS
        NOT_VALID = 1
. " ISP_POSTAL_CODE_CHECK




ABAP code using 7.40 inline data declarations to call FM ISP_POSTAL_CODE_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 KNA1 INTO @DATA(ld_country).
 
 
 
"SELECT single PSTLZ FROM KNA1 INTO @DATA(ld_e_postal_code).
 
"SELECT single XCPDS FROM T077D INTO @DATA(ld_one_time_account).
DATA(ld_one_time_account) = ' '.
 
"SELECT single PSTLZ FROM KNA1 INTO @DATA(ld_postal_code).
DATA(ld_postal_code) = ' '.
 
"SELECT single PSTL2 FROM KNA1 INTO @DATA(ld_postal_code_po_box).
DATA(ld_postal_code_po_box) = ' '.
 
"SELECT single PFACH FROM KNA1 INTO @DATA(ld_po_box).
DATA(ld_po_box) = ' '.
 
"SELECT single REGIO FROM KNA1 INTO @DATA(ld_region).
DATA(ld_region) = ' '.
 
DATA(ld_x_plz_str_muss) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!