SAP ADDR_GET_COMPLETE_ALL_TYPES Function Module for

Search SAP Function Modules

ADDR_GET_COMPLETE_ALL_TYPES is a standard addr get complete all types SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 addr get complete all types FM, simply by entering the name ADDR_GET_COMPLETE_ALL_TYPES into the relevant SAP transaction such as SE37 or SE38.

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

Function ADDR_GET_COMPLETE_ALL_TYPES 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 'ADDR_GET_COMPLETE_ALL_TYPES'"
  EXPORTING
   ADDRNUMBER =  "Address Number
*  PERSNUMBER =  "Person Number
   ADDRESS_OBJECT_TYPE =  "Address type (1=Organization, 2=Person, 3=Contact person)
*  IV_CURRENT_COMM_DATA = 'X' "

 IMPORTING
   ADDR1_COMPLETE =  "
   ADDR2_COMPLETE =  "
   ADDR3_COMPLETE =  "
   ADDR1_COMPLETE_BAPI =  "BAPI Reference Structure for Addresses (Org./Company)
   ADDR2_COMPLETE_BAPI =  "BAPI reference structure for addresses (nat. persons)
   ADDR3_COMPLETE_BAPI =  "BAPI Reference Structure for Addresses (Contact Person)

EXCEPTIONS
   PARAMETER_ERROR = 1    ADDRESS_NOT_EXIST = 2    PERSON_NOT_EXIST = 3    INTERNAL_ERROR = 4 

.

IMPORTING Parameters details for ADDR_GET_COMPLETE_ALL_TYPES

ADDRNUMBER - Address Number

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

PERSNUMBER - Person Number

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

ADDRESS_OBJECT_TYPE - Address type (1=Organization, 2=Person, 3=Contact person)

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

IV_CURRENT_COMM_DATA -

Data type: AD_COMCURR
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ADDR_GET_COMPLETE_ALL_TYPES

ADDR1_COMPLETE -

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

ADDR2_COMPLETE -

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

ADDR3_COMPLETE -

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

ADDR1_COMPLETE_BAPI - BAPI Reference Structure for Addresses (Org./Company)

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

ADDR2_COMPLETE_BAPI - BAPI reference structure for addresses (nat. persons)

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

ADDR3_COMPLETE_BAPI - BAPI Reference Structure for Addresses (Contact Person)

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

EXCEPTIONS details

PARAMETER_ERROR - Incorrect parameter values

Data type:
Optional: No
Call by Reference: Yes

ADDRESS_NOT_EXIST - Address does not exist

Data type:
Optional: No
Call by Reference: Yes

PERSON_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Serious internal error (MESSAGE A...)

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADDR_GET_COMPLETE_ALL_TYPES 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.

ABAP code using 7.40 inline data declarations to call FM ADDR_GET_COMPLETE_ALL_TYPES

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.

Search for further information about these or an SAP related objects