SAP ADDR_ADJUST Function Module for Help Module for Client Adjustment/Customizing Addresses
ADDR_ADJUST is a standard addr adjust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Help Module for Client Adjustment/Customizing Addresses processing and below is the pattern details for this FM, 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 adjust FM, simply by entering the name ADDR_ADJUST into the relevant SAP transaction such as SE37 or SE38.
Function Group: SZAI
Program Name: SAPLSZAI
Main Program: SAPLSZAI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADDR_ADJUST 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_ADJUST'"Help Module for Client Adjustment/Customizing Addresses.
EXPORTING
* ADDRNUMBER = "Address Number
* ADDRHANDLE = "Address Handle
ADDRESS_GROUP = "Address Group
IMPORTING
RETURNCODE = "Return code: ' '(ok), 'I'nfo, 'W'arning, 'E'rror
TABLES
* ERROR_TABLE = "Table with errors, warnings, information
EXCEPTIONS
PARAMETER_ERROR = 1 ADDRESS_NOT_EXIST = 2 HANDLE_EXIST = 3 INTERNAL_ERROR = 4 ADDRESS_NOT_COMPARED = 5
IMPORTING Parameters details for ADDR_ADJUST
ADDRNUMBER - Address Number
Data type: ADDR1_SEL-ADDRNUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRHANDLE - Address Handle
Data type: ADDR1_SEL-ADDRHANDLEOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESS_GROUP - Address Group
Data type: ADRG-ADDR_GROUPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ADDR_ADJUST
RETURNCODE - Return code: ' '(ok), 'I'nfo, 'W'arning, 'E'rror
Data type: SZAD_FIELD-RETURNCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADDR_ADJUST
ERROR_TABLE - Table with errors, warnings, information
Data type: ADDR_ERROROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR - Incorrect parameter values
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ADDRESS_NOT_EXIST - Address does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HANDLE_EXIST - Handle already exists (only for 'Insert')
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)
ADDRESS_NOT_COMPARED - Address not compared with ADDR_COMPARE
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADDR_ADJUST 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_addrnumber | TYPE ADDR1_SEL-ADDRNUMBER, " | |||
| lv_returncode | TYPE SZAD_FIELD-RETURNCODE, " | |||
| lt_error_table | TYPE STANDARD TABLE OF ADDR_ERROR, " | |||
| lv_parameter_error | TYPE ADDR_ERROR, " | |||
| lv_addrhandle | TYPE ADDR1_SEL-ADDRHANDLE, " | |||
| lv_address_not_exist | TYPE ADDR1_SEL, " | |||
| lv_handle_exist | TYPE ADDR1_SEL, " | |||
| lv_address_group | TYPE ADRG-ADDR_GROUP, " | |||
| lv_internal_error | TYPE ADRG, " | |||
| lv_address_not_compared | TYPE ADRG. " |
|   CALL FUNCTION 'ADDR_ADJUST' "Help Module for Client Adjustment/Customizing Addresses |
| EXPORTING | ||
| ADDRNUMBER | = lv_addrnumber | |
| ADDRHANDLE | = lv_addrhandle | |
| ADDRESS_GROUP | = lv_address_group | |
| IMPORTING | ||
| RETURNCODE | = lv_returncode | |
| TABLES | ||
| ERROR_TABLE | = lt_error_table | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| ADDRESS_NOT_EXIST = 2 | ||
| HANDLE_EXIST = 3 | ||
| INTERNAL_ERROR = 4 | ||
| ADDRESS_NOT_COMPARED = 5 | ||
| . " ADDR_ADJUST | ||
ABAP code using 7.40 inline data declarations to call FM ADDR_ADJUST
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_addrnumber). | ||||
| "SELECT single RETURNCODE FROM SZAD_FIELD INTO @DATA(ld_returncode). | ||||
| "SELECT single ADDRHANDLE FROM ADDR1_SEL INTO @DATA(ld_addrhandle). | ||||
| "SELECT single ADDR_GROUP FROM ADRG INTO @DATA(ld_address_group). | ||||
Search for further information about these or an SAP related objects