SAP ADDR_CONTAINER_SAVE Function Module for









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

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



Function ADDR_CONTAINER_SAVE 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_CONTAINER_SAVE'"
EXPORTING
EXECUTE_IN_UPDATE_TASK = "Checkbox Field
INSERT_TAB = "Address Number Table
UPDATE_TAB = "Address Number Table
DELETE_TAB = "Address Number Table

EXCEPTIONS
INTERNAL_ERROR = 1 DATABASE_ERROR = 2
.



IMPORTING Parameters details for ADDR_CONTAINER_SAVE

EXECUTE_IN_UPDATE_TASK - Checkbox Field

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

INSERT_TAB - Address Number Table

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

UPDATE_TAB - Address Number Table

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

DELETE_TAB - Address Number Table

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

EXCEPTIONS details

INTERNAL_ERROR - Serious internal error

Data type:
Optional: No
Call by Reference: Yes

DATABASE_ERROR - Error writing to the database

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADDR_CONTAINER_SAVE 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_internal_error  TYPE STRING, "   
lv_execute_in_update_task  TYPE SZAD_FIELD-FLAG, "   
lv_insert_tab  TYPE AES_ADDRNUM_TABLE, "   
lv_database_error  TYPE AES_ADDRNUM_TABLE, "   
lv_update_tab  TYPE AES_ADDRNUM_TABLE, "   
lv_delete_tab  TYPE AES_ADDRNUM_TABLE. "   

  CALL FUNCTION 'ADDR_CONTAINER_SAVE'  "
    EXPORTING
         EXECUTE_IN_UPDATE_TASK = lv_execute_in_update_task
         INSERT_TAB = lv_insert_tab
         UPDATE_TAB = lv_update_tab
         DELETE_TAB = lv_delete_tab
    EXCEPTIONS
        INTERNAL_ERROR = 1
        DATABASE_ERROR = 2
. " ADDR_CONTAINER_SAVE




ABAP code using 7.40 inline data declarations to call FM ADDR_CONTAINER_SAVE

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 SZAD_FIELD INTO @DATA(ld_execute_in_update_task).
 
 
 
 
 


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!