SAP SATT_SAVE Function Module for









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

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



Function SATT_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 'SATT_SAVE'"
  EXPORTING
*  I_OBJTYP =  "Object Type of Reference Object for Attribute Repository
*  I_OBJID =  "Identifier of Reference Object for Attribute Repository
*  I_SAVE_AS_OBJTYP =  "
*  I_SAVE_AS_OBJID =  "
*  I_CHANGE_OBJID = 'X' "
*  I_SUBTYP =  "Subgroup of object types in the attribute repository
*  I_EXTKEY =  "
*  I_SAVE_AS_SUBTYP =  "Subgroup of object types in the attribute repository
*  I_SAVE_AS_EXTKEY =  "

 IMPORTING
   E_OBJTYP =  "
   E_OBJID =  "

EXCEPTIONS
   CANCELED = 1    ERROR = 2    ERROR_WRONG_OBJECT = 3
.



IMPORTING Parameters details for SATT_SAVE

I_OBJTYP - Object Type of Reference Object for Attribute Repository

Data type: ATOBJTYPE
Optional: Yes
Call by Reference: Yes

I_OBJID - Identifier of Reference Object for Attribute Repository

Data type: ATOBJ_NAME
Optional: Yes
Call by Reference: Yes

I_SAVE_AS_OBJTYP -

Data type: ATOBJTYPE
Optional: Yes
Call by Reference: Yes

I_SAVE_AS_OBJID -

Data type: ATOBJ_NAME
Optional: Yes
Call by Reference: Yes

I_CHANGE_OBJID -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_SUBTYP - Subgroup of object types in the attribute repository

Data type: ATSUBTYPE
Optional: Yes
Call by Reference: Yes

I_EXTKEY -

Data type: ANY
Optional: Yes
Call by Reference: Yes

I_SAVE_AS_SUBTYP - Subgroup of object types in the attribute repository

Data type: ATSUBTYPE
Optional: Yes
Call by Reference: Yes

I_SAVE_AS_EXTKEY -

Data type: ANY
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SATT_SAVE

E_OBJTYP -

Data type: ATOBJTYPE
Optional: No
Call by Reference: Yes

E_OBJID -

Data type: ATOBJ_NAME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CANCELED -

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

ERROR - General Error

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

ERROR_WRONG_OBJECT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SATT_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_canceled  TYPE STRING, "   
lv_e_objtyp  TYPE ATOBJTYPE, "   
lv_i_objtyp  TYPE ATOBJTYPE, "   
lv_error  TYPE ATOBJTYPE, "   
lv_e_objid  TYPE ATOBJ_NAME, "   
lv_i_objid  TYPE ATOBJ_NAME, "   
lv_i_save_as_objtyp  TYPE ATOBJTYPE, "   
lv_error_wrong_object  TYPE ATOBJTYPE, "   
lv_i_save_as_objid  TYPE ATOBJ_NAME, "   
lv_i_change_objid  TYPE CHAR1, "   'X'
lv_i_subtyp  TYPE ATSUBTYPE, "   
lv_i_extkey  TYPE ANY, "   
lv_i_save_as_subtyp  TYPE ATSUBTYPE, "   
lv_i_save_as_extkey  TYPE ANY. "   

  CALL FUNCTION 'SATT_SAVE'  "
    EXPORTING
         I_OBJTYP = lv_i_objtyp
         I_OBJID = lv_i_objid
         I_SAVE_AS_OBJTYP = lv_i_save_as_objtyp
         I_SAVE_AS_OBJID = lv_i_save_as_objid
         I_CHANGE_OBJID = lv_i_change_objid
         I_SUBTYP = lv_i_subtyp
         I_EXTKEY = lv_i_extkey
         I_SAVE_AS_SUBTYP = lv_i_save_as_subtyp
         I_SAVE_AS_EXTKEY = lv_i_save_as_extkey
    IMPORTING
         E_OBJTYP = lv_e_objtyp
         E_OBJID = lv_e_objid
    EXCEPTIONS
        CANCELED = 1
        ERROR = 2
        ERROR_WRONG_OBJECT = 3
. " SATT_SAVE




ABAP code using 7.40 inline data declarations to call FM SATT_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.

 
 
 
 
 
 
 
 
 
DATA(ld_i_change_objid) = 'X'.
 
 
 
 
 


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!