BBP_PARTNER_ADDRESS_GET_COMPL SAP Function module - Lesen einer kompletten Adresse (inkl. Kommunikation)

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

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

Pattern for FM BBP_PARTNER_ADDRESS_GET_COMPL - BBP PARTNER ADDRESS GET COMPL

CALL FUNCTION 'BBP_PARTNER_ADDRESS_GET_COMPL' "Lesen einer kompletten Adresse (inkl. Kommunikation)
  EXPORTING
    iv_addr_nr =                " ad_addrnum    Adreßnummer
*   iv_addr_np =                " ad_persnum    Personennummer
    iv_addr_type =              " ad_adrtype    Adreßtyp (1=Organisation, 2=Person, 3=Ansprechpartner)
*   iv_addr_origin =            " crmt_addr_origin_md  Herkunft einer Partneradresse (PERFORMANCE RELEVANT!)
*   iv_get_database = SPACE     " xflag         Soll der Datenbankstand gelesen werden?
*   iv_include_slow_comm_fields = SPACE  " xflag  Lesen langsamer Comm-Felder bei BAPIADDRx Struktur (z.b. eMail)
*   iv_read_complete_addr = SPACE  " xflag      Lesen der kompletten Adresse
  IMPORTING
    es_addr1_complete =         " szadr_addr1_complete  Komplette Adresse für Typ 1
    es_addr2_complete =         " szadr_addr2_complete  Komplette Adresse für Typ 2
    es_addr3_complete =         " szadr_addr3_complete  Komplette Adresse für Typ 3
    es_bapiaddr1 =              " bapiaddr1     Komplette BAPI-Adresse für Typ 1
    es_bapiaddr2 =              " bapiaddr2     Komplette BAPI-Adresse für Typ 2
    es_bapiaddr3 =              " bapiaddr3     Komplette BAPI-Adresse für Typ 3
  EXCEPTIONS
    ERROR_OCCURRED = 1          "
    .  "  BBP_PARTNER_ADDRESS_GET_COMPL

ABAP code example for Function Module BBP_PARTNER_ADDRESS_GET_COMPL

The ABAP code below is a full code listing to execute function module BBP_PARTNER_ADDRESS_GET_COMPL 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_es_addr1_complete  
 
 TYPE SZADR_ADDR1_COMPLETE
,
ld_es_addr2_complete  
 
 TYPE SZADR_ADDR2_COMPLETE
,
ld_es_addr3_complete  
 
 TYPE SZADR_ADDR3_COMPLETE
,
ld_es_bapiaddr1  
 
 TYPE BAPIADDR1
,
ld_es_bapiaddr2  
 
 TYPE BAPIADDR2
,
ld_es_bapiaddr3  
 
 TYPE BAPIADDR3
.


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

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

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

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

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

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

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

CALL FUNCTION 'BBP_PARTNER_ADDRESS_GET_COMPL'
  EXPORTING
    iv_addr_nr =                 ld_iv_addr_nr
*   iv_addr_np =                 ld_iv_addr_np
    iv_addr_type =               ld_iv_addr_type
*   iv_addr_origin =             ld_iv_addr_origin
*   iv_get_database =            ld_iv_get_database
*   iv_include_slow_comm_fields =    ld_iv_include_slow_comm_fields
*   iv_read_complete_addr =      ld_iv_read_complete_addr
  IMPORTING
    es_addr1_complete =          ld_es_addr1_complete
    es_addr2_complete =          ld_es_addr2_complete
    es_addr3_complete =          ld_es_addr3_complete
    es_bapiaddr1 =               ld_es_bapiaddr1
    es_bapiaddr2 =               ld_es_bapiaddr2
    es_bapiaddr3 =               ld_es_bapiaddr3
  EXCEPTIONS
    ERROR_OCCURRED =             1
    .  "  BBP_PARTNER_ADDRESS_GET_COMPL

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_es_addr1_complete
 
 TYPE SZADR_ADDR1_COMPLETE ,
ld_iv_addr_nr
 
 TYPE AD_ADDRNUM ,
ld_es_addr2_complete
 
 TYPE SZADR_ADDR2_COMPLETE ,
ld_iv_addr_np
 
 TYPE AD_PERSNUM ,
ld_es_addr3_complete
 
 TYPE SZADR_ADDR3_COMPLETE ,
ld_iv_addr_type
 
 TYPE AD_ADRTYPE ,
ld_es_bapiaddr1
 
 TYPE BAPIADDR1 ,
ld_iv_addr_origin
 
 TYPE CRMT_ADDR_ORIGIN_MD ,
ld_es_bapiaddr2
 
 TYPE BAPIADDR2 ,
ld_iv_get_database
 
 TYPE XFLAG ,
ld_es_bapiaddr3
 
 TYPE BAPIADDR3 ,
ld_iv_include_slow_comm_fields
 
 TYPE XFLAG ,
ld_iv_read_complete_addr
 
 TYPE XFLAG .


ld_iv_addr_nr = 'Check type of data required'.
ld_iv_addr_np = 'Check type of data required'.
ld_iv_addr_type = 'Check type of data required'.
ld_iv_addr_origin = 'Check type of data required'.
ld_iv_get_database = 'Check type of data required'.
ld_iv_include_slow_comm_fields = 'Check type of data required'.
ld_iv_read_complete_addr = 'Check type of data required'.