SAP ISP_ADDRESS_EXTRACT Function Module for Extract Address Data









ISP_ADDRESS_EXTRACT is a standard isp address extract SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extract Address Data 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 address extract FM, simply by entering the name ISP_ADDRESS_EXTRACT 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_ADDRESS_EXTRACT 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_ADDRESS_EXTRACT'"Extract Address Data
EXPORTING
* DIALOG = JPSD_FALSE "
LAND = "
ORT = "
PLZ = "
STRASSE = "

IMPORTING
ADRDATA = "
ANSCHR_TYP = "
XFLG_DATA_CHANGED = "
XFLG_TOWN_CHANGED = "
XFLG_STREET_CHANGED = "

EXCEPTIONS
WRONG_INPUT = 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_ADDRESS_EXTRACT

DIALOG -

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

LAND -

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

ORT -

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

PLZ -

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

STRASSE -

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

EXPORTING Parameters details for ISP_ADDRESS_EXTRACT

ADRDATA -

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

ANSCHR_TYP -

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

XFLG_DATA_CHANGED -

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

XFLG_TOWN_CHANGED -

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

XFLG_STREET_CHANGED -

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

EXCEPTIONS details

WRONG_INPUT -

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

Copy and paste ABAP code example for ISP_ADDRESS_EXTRACT 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_dialog  TYPE JPSD_BOOLEAN, "   JPSD_FALSE
lv_adrdata  TYPE JKSI_ADDRESS, "   
lv_wrong_input  TYPE JKSI_ADDRESS, "   
lv_land  TYPE RJGSADR-LAND1, "   
lv_anschr_typ  TYPE JGTSADR-ERSTADR, "   
lv_ort  TYPE RJGSADR-ORT01, "   
lv_xflg_data_changed  TYPE JPSD_XFELD, "   
lv_plz  TYPE RJGSADR-PSTLZ, "   
lv_xflg_town_changed  TYPE JPSD_XFELD, "   
lv_strasse  TYPE RJGSADR-STRAS, "   
lv_xflg_street_changed  TYPE JPSD_XFELD. "   

  CALL FUNCTION 'ISP_ADDRESS_EXTRACT'  "Extract Address Data
    EXPORTING
         DIALOG = lv_dialog
         LAND = lv_land
         ORT = lv_ort
         PLZ = lv_plz
         STRASSE = lv_strasse
    IMPORTING
         ADRDATA = lv_adrdata
         ANSCHR_TYP = lv_anschr_typ
         XFLG_DATA_CHANGED = lv_xflg_data_changed
         XFLG_TOWN_CHANGED = lv_xflg_town_changed
         XFLG_STREET_CHANGED = lv_xflg_street_changed
    EXCEPTIONS
        WRONG_INPUT = 1
. " ISP_ADDRESS_EXTRACT




ABAP code using 7.40 inline data declarations to call FM ISP_ADDRESS_EXTRACT

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.

DATA(ld_dialog) = JPSD_FALSE.
 
 
 
"SELECT single LAND1 FROM RJGSADR INTO @DATA(ld_land).
 
"SELECT single ERSTADR FROM JGTSADR INTO @DATA(ld_anschr_typ).
 
"SELECT single ORT01 FROM RJGSADR INTO @DATA(ld_ort).
 
 
"SELECT single PSTLZ FROM RJGSADR INTO @DATA(ld_plz).
 
 
"SELECT single STRAS FROM RJGSADR INTO @DATA(ld_strasse).
 
 


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!