SAP ADDR_GET_COMPLETE Function Module for Read the complete address object (incl. all communication tables)
ADDR_GET_COMPLETE is a standard addr get complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the complete address object (incl. all communication tables) processing and below is the pattern details for this FM, 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 FM, simply by entering the name ADDR_GET_COMPLETE 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 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'"Read the complete address object (incl. all communication tables).
EXPORTING
* ADDRNUMBER = "Address Number (Key of Database Table)
* ADDRHANDLE = "Address Handle (Temporary Key)
* ARCHIVE_HANDLE = "Read Address from Archive
* IV_CURRENT_COMM_DATA = 'X' "Indicator: Current Status of Communication Data
IMPORTING
ADDR1_COMPLETE = "Complete Address Object (Including Communication)
EXCEPTIONS
PARAMETER_ERROR = 1 ADDRESS_NOT_EXIST = 2 INTERNAL_ERROR = 3 WRONG_ACCESS_TO_ARCHIVE = 4
IMPORTING Parameters details for ADDR_GET_COMPLETE
ADDRNUMBER - Address Number (Key of Database Table)
Data type: ADDR1_SEL-ADDRNUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRHANDLE - Address Handle (Temporary Key)
Data type: ADDR1_SEL-ADDRHANDLEOptional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIVE_HANDLE - Read Address from Archive
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CURRENT_COMM_DATA - Indicator: Current Status of Communication Data
Data type: AD_COMCURRDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDR_GET_COMPLETE
ADDR1_COMPLETE - Complete Address Object (Including Communication)
Data type: SZADR_ADDR1_COMPLETEOptional: 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: No ( called with pass by value option)
ADDRESS_NOT_EXIST - Address does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Serious internal error (MESSAGE A...)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_ACCESS_TO_ARCHIVE - Incorrect access to archived data
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ADDR_GET_COMPLETE 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.DATA: | ||||
lv_addrnumber | TYPE ADDR1_SEL-ADDRNUMBER, " | |||
lv_addr1_complete | TYPE SZADR_ADDR1_COMPLETE, " | |||
lv_parameter_error | TYPE SZADR_ADDR1_COMPLETE, " | |||
lv_addrhandle | TYPE ADDR1_SEL-ADDRHANDLE, " | |||
lv_address_not_exist | TYPE ADDR1_SEL, " | |||
lv_archive_handle | TYPE SY-TABIX, " | |||
lv_internal_error | TYPE SY, " | |||
lv_iv_current_comm_data | TYPE AD_COMCURR, " 'X' | |||
lv_wrong_access_to_archive | TYPE AD_COMCURR. " |
  CALL FUNCTION 'ADDR_GET_COMPLETE' "Read the complete address object (incl. all communication tables) |
EXPORTING | ||
ADDRNUMBER | = lv_addrnumber | |
ADDRHANDLE | = lv_addrhandle | |
ARCHIVE_HANDLE | = lv_archive_handle | |
IV_CURRENT_COMM_DATA | = lv_iv_current_comm_data | |
IMPORTING | ||
ADDR1_COMPLETE | = lv_addr1_complete | |
EXCEPTIONS | ||
PARAMETER_ERROR = 1 | ||
ADDRESS_NOT_EXIST = 2 | ||
INTERNAL_ERROR = 3 | ||
WRONG_ACCESS_TO_ARCHIVE = 4 | ||
. " ADDR_GET_COMPLETE |
ABAP code using 7.40 inline data declarations to call FM ADDR_GET_COMPLETE
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."SELECT single ADDRNUMBER FROM ADDR1_SEL INTO @DATA(ld_addrnumber). | ||||
"SELECT single ADDRHANDLE FROM ADDR1_SEL INTO @DATA(ld_addrhandle). | ||||
"SELECT single TABIX FROM SY INTO @DATA(ld_archive_handle). | ||||
DATA(ld_iv_current_comm_data) | = 'X'. | |||
Search for further information about these or an SAP related objects