SAP UPP_SSHEET_COMMIT Function Module for write to buffer
UPP_SSHEET_COMMIT is a standard upp ssheet 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 write to buffer 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 upp ssheet commit FM, simply by entering the name UPP_SSHEET_COMMIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPP_FRONT_SPREADS
Program Name: SAPLUPP_FRONT_SPREADS
Main Program: SAPLUPP_FRONT_SPREADS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPP_SSHEET_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 'UPP_SSHEET_COMMIT'"write to buffer.
EXPORTING
I_HNDL = "Planning Processor: Handle for Context
IMPORTING
ET_MESG = "Messages
EXCEPTIONS
NO_INSTANCE = 1 FAILED = 2
IMPORTING Parameters details for UPP_SSHEET_COMMIT
I_HNDL - Planning Processor: Handle for Context
Data type: UPP_Y_PP_HNDLOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UPP_SSHEET_COMMIT
ET_MESG - Messages
Data type: UPC_YT_MESGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_INSTANCE - no instance
Data type:Optional: No
Call by Reference: Yes
FAILED - Commit error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPP_SSHEET_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_i_hndl | TYPE UPP_Y_PP_HNDL, " | |||
| lv_et_mesg | TYPE UPC_YT_MESG, " | |||
| lv_no_instance | TYPE UPC_YT_MESG, " | |||
| lv_failed | TYPE UPC_YT_MESG. " |
|   CALL FUNCTION 'UPP_SSHEET_COMMIT' "write to buffer |
| EXPORTING | ||
| I_HNDL | = lv_i_hndl | |
| IMPORTING | ||
| ET_MESG | = lv_et_mesg | |
| EXCEPTIONS | ||
| NO_INSTANCE = 1 | ||
| FAILED = 2 | ||
| . " UPP_SSHEET_COMMIT | ||
ABAP code using 7.40 inline data declarations to call FM UPP_SSHEET_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