SAP SM_OM_SAVE_DATA Function Module for
SM_OM_SAVE_DATA is a standard sm om save data 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 sm om save data FM, simply by entering the name SM_OM_SAVE_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: SMAPOM
Program Name: SAPLSMAPOM
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SM_OM_SAVE_DATA 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 'SM_OM_SAVE_DATA'".
EXPORTING
LS_KEY = "
LS_ADD_KEY = "
LS_APPL = "
IMPORTING
LD_RC = "
IMPORTING Parameters details for SM_OM_SAVE_DATA
LS_KEY -
Data type: SCHEDMAN_KEYOptional: No
Call by Reference: Yes
LS_ADD_KEY -
Data type: SCHEDMAN_ADD_KEYOptional: No
Call by Reference: Yes
LS_APPL -
Data type: SCHEDMAN_SPECIFIC_COOMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SM_OM_SAVE_DATA
LD_RC -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SM_OM_SAVE_DATA 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_ld_rc | TYPE SY-SUBRC, " | |||
| lv_ls_key | TYPE SCHEDMAN_KEY, " | |||
| lv_ls_add_key | TYPE SCHEDMAN_ADD_KEY, " | |||
| lv_ls_appl | TYPE SCHEDMAN_SPECIFIC_COOM. " |
|   CALL FUNCTION 'SM_OM_SAVE_DATA' " |
| EXPORTING | ||
| LS_KEY | = lv_ls_key | |
| LS_ADD_KEY | = lv_ls_add_key | |
| LS_APPL | = lv_ls_appl | |
| IMPORTING | ||
| LD_RC | = lv_ld_rc | |
| . " SM_OM_SAVE_DATA | ||
ABAP code using 7.40 inline data declarations to call FM SM_OM_SAVE_DATA
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 SUBRC FROM SY INTO @DATA(ld_ld_rc). | ||||
Search for further information about these or an SAP related objects