SAP ADDR_COMM_GET Function Module for

Search SAP Function Modules

ADDR_COMM_GET is a standard addr comm get 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 comm get FM, simply by entering the name ADDR_COMM_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function ADDR_COMM_GET 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_COMM_GET'"
  EXPORTING
*  ADDRESS_HANDLE = ' ' "
*  ADDRESS_NUMBER = ' ' "
*  DATE_FROM = '00010101' "
*  LANGUAGE = SY-LANGU "
   TABLE_TYPE =  "
*  IV_CURRENT_STATE = 'X' "
*  IV_FILL_EMPTY_COUNTRY = 'X' "

 IMPORTING
   RETURNCODE =  "

TABLES
   COMM_TABLE =  "
*  ERROR_TABLE =  "
*  ET_USAGE =  "Address Usages
*  ET_USAGE_UUID =  "

EXCEPTIONS
   PARAMETER_ERROR = 1    ADDRESS_NOT_EXIST = 2    INTERNAL_ERROR = 3 

.

IMPORTING Parameters details for ADDR_COMM_GET

ADDRESS_HANDLE -

Data type: SZAD_FIELD-HANDLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ADDRESS_NUMBER -

Data type: ADRC-ADDRNUMBER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATE_FROM -

Data type: ADCP-DATE_FROM
Default: '00010101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

Data type: ADRT-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLE_TYPE -

Data type: SZAD_FIELD-TABLE_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CURRENT_STATE -

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

IV_FILL_EMPTY_COUNTRY -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ADDR_COMM_GET

RETURNCODE -

Data type: SZAD_FIELD-RETURNCODE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ADDR_COMM_GET

COMM_TABLE -

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

ERROR_TABLE -

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

ET_USAGE - Address Usages

Data type: ADSUSE
Optional: Yes
Call by Reference: Yes

ET_USAGE_UUID -

Data type: ADSUSE_UUID
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PARAMETER_ERROR -

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

ADDRESS_NOT_EXIST -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for ADDR_COMM_GET 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_COMM_GET

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