SAP UPP_PLAN_COMMIT Function Module for Planning: Commit of the detail application









UPP_PLAN_COMMIT is a standard upp plan 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 Planning: Commit of the detail application 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 plan commit FM, simply by entering the name UPP_PLAN_COMMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: UPP_PLAN
Program Name: SAPLUPP_PLAN
Main Program: SAPLUPP_PLAN
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function UPP_PLAN_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_PLAN_COMMIT'"Planning: Commit of the detail application
EXPORTING
I_CANCEL = "Flag for 'cancel' event in framework

IMPORTING
ET_MESG = "Message Table
E_CHANGED_TRANSACTION_DATA = "Single-Character Flag
ES_COMMIT_EXEC = "Executing a Planning Function with Commit in FW

EXCEPTIONS
ERROR_COMMIT = 1
.



IMPORTING Parameters details for UPP_PLAN_COMMIT

I_CANCEL - Flag for 'cancel' event in framework

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

EXPORTING Parameters details for UPP_PLAN_COMMIT

ET_MESG - Message Table

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

E_CHANGED_TRANSACTION_DATA - Single-Character Flag

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

ES_COMMIT_EXEC - Executing a Planning Function with Commit in FW

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

EXCEPTIONS details

ERROR_COMMIT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPP_PLAN_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_et_mesg  TYPE UPC_YT_MESG, "   
lv_i_cancel  TYPE CHAR1, "   
lv_error_commit  TYPE CHAR1, "   
lv_e_changed_transaction_data  TYPE CHAR1, "   
lv_es_commit_exec  TYPE UPC_YS_COMMIT_EXEC. "   

  CALL FUNCTION 'UPP_PLAN_COMMIT'  "Planning: Commit of the detail application
    EXPORTING
         I_CANCEL = lv_i_cancel
    IMPORTING
         ET_MESG = lv_et_mesg
         E_CHANGED_TRANSACTION_DATA = lv_e_changed_transaction_data
         ES_COMMIT_EXEC = lv_es_commit_exec
    EXCEPTIONS
        ERROR_COMMIT = 1
. " UPP_PLAN_COMMIT




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



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!