SAP ADDR_PERS_COMP_DIALOG Function Module for
ADDR_PERS_COMP_DIALOG is a standard addr pers comp dialog 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 pers comp dialog FM, simply by entering the name ADDR_PERS_COMP_DIALOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SZA5
Program Name: SAPLSZA5
Main Program: SAPLSZA5
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADDR_PERS_COMP_DIALOG 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_PERS_COMP_DIALOG'".
EXPORTING
* CHECK_ADDRESS = 'X' "Checkbox Field
* IV_TIME_DEPENDENT_COMM_DATA = ' ' "
IMPORTING
OK_CODE = "OK_CODE passed for calling program
TABLES
NUMBER_HANDLE_TAB = "Transfer table of addresses to be processed
* VALUES = "Return table with maintained address data
EXCEPTIONS
ADDRESS_NOT_EXIST = 1 GROUP_NOT_VALID = 2 PARAMETER_ERROR = 3 INTERNAL_ERROR = 4
IMPORTING Parameters details for ADDR_PERS_COMP_DIALOG
CHECK_ADDRESS - Checkbox Field
Data type: SZAD_FIELD-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TIME_DEPENDENT_COMM_DATA -
Data type: AD_TIMEDEPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDR_PERS_COMP_DIALOG
OK_CODE - OK_CODE passed for calling program
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADDR_PERS_COMP_DIALOG
NUMBER_HANDLE_TAB - Transfer table of addresses to be processed
Data type: ADDR3_DIAOptional: No
Call by Reference: No ( called with pass by value option)
VALUES - Return table with maintained address data
Data type: ADDR3_DATAOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADDRESS_NOT_EXIST - Address does not exist or is invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GROUP_NOT_VALID - Address group does not exist or is invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR - Incorrect parameter values
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)
Copy and paste ABAP code example for ADDR_PERS_COMP_DIALOG 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_ok_code | TYPE SY-UCOMM, " | |||
| lv_check_address | TYPE SZAD_FIELD-FLAG, " 'X' | |||
| lv_address_not_exist | TYPE SZAD_FIELD, " | |||
| lt_number_handle_tab | TYPE STANDARD TABLE OF ADDR3_DIA, " | |||
| lt_values | TYPE STANDARD TABLE OF ADDR3_DATA, " | |||
| lv_group_not_valid | TYPE ADDR3_DATA, " | |||
| lv_iv_time_dependent_comm_data | TYPE AD_TIMEDEP, " SPACE | |||
| lv_parameter_error | TYPE AD_TIMEDEP, " | |||
| lv_internal_error | TYPE AD_TIMEDEP. " |
|   CALL FUNCTION 'ADDR_PERS_COMP_DIALOG' " |
| EXPORTING | ||
| CHECK_ADDRESS | = lv_check_address | |
| IV_TIME_DEPENDENT_COMM_DATA | = lv_iv_time_dependent_comm_data | |
| IMPORTING | ||
| OK_CODE | = lv_ok_code | |
| TABLES | ||
| NUMBER_HANDLE_TAB | = lt_number_handle_tab | |
| VALUES | = lt_values | |
| EXCEPTIONS | ||
| ADDRESS_NOT_EXIST = 1 | ||
| GROUP_NOT_VALID = 2 | ||
| PARAMETER_ERROR = 3 | ||
| INTERNAL_ERROR = 4 | ||
| . " ADDR_PERS_COMP_DIALOG | ||
ABAP code using 7.40 inline data declarations to call FM ADDR_PERS_COMP_DIALOG
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 UCOMM FROM SY INTO @DATA(ld_ok_code). | ||||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_check_address). | ||||
| DATA(ld_check_address) | = 'X'. | |||
| DATA(ld_iv_time_dependent_comm_data) | = ' '. | |||
Search for further information about these or an SAP related objects