ISP_POSTCODE_CHECK SAP Function module - IS-M: Check Postal Code for Country with Specific Usage

ISP_POSTCODE_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISP_POSTCODE_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JSS2
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISP_POSTCODE_CHECK - ISP POSTCODE CHECK

CALL FUNCTION 'ISP_POSTCODE_CHECK' "IS-M: Check Postal Code for Country with Specific Usage
  EXPORTING
    land1 =                     " jstortpro-land1  Country
    loc_jytplzart =             " jytplzart
    postleitzahl =              " jstplzpro-plzneu
* CHANGING
*   gueltigab = CON_TIME_ZERO   " jstplzpro-gueltigab
*   gueltigbis = CON_TIME_INFINITY  " jstplzpro-gueltigbis
  EXCEPTIONS
    NO_SUCH_POSTCODE_FOUND = 1  "
    PLZART_FEHLT = 2            "
    PLZART_KONFLIKT = 3         "
    .  "  ISP_POSTCODE_CHECK

ABAP code example for Function Module ISP_POSTCODE_CHECK

The ABAP code below is a full code listing to execute function module ISP_POSTCODE_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

 

SELECT single GUELTIGAB 
  FROM JSTPLZPRO 
  INTO @DATA(ld_gueltigab).

 

SELECT single GUELTIGBIS 
  FROM JSTPLZPRO 
  INTO @DATA(ld_gueltigbis).

 

SELECT single LAND1 
  FROM JSTORTPRO 
  INTO @DATA(ld_land1).


DATA(ld_loc_jytplzart) = 'Check type of data required'.
 

SELECT single PLZNEU 
  FROM JSTPLZPRO 
  INTO @DATA(ld_postleitzahl).

.

CALL FUNCTION 'ISP_POSTCODE_CHECK'
  EXPORTING
    land1 =                      ld_land1
    loc_jytplzart =              ld_loc_jytplzart
    postleitzahl =               ld_postleitzahl
* CHANGING
*   gueltigab =                  ld_gueltigab
*   gueltigbis =                 ld_gueltigbis
  EXCEPTIONS
    NO_SUCH_POSTCODE_FOUND =     1
    PLZART_FEHLT =               2
    PLZART_KONFLIKT =            3
    .  "  ISP_POSTCODE_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_gueltigab
 
 TYPE JSTPLZPRO-GUELTIGAB ,
ld_land1
 
 TYPE JSTORTPRO-LAND1 ,
ld_gueltigbis
 
 TYPE JSTPLZPRO-GUELTIGBIS ,
ld_loc_jytplzart
 
 TYPE JYTPLZART ,
ld_postleitzahl
 
 TYPE JSTPLZPRO-PLZNEU .



SELECT single GUELTIGAB 
  FROM JSTPLZPRO 
  INTO ld_gueltigab.


SELECT single LAND1 
  FROM JSTORTPRO 
  INTO ld_land1.


SELECT single GUELTIGBIS 
  FROM JSTPLZPRO 
  INTO ld_gueltigbis.

ld_loc_jytplzart = 'Check type of data required'.

SELECT single PLZNEU 
  FROM JSTPLZPRO 
  INTO ld_postleitzahl.