SAP ISP_ADDRESS_CHECK_POST_UPDATE Function Module for IS-M/SD: Determine Whether Change to Postal Data Affect Address









ISP_ADDRESS_CHECK_POST_UPDATE is a standard isp address check post update 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: Determine Whether Change to Postal Data Affect Address 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 check post update FM, simply by entering the name ISP_ADDRESS_CHECK_POST_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISP_ADDRESS_CHECK_POST_UPDATE 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_CHECK_POST_UPDATE'"IS-M/SD: Determine Whether Change to Postal Data Affect Address
EXPORTING
GUELTIGBIS = "
* AENDNR = "

CHANGING
* X_ADR_CHANGED = "Address changed

TABLES
JGTSADR_EXT_TAB = "
JGTADRA_EXT_TAB = "

EXCEPTIONS
NO_CHANGES = 1
.



IMPORTING Parameters details for ISP_ADDRESS_CHECK_POST_UPDATE

GUELTIGBIS -

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

AENDNR -

Data type: JSTAENDER-AENDNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for ISP_ADDRESS_CHECK_POST_UPDATE

X_ADR_CHANGED - Address changed

Data type: JGTSADR-XADRLOE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for ISP_ADDRESS_CHECK_POST_UPDATE

JGTSADR_EXT_TAB -

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

JGTADRA_EXT_TAB -

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

EXCEPTIONS details

NO_CHANGES -

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

Copy and paste ABAP code example for ISP_ADDRESS_CHECK_POST_UPDATE 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_gueltigbis  TYPE JGTADRA-WDAT2, "   
lv_no_changes  TYPE JGTADRA, "   
lv_x_adr_changed  TYPE JGTSADR-XADRLOE, "   
lt_jgtsadr_ext_tab  TYPE STANDARD TABLE OF RJGADRA, "   
lv_aendnr  TYPE JSTAENDER-AENDNR, "   
lt_jgtadra_ext_tab  TYPE STANDARD TABLE OF RJMG07. "   

  CALL FUNCTION 'ISP_ADDRESS_CHECK_POST_UPDATE'  "IS-M/SD: Determine Whether Change to Postal Data Affect Address
    EXPORTING
         GUELTIGBIS = lv_gueltigbis
         AENDNR = lv_aendnr
    CHANGING
         X_ADR_CHANGED = lv_x_adr_changed
    TABLES
         JGTSADR_EXT_TAB = lt_jgtsadr_ext_tab
         JGTADRA_EXT_TAB = lt_jgtadra_ext_tab
    EXCEPTIONS
        NO_CHANGES = 1
. " ISP_ADDRESS_CHECK_POST_UPDATE




ABAP code using 7.40 inline data declarations to call FM ISP_ADDRESS_CHECK_POST_UPDATE

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 WDAT2 FROM JGTADRA INTO @DATA(ld_gueltigbis).
 
 
"SELECT single XADRLOE FROM JGTSADR INTO @DATA(ld_x_adr_changed).
 
 
"SELECT single AENDNR FROM JSTAENDER INTO @DATA(ld_aendnr).
 
 


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!