SAP /MRSS/SGE_API_COMMIT Function Module for Function for Commiting API Changes
/MRSS/SGE_API_COMMIT is a standard /mrss/sge api commit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function for Commiting API Changes 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 /mrss/sge api commit FM, simply by entering the name /MRSS/SGE_API_COMMIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: /MRSS/SGE_API
Program Name: /MRSS/SAPLSGE_API
Main Program: /MRSS/SAPLSGE_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /MRSS/SGE_API_COMMIT 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 '/MRSS/SGE_API_COMMIT'"Function for Commiting API Changes.
IMPORTING
EV_FAILED = "Boolean Variable
ET_MESSAGES = "Table with Messages
EXPORTING Parameters details for /MRSS/SGE_API_COMMIT
EV_FAILED - Boolean Variable
Data type: /MRSS/T_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Table with Messages
Data type: /MRSS/T_MESSAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /MRSS/SGE_API_COMMIT 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_ev_failed | TYPE /MRSS/T_BOOLEAN, " | |||
| lv_et_messages | TYPE /MRSS/T_MESSAGE_TAB. " |
|   CALL FUNCTION '/MRSS/SGE_API_COMMIT' "Function for Commiting API Changes |
| IMPORTING | ||
| EV_FAILED | = lv_ev_failed | |
| ET_MESSAGES | = lv_et_messages | |
| . " /MRSS/SGE_API_COMMIT | ||
ABAP code using 7.40 inline data declarations to call FM /MRSS/SGE_API_COMMIT
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