ISU_DB_EADRSTRTAMS_CHANGE SAP Function module - Change EADRSTRTAMS on Key Change to Street

ISU_DB_EADRSTRTAMS_CHANGE 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 ISU_DB_EADRSTRTAMS_CHANGE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISU_DB_EADRSTRTAMS_CHANGE - ISU DB EADRSTRTAMS CHANGE

CALL FUNCTION 'ISU_DB_EADRSTRTAMS_CHANGE' "Change EADRSTRTAMS on Key Change to Street
  EXPORTING
    x_country =                 " land1         Country Key
    x_strt_code_old =           " strt_code     Street Code for City/Street File
    x_strt_code_new =           " strt_code     Street Code for City/Street File
    x_istreetupdate =           " eistreetupdate  Transfer Table for Street Change
  EXCEPTIONS
    UPDATE_INCOMPLETE = 1       "               Error During Update
    .  "  ISU_DB_EADRSTRTAMS_CHANGE

ABAP code example for Function Module ISU_DB_EADRSTRTAMS_CHANGE

The ABAP code below is a full code listing to execute function module ISU_DB_EADRSTRTAMS_CHANGE 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).

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

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

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

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

CALL FUNCTION 'ISU_DB_EADRSTRTAMS_CHANGE'
  EXPORTING
    x_country =                  ld_x_country
    x_strt_code_old =            ld_x_strt_code_old
    x_strt_code_new =            ld_x_strt_code_new
    x_istreetupdate =            ld_x_istreetupdate
  EXCEPTIONS
    UPDATE_INCOMPLETE =          1
    .  "  ISU_DB_EADRSTRTAMS_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_x_country
 
 TYPE LAND1 ,
ld_x_strt_code_old
 
 TYPE STRT_CODE ,
ld_x_strt_code_new
 
 TYPE STRT_CODE ,
ld_x_istreetupdate
 
 TYPE EISTREETUPDATE .


ld_x_country = 'Check type of data required'.
ld_x_strt_code_old = 'Check type of data required'.
ld_x_strt_code_new = 'Check type of data required'.
ld_x_istreetupdate = 'Check type of data required'.