SAP CLOI_COMMIT Function Module for NOTRANSL: Perform commit which means save all changes (LOI)









CLOI_COMMIT is a standard cloi 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 NOTRANSL: Perform commit which means save all changes (LOI) 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 cloi commit FM, simply by entering the name CLOI_COMMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: LOI2
Program Name: SAPLLOI2
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CLOI_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 'CLOI_COMMIT'"NOTRANSL: Perform commit which means save all changes (LOI)
EXPORTING
* X_PLORD_OR_OPR_CHG = "
* X_ORD_OR_OPR_CHG = "
* X_EBAN_CHG = "

CHANGING
CLOI_SUCC_CODE = "

EXCEPTIONS
COMMIT_NOT_DONE = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLLOI2_001 User Exit for Function Module cloi_changes_upl_31

IMPORTING Parameters details for CLOI_COMMIT

X_PLORD_OR_OPR_CHG -

Data type: CLOI_X
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_ORD_OR_OPR_CHG -

Data type: CLOI_X
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_EBAN_CHG -

Data type: CLOI_X
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for CLOI_COMMIT

CLOI_SUCC_CODE -

Data type: METHOD_LOG-SUCC_CODE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

COMMIT_NOT_DONE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CLOI_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_cloi_succ_code  TYPE METHOD_LOG-SUCC_CODE, "   
lv_commit_not_done  TYPE METHOD_LOG, "   
lv_x_plord_or_opr_chg  TYPE CLOI_X, "   
lv_x_ord_or_opr_chg  TYPE CLOI_X, "   
lv_x_eban_chg  TYPE CLOI_X. "   

  CALL FUNCTION 'CLOI_COMMIT'  "NOTRANSL: Perform commit which means save all changes (LOI)
    EXPORTING
         X_PLORD_OR_OPR_CHG = lv_x_plord_or_opr_chg
         X_ORD_OR_OPR_CHG = lv_x_ord_or_opr_chg
         X_EBAN_CHG = lv_x_eban_chg
    CHANGING
         CLOI_SUCC_CODE = lv_cloi_succ_code
    EXCEPTIONS
        COMMIT_NOT_DONE = 1
. " CLOI_COMMIT




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

"SELECT single SUCC_CODE FROM METHOD_LOG INTO @DATA(ld_cloi_succ_code).
 
 
 
 
 


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!