SAP ADDR_PERSON_INSERT Function Module for
ADDR_PERSON_INSERT is a standard addr person insert 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 person insert FM, simply by entering the name ADDR_PERSON_INSERT 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_PERSON_INSERT 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_PERSON_INSERT'".
EXPORTING
PERSON_HANDLE = "
PERSON_DATA = "
PERSON_GROUP = "
* DATE_FROM = '00010101' "
* CHECK_ADDRESS = 'X' "Flag: Check address contents
IMPORTING
RETURNCODE = "
TABLES
* ERROR_TABLE = "
EXCEPTIONS
PARAMETER_ERROR = 1 PERSON_EXISTS = 2 INTERNAL_ERROR = 3
IMPORTING Parameters details for ADDR_PERSON_INSERT
PERSON_HANDLE -
Data type: SZAD_FIELD-HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
PERSON_DATA -
Data type: PERS_DATAOptional: No
Call by Reference: No ( called with pass by value option)
PERSON_GROUP -
Data type: TSAD8-PERS_GROUPOptional: No
Call by Reference: No ( called with pass by value option)
DATE_FROM -
Data type: ADRP-DATE_FROMDefault: '00010101'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHECK_ADDRESS - Flag: Check address contents
Data type: SZAD_FIELD-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDR_PERSON_INSERT
RETURNCODE -
Data type: SZAD_FIELD-RETURNCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADDR_PERSON_INSERT
ERROR_TABLE -
Data type: ADDR_ERROROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PERSON_EXISTS -
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_PERSON_INSERT 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_returncode | TYPE SZAD_FIELD-RETURNCODE, " | |||
| lt_error_table | TYPE STANDARD TABLE OF ADDR_ERROR, " | |||
| lv_person_handle | TYPE SZAD_FIELD-HANDLE, " | |||
| lv_parameter_error | TYPE SZAD_FIELD, " | |||
| lv_person_data | TYPE PERS_DATA, " | |||
| lv_person_exists | TYPE PERS_DATA, " | |||
| lv_person_group | TYPE TSAD8-PERS_GROUP, " | |||
| lv_internal_error | TYPE TSAD8, " | |||
| lv_date_from | TYPE ADRP-DATE_FROM, " '00010101' | |||
| lv_check_address | TYPE SZAD_FIELD-FLAG. " 'X' |
|   CALL FUNCTION 'ADDR_PERSON_INSERT' " |
| EXPORTING | ||
| PERSON_HANDLE | = lv_person_handle | |
| PERSON_DATA | = lv_person_data | |
| PERSON_GROUP | = lv_person_group | |
| DATE_FROM | = lv_date_from | |
| CHECK_ADDRESS | = lv_check_address | |
| IMPORTING | ||
| RETURNCODE | = lv_returncode | |
| TABLES | ||
| ERROR_TABLE | = lt_error_table | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| PERSON_EXISTS = 2 | ||
| INTERNAL_ERROR = 3 | ||
| . " ADDR_PERSON_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM ADDR_PERSON_INSERT
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 RETURNCODE FROM SZAD_FIELD INTO @DATA(ld_returncode). | ||||
| "SELECT single HANDLE FROM SZAD_FIELD INTO @DATA(ld_person_handle). | ||||
| "SELECT single PERS_GROUP FROM TSAD8 INTO @DATA(ld_person_group). | ||||
| "SELECT single DATE_FROM FROM ADRP INTO @DATA(ld_date_from). | ||||
| DATA(ld_date_from) | = '00010101'. | |||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_check_address). | ||||
| DATA(ld_check_address) | = 'X'. | |||
Search for further information about these or an SAP related objects