SAP /SRMSMC/EXTN_SAVE_LAYOUT Function Module for Saves the layout of the current enhancement area
/SRMSMC/EXTN_SAVE_LAYOUT is a standard /srmsmc/extn save layout SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Saves the layout of the current enhancement area 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 /srmsmc/extn save layout FM, simply by entering the name /SRMSMC/EXTN_SAVE_LAYOUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SRMSMC/EXTN_DB
Program Name: /SRMSMC/SAPLEXTN_DB
Main Program: /SRMSMC/SAPLEXTN_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SRMSMC/EXTN_SAVE_LAYOUT 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 '/SRMSMC/EXTN_SAVE_LAYOUT'"Saves the layout of the current enhancement area.
EXPORTING
IV_CONFIG_ID = "Extension Configuration ID
IV_PACKAGE = "Package for UI Extension Configuration
IV_ON_REQUEST = "Is this object already on a transport
IV_TRKORR = "Correction request
IS_EXT_KEY = "UI Extension Key
TABLES
CT_EXT_UIEL = "Location of SFG
CT_EXT_PROP = "Semantic Field Group Properties
CT_EXT_UIEL_DEL = "Location of SFG
CT_EXT_PROP_DEL = "Semantic Field Group Properties
CT_MESSAGES = "Return Parameter
IMPORTING Parameters details for /SRMSMC/EXTN_SAVE_LAYOUT
IV_CONFIG_ID - Extension Configuration ID
Data type: /SRMSMC/EXTN_CONFIG_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_PACKAGE - Package for UI Extension Configuration
Data type: /SRMSMC/EXTN_DEVCOptional: No
Call by Reference: No ( called with pass by value option)
IV_ON_REQUEST - Is this object already on a transport
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
IV_TRKORR - Correction request
Data type: TRKORROptional: No
Call by Reference: No ( called with pass by value option)
IS_EXT_KEY - UI Extension Key
Data type: /SRMSMC/EXTN_KEYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /SRMSMC/EXTN_SAVE_LAYOUT
CT_EXT_UIEL - Location of SFG
Data type: /SRMSMC/EXTN_UIEOptional: No
Call by Reference: Yes
CT_EXT_PROP - Semantic Field Group Properties
Data type: /SRMSMC/EXTN_PROOptional: No
Call by Reference: Yes
CT_EXT_UIEL_DEL - Location of SFG
Data type: /SRMSMC/EXTN_UIEOptional: No
Call by Reference: Yes
CT_EXT_PROP_DEL - Semantic Field Group Properties
Data type: /SRMSMC/EXTN_PROOptional: No
Call by Reference: Yes
CT_MESSAGES - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /SRMSMC/EXTN_SAVE_LAYOUT 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: | ||||
| lt_ct_ext_uiel | TYPE STANDARD TABLE OF /SRMSMC/EXTN_UIE, " | |||
| lv_iv_config_id | TYPE /SRMSMC/EXTN_CONFIG_ID, " | |||
| lv_iv_package | TYPE /SRMSMC/EXTN_DEVC, " | |||
| lt_ct_ext_prop | TYPE STANDARD TABLE OF /SRMSMC/EXTN_PRO, " | |||
| lv_iv_on_request | TYPE BOOLE_D, " | |||
| lt_ct_ext_uiel_del | TYPE STANDARD TABLE OF /SRMSMC/EXTN_UIE, " | |||
| lv_iv_trkorr | TYPE TRKORR, " | |||
| lt_ct_ext_prop_del | TYPE STANDARD TABLE OF /SRMSMC/EXTN_PRO, " | |||
| lv_is_ext_key | TYPE /SRMSMC/EXTN_KEY, " | |||
| lt_ct_messages | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION '/SRMSMC/EXTN_SAVE_LAYOUT' "Saves the layout of the current enhancement area |
| EXPORTING | ||
| IV_CONFIG_ID | = lv_iv_config_id | |
| IV_PACKAGE | = lv_iv_package | |
| IV_ON_REQUEST | = lv_iv_on_request | |
| IV_TRKORR | = lv_iv_trkorr | |
| IS_EXT_KEY | = lv_is_ext_key | |
| TABLES | ||
| CT_EXT_UIEL | = lt_ct_ext_uiel | |
| CT_EXT_PROP | = lt_ct_ext_prop | |
| CT_EXT_UIEL_DEL | = lt_ct_ext_uiel_del | |
| CT_EXT_PROP_DEL | = lt_ct_ext_prop_del | |
| CT_MESSAGES | = lt_ct_messages | |
| . " /SRMSMC/EXTN_SAVE_LAYOUT | ||
ABAP code using 7.40 inline data declarations to call FM /SRMSMC/EXTN_SAVE_LAYOUT
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.Search for further information about these or an SAP related objects