FDM_AR_BUP_CONTACT_ADDRESS_KEY SAP Function module

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

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

Pattern for FM FDM_AR_BUP_CONTACT_ADDRESS_KEY - FDM AR BUP CONTACT ADDRESS KEY

CALL FUNCTION 'FDM_AR_BUP_CONTACT_ADDRESS_KEY' "
* EXPORTING
*   i_case_guid =               " bdm_case_guid  FSCM-DM: GUID (Internal Key of Dispute Case)
*   it_attributes =             " bdm_t_attribute  FSCM-DM: Attribute Value
  IMPORTING
    e_addrtype =                " ad_adrtype    Address Type (1=Organization, 2=Person, 3=Contact Person)
    e_addrnum =                 " ad_addrnum    Address Number
    e_persnum =                 " ad_persnum    Person Number
    e_addrsource =              " ad_adrtype
    e_default_comm =            " ad_comm
    e_langu =                   " spras
    es_return =                 " bapiret2      Return Parameter(s)
    .  "  FDM_AR_BUP_CONTACT_ADDRESS_KEY

ABAP code example for Function Module FDM_AR_BUP_CONTACT_ADDRESS_KEY

The ABAP code below is a full code listing to execute function module FDM_AR_BUP_CONTACT_ADDRESS_KEY 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_e_addrtype  
 
 TYPE AD_ADRTYPE
,
ld_e_addrnum  
 
 TYPE AD_ADDRNUM
,
ld_e_persnum  
 
 TYPE AD_PERSNUM
,
ld_e_addrsource  
 
 TYPE AD_ADRTYPE
,
ld_e_default_comm  
 
 TYPE AD_COMM
,
ld_e_langu  
 
 TYPE SPRAS
,
ld_es_return  
 
 TYPE BAPIRET2
.


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

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

CALL FUNCTION 'FDM_AR_BUP_CONTACT_ADDRESS_KEY'
* EXPORTING
*   i_case_guid =                ld_i_case_guid
*   it_attributes =              ld_it_attributes
  IMPORTING
    e_addrtype =                 ld_e_addrtype
    e_addrnum =                  ld_e_addrnum
    e_persnum =                  ld_e_persnum
    e_addrsource =               ld_e_addrsource
    e_default_comm =             ld_e_default_comm
    e_langu =                    ld_e_langu
    es_return =                  ld_es_return
    .  "  FDM_AR_BUP_CONTACT_ADDRESS_KEY

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_e_addrtype
 
 TYPE AD_ADRTYPE ,
ld_i_case_guid
 
 TYPE BDM_CASE_GUID ,
ld_e_addrnum
 
 TYPE AD_ADDRNUM ,
ld_it_attributes
 
 TYPE BDM_T_ATTRIBUTE ,
ld_e_persnum
 
 TYPE AD_PERSNUM ,
ld_e_addrsource
 
 TYPE AD_ADRTYPE ,
ld_e_default_comm
 
 TYPE AD_COMM ,
ld_e_langu
 
 TYPE SPRAS ,
ld_es_return
 
 TYPE BAPIRET2 .


ld_i_case_guid = 'Check type of data required'.
ld_it_attributes = 'Check type of data required'.