SAP ADDRESS_GET_COM Function Module for
ADDRESS_GET_COM is a standard address get com 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 address get com FM, simply by entering the name ADDRESS_GET_COM into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAD2
Program Name: SAPLSAD2
Main Program: SAPLSAD2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ADDRESS_GET_COM 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 'ADDRESS_GET_COM'".
EXPORTING
ENTRY_ADRNR = "Address number
* ENTRY_COM_ART = ' ' "Required type of communication
* ENTRY_LFDNR = ' ' "Required serial number
* ENTRY_VERSION = ' ' "Version of address (national indicator)
IMPORTING
EX_COM_ART = "Type of communication
EX_LFDNR = "Serial number
EX_NUMBER = "Address data/number
EX_NAME1 = "
EXCEPTIONS
ADDR_NOT_EXIST = 1 DATA_NOT_FOUND = 2 WRONG_DATA = 3
IMPORTING Parameters details for ADDRESS_GET_COM
ENTRY_ADRNR - Address number
Data type: SADR-ADRNROptional: No
Call by Reference: No ( called with pass by value option)
ENTRY_COM_ART - Required type of communication
Data type: SADR-STDCOMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENTRY_LFDNR - Required serial number
Data type: SADR3-LFDNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENTRY_VERSION - Version of address (national indicator)
Data type: SADR-NATIODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDRESS_GET_COM
EX_COM_ART - Type of communication
Data type: SADR-STDCOMOptional: No
Call by Reference: No ( called with pass by value option)
EX_LFDNR - Serial number
Data type: SADR3-LFDNROptional: No
Call by Reference: No ( called with pass by value option)
EX_NUMBER - Address data/number
Data type: SOXEA-ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
EX_NAME1 -
Data type: SADR-NAME1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADDR_NOT_EXIST - Address number does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_DATA - Incorrect data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADDRESS_GET_COM 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_ex_com_art | TYPE SADR-STDCOM, " | |||
| lv_entry_adrnr | TYPE SADR-ADRNR, " | |||
| lv_addr_not_exist | TYPE SADR, " | |||
| lv_ex_lfdnr | TYPE SADR3-LFDNR, " | |||
| lv_entry_com_art | TYPE SADR-STDCOM, " SPACE | |||
| lv_data_not_found | TYPE SADR, " | |||
| lv_ex_number | TYPE SOXEA-ADDRESS, " | |||
| lv_wrong_data | TYPE SOXEA, " | |||
| lv_entry_lfdnr | TYPE SADR3-LFDNR, " SPACE | |||
| lv_ex_name1 | TYPE SADR-NAME1, " | |||
| lv_entry_version | TYPE SADR-NATIO. " SPACE |
|   CALL FUNCTION 'ADDRESS_GET_COM' " |
| EXPORTING | ||
| ENTRY_ADRNR | = lv_entry_adrnr | |
| ENTRY_COM_ART | = lv_entry_com_art | |
| ENTRY_LFDNR | = lv_entry_lfdnr | |
| ENTRY_VERSION | = lv_entry_version | |
| IMPORTING | ||
| EX_COM_ART | = lv_ex_com_art | |
| EX_LFDNR | = lv_ex_lfdnr | |
| EX_NUMBER | = lv_ex_number | |
| EX_NAME1 | = lv_ex_name1 | |
| EXCEPTIONS | ||
| ADDR_NOT_EXIST = 1 | ||
| DATA_NOT_FOUND = 2 | ||
| WRONG_DATA = 3 | ||
| . " ADDRESS_GET_COM | ||
ABAP code using 7.40 inline data declarations to call FM ADDRESS_GET_COM
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 STDCOM FROM SADR INTO @DATA(ld_ex_com_art). | ||||
| "SELECT single ADRNR FROM SADR INTO @DATA(ld_entry_adrnr). | ||||
| "SELECT single LFDNR FROM SADR3 INTO @DATA(ld_ex_lfdnr). | ||||
| "SELECT single STDCOM FROM SADR INTO @DATA(ld_entry_com_art). | ||||
| DATA(ld_entry_com_art) | = ' '. | |||
| "SELECT single ADDRESS FROM SOXEA INTO @DATA(ld_ex_number). | ||||
| "SELECT single LFDNR FROM SADR3 INTO @DATA(ld_entry_lfdnr). | ||||
| DATA(ld_entry_lfdnr) | = ' '. | |||
| "SELECT single NAME1 FROM SADR INTO @DATA(ld_ex_name1). | ||||
| "SELECT single NATIO FROM SADR INTO @DATA(ld_entry_version). | ||||
| DATA(ld_entry_version) | = ' '. | |||
Search for further information about these or an SAP related objects