SAP CBIH_LB39_UE_PRE_COMMIT Function Module for









CBIH_LB39_UE_PRE_COMMIT is a standard cbih lb39 ue pre commit 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 cbih lb39 ue pre commit FM, simply by entering the name CBIH_LB39_UE_PRE_COMMIT into the relevant SAP transaction such as SE37 or SE38.

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



Function CBIH_LB39_UE_PRE_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 'CBIH_LB39_UE_PRE_COMMIT'"
EXPORTING
I_VALDAT = "
I_AENNR = "

IMPORTING
E_FLG_ABORT_SAVE = "

TABLES
I_IOT = "
* E_ERROR_TAB = "
.



IMPORTING Parameters details for CBIH_LB39_UE_PRE_COMMIT

I_VALDAT -

Data type: RCGADDINF-VALDAT
Optional: No
Call by Reference: Yes

I_AENNR -

Data type: RCGADDINF-AENNR
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CBIH_LB39_UE_PRE_COMMIT

E_FLG_ABORT_SAVE -

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

TABLES Parameters details for CBIH_LB39_UE_PRE_COMMIT

I_IOT -

Data type:
Optional: No
Call by Reference: Yes

E_ERROR_TAB -

Data type: RCGEXTERROR
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CBIH_LB39_UE_PRE_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:
lt_i_iot  TYPE STANDARD TABLE OF STRING, "   
lv_i_valdat  TYPE RCGADDINF-VALDAT, "   
lv_e_flg_abort_save  TYPE ESP1_BOOLEAN, "   
lv_i_aennr  TYPE RCGADDINF-AENNR, "   
lt_e_error_tab  TYPE STANDARD TABLE OF RCGEXTERROR. "   

  CALL FUNCTION 'CBIH_LB39_UE_PRE_COMMIT'  "
    EXPORTING
         I_VALDAT = lv_i_valdat
         I_AENNR = lv_i_aennr
    IMPORTING
         E_FLG_ABORT_SAVE = lv_e_flg_abort_save
    TABLES
         I_IOT = lt_i_iot
         E_ERROR_TAB = lt_e_error_tab
. " CBIH_LB39_UE_PRE_COMMIT




ABAP code using 7.40 inline data declarations to call FM CBIH_LB39_UE_PRE_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 VALDAT FROM RCGADDINF INTO @DATA(ld_i_valdat).
 
 
"SELECT single AENNR FROM RCGADDINF INTO @DATA(ld_i_aennr).
 
 


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!