SAP ADDRESS_MAINTAIN Function Module for









ADDRESS_MAINTAIN is a standard address maintain 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 maintain FM, simply by entering the name ADDRESS_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: SAD1
Program Name: SAPLSAD1
Main Program: SAPLSAD1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ADDRESS_MAINTAIN 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_MAINTAIN'"
EXPORTING
ADRSWA_IN = "Work area entry.
* KENNZEICHEN = ' ' "Keep or delete address data
* OBJECT = ' ' "
* PROCESSING_STATUS = 'D' "Status of processing
* SAVE_INTERN = ' ' "Save externally or internally
* TITLE = ' ' "

IMPORTING
ADRSWA_OUT = "Work area issue
RETURNCODE = "Return code
UPDATE_FLAG = "User inputs yes/no ('X'/'' )

EXCEPTIONS
GET_NEXT_KEY_FAILED = 1 INVALID_STATUS = 2 NOT_FOUND = 3
.



IMPORTING Parameters details for ADDRESS_MAINTAIN

ADRSWA_IN - Work area entry.

Data type: SADR
Optional: No
Call by Reference: No ( called with pass by value option)

KENNZEICHEN - Keep or delete address data

Data type: SADR-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PROCESSING_STATUS - Status of processing

Data type:
Default: 'D'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAVE_INTERN - Save externally or internally

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TITLE -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ADDRESS_MAINTAIN

ADRSWA_OUT - Work area issue

Data type: SADR
Optional: No
Call by Reference: No ( called with pass by value option)

RETURNCODE - Return code

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_FLAG - User inputs yes/no ('X'/'' )

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

GET_NEXT_KEY_FAILED - Overflow in number range allocatio

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_STATUS - PROCESSING_STATUS has incorrect va

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_FOUND - Address not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ADDRESS_MAINTAIN 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_adrswa_in  TYPE SADR, "   
lv_adrswa_out  TYPE SADR, "   
lv_get_next_key_failed  TYPE SADR, "   
lv_returncode  TYPE SADR, "   
lv_kennzeichen  TYPE SADR-FLAG, "   SPACE
lv_invalid_status  TYPE SADR, "   
lv_object  TYPE SADR, "   SPACE
lv_not_found  TYPE SADR, "   
lv_update_flag  TYPE SADR, "   
lv_processing_status  TYPE SADR, "   'D'
lv_save_intern  TYPE SADR, "   SPACE
lv_title  TYPE SADR. "   SPACE

  CALL FUNCTION 'ADDRESS_MAINTAIN'  "
    EXPORTING
         ADRSWA_IN = lv_adrswa_in
         KENNZEICHEN = lv_kennzeichen
         OBJECT = lv_object
         PROCESSING_STATUS = lv_processing_status
         SAVE_INTERN = lv_save_intern
         TITLE = lv_title
    IMPORTING
         ADRSWA_OUT = lv_adrswa_out
         RETURNCODE = lv_returncode
         UPDATE_FLAG = lv_update_flag
    EXCEPTIONS
        GET_NEXT_KEY_FAILED = 1
        INVALID_STATUS = 2
        NOT_FOUND = 3
. " ADDRESS_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM ADDRESS_MAINTAIN

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 FLAG FROM SADR INTO @DATA(ld_kennzeichen).
DATA(ld_kennzeichen) = ' '.
 
 
DATA(ld_object) = ' '.
 
 
 
DATA(ld_processing_status) = 'D'.
 
DATA(ld_save_intern) = ' '.
 
DATA(ld_title) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!