ISM_BAPI_007_ADDRESS_COMPLETE SAP Function module - IS-M: BAPI BP: Enter Missing Address Data

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

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

Pattern for FM ISM_BAPI_007_ADDRESS_COMPLETE - ISM BAPI 007 ADDRESS COMPLETE

CALL FUNCTION 'ISM_BAPI_007_ADDRESS_COMPLETE' "IS-M: BAPI BP: Enter Missing Address Data
  EXPORTING
    pv_partner =                " bu_partner    Business Partner Number
    ps_central_rel =            " rjgbusism007_bus006_central  IS-M: Business Partner BAPI SAP BP Central STR
    ps_address_rel =            " rjgbusism007_bus006_addr  IS-M: Business Partner BAPI SAP BP Address STR
  CHANGING
    ps_bapiad1vl =              " bapiad1vl     Address type 1 distribution BAPI structure
    ps_bapiad1vl_x =            " bapiad1vlx    Address type 1 distribution BAPI structure
    pt_return =                 " bapiret2_t    Return Table
    .  "  ISM_BAPI_007_ADDRESS_COMPLETE

ABAP code example for Function Module ISM_BAPI_007_ADDRESS_COMPLETE

The ABAP code below is a full code listing to execute function module ISM_BAPI_007_ADDRESS_COMPLETE 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_ps_bapiad1vl) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'ISM_BAPI_007_ADDRESS_COMPLETE'
  EXPORTING
    pv_partner =                 ld_pv_partner
    ps_central_rel =             ld_ps_central_rel
    ps_address_rel =             ld_ps_address_rel
  CHANGING
    ps_bapiad1vl =               ld_ps_bapiad1vl
    ps_bapiad1vl_x =             ld_ps_bapiad1vl_x
    pt_return =                  ld_pt_return
    .  "  ISM_BAPI_007_ADDRESS_COMPLETE

IF SY-SUBRC EQ 0.
  "All OK
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_ps_bapiad1vl
 
 TYPE BAPIAD1VL ,
ld_pv_partner
 
 TYPE BU_PARTNER ,
ld_ps_bapiad1vl_x
 
 TYPE BAPIAD1VLX ,
ld_ps_central_rel
 
 TYPE RJGBUSISM007_BUS006_CENTRAL ,
ld_pt_return
 
 TYPE BAPIRET2_T ,
ld_ps_address_rel
 
 TYPE RJGBUSISM007_BUS006_ADDR .


ld_ps_bapiad1vl = 'Check type of data required'.
ld_pv_partner = 'Check type of data required'.
ld_ps_bapiad1vl_x = 'Check type of data required'.
ld_ps_central_rel = 'Check type of data required'.
ld_pt_return = 'Check type of data required'.
ld_ps_address_rel = 'Check type of data required'.