SAP ADDR_PERS_COMP_IMP_SUBSCREEN Function Module for
ADDR_PERS_COMP_IMP_SUBSCREEN is a standard addr pers comp imp subscreen 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 imp subscreen FM, simply by entering the name ADDR_PERS_COMP_IMP_SUBSCREEN 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_IMP_SUBSCREEN 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_IMP_SUBSCREEN'".
IMPORTING
VALUES = "
DUPLICATE_CHECK_STATUS = "
ERROR_IN_ADDRESS_DATA = "
DATA_HAS_CHANGED = "
NEW_COMP_ADDRESS = "
NEW_ADDRNUMBER = "
CURSOR_FIELD = "
DUPLICATE_RECORD_FOUND = "
* DUPLICATE_CHECK_LIST = "Table with Duplicate Hits (Address Key/Owner Objects)
DUPL_INDEX_INCOMPLETE = "
TABLES
* MESSAGE_TABLE = "Table with errors, warnings, information
* DUPLICATE_CHECK_ERRORS = "
EXCEPTIONS
INTERNAL_ERROR = 1
EXPORTING Parameters details for ADDR_PERS_COMP_IMP_SUBSCREEN
VALUES -
Data type: ADDR3_DATAOptional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_CHECK_STATUS -
Data type: AD_DUPSTATOptional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_ADDRESS_DATA -
Data type: T_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
DATA_HAS_CHANGED -
Data type: T_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
NEW_COMP_ADDRESS -
Data type: T_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
NEW_ADDRNUMBER -
Data type: ADDR1_SEL-ADDRNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
CURSOR_FIELD -
Data type: SCRFNAMEOptional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_RECORD_FOUND -
Data type: T_BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_CHECK_LIST - Table with Duplicate Hits (Address Key/Owner Objects)
Data type: ADKEY_OBJ_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
DUPL_INDEX_INCOMPLETE -
Data type: T_BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADDR_PERS_COMP_IMP_SUBSCREEN
MESSAGE_TABLE - Table with errors, warnings, information
Data type: ADDR_ERROROptional: Yes
Call by Reference: No ( called with pass by value option)
DUPLICATE_CHECK_ERRORS -
Data type: ADDUPERROR_TABOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
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_IMP_SUBSCREEN 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_values | TYPE ADDR3_DATA, " | |||
lt_message_table | TYPE STANDARD TABLE OF ADDR_ERROR, " | |||
lv_internal_error | TYPE ADDR_ERROR, " | |||
lv_duplicate_check_status | TYPE AD_DUPSTAT, " | |||
lv_error_in_address_data | TYPE T_BOOL, " | |||
lt_duplicate_check_errors | TYPE STANDARD TABLE OF ADDUPERROR_TAB, " | |||
lv_data_has_changed | TYPE T_BOOL, " | |||
lv_new_comp_address | TYPE T_BOOL, " | |||
lv_new_addrnumber | TYPE ADDR1_SEL-ADDRNUMBER, " | |||
lv_cursor_field | TYPE SCRFNAME, " | |||
lv_duplicate_record_found | TYPE T_BOOLE, " | |||
lv_duplicate_check_list | TYPE ADKEY_OBJ_TAB, " | |||
lv_dupl_index_incomplete | TYPE T_BOOLE. " |
  CALL FUNCTION 'ADDR_PERS_COMP_IMP_SUBSCREEN' " |
IMPORTING | ||
VALUES | = lv_values | |
DUPLICATE_CHECK_STATUS | = lv_duplicate_check_status | |
ERROR_IN_ADDRESS_DATA | = lv_error_in_address_data | |
DATA_HAS_CHANGED | = lv_data_has_changed | |
NEW_COMP_ADDRESS | = lv_new_comp_address | |
NEW_ADDRNUMBER | = lv_new_addrnumber | |
CURSOR_FIELD | = lv_cursor_field | |
DUPLICATE_RECORD_FOUND | = lv_duplicate_record_found | |
DUPLICATE_CHECK_LIST | = lv_duplicate_check_list | |
DUPL_INDEX_INCOMPLETE | = lv_dupl_index_incomplete | |
TABLES | ||
MESSAGE_TABLE | = lt_message_table | |
DUPLICATE_CHECK_ERRORS | = lt_duplicate_check_errors | |
EXCEPTIONS | ||
INTERNAL_ERROR = 1 | ||
. " ADDR_PERS_COMP_IMP_SUBSCREEN |
ABAP code using 7.40 inline data declarations to call FM ADDR_PERS_COMP_IMP_SUBSCREEN
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_new_addrnumber). | ||||
Search for further information about these or an SAP related objects