SAP ICL_CVERM_UNI_ENQUEUE Function Module for Create lock entries for versioned tables









ICL_CVERM_UNI_ENQUEUE is a standard icl cverm uni enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create lock entries for versioned tables 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 icl cverm uni enqueue FM, simply by entering the name ICL_CVERM_UNI_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.

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



Function ICL_CVERM_UNI_ENQUEUE 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 'ICL_CVERM_UNI_ENQUEUE'"Create lock entries for versioned tables
EXPORTING
I_TABNAME = "
* I_MODE = "Single-Character Flag
* I_XNO_OBJ_CHECK = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

TABLES
T_KEYSEL = "

EXCEPTIONS
FOREIGN_LOCK = 1 LOCK_FAILURE = 2
.



IMPORTING Parameters details for ICL_CVERM_UNI_ENQUEUE

I_TABNAME -

Data type: DCOBJDEF-NAME
Optional: No
Call by Reference: Yes

I_MODE - Single-Character Flag

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

I_XNO_OBJ_CHECK - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

TABLES Parameters details for ICL_CVERM_UNI_ENQUEUE

T_KEYSEL -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

LOCK_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ICL_CVERM_UNI_ENQUEUE 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_t_keysel  TYPE STANDARD TABLE OF STRING, "   
lv_i_tabname  TYPE DCOBJDEF-NAME, "   
lv_foreign_lock  TYPE DCOBJDEF, "   
lv_i_mode  TYPE CHAR1, "   
lv_lock_failure  TYPE CHAR1, "   
lv_i_xno_obj_check  TYPE BOOLE_D. "   

  CALL FUNCTION 'ICL_CVERM_UNI_ENQUEUE'  "Create lock entries for versioned tables
    EXPORTING
         I_TABNAME = lv_i_tabname
         I_MODE = lv_i_mode
         I_XNO_OBJ_CHECK = lv_i_xno_obj_check
    TABLES
         T_KEYSEL = lt_t_keysel
    EXCEPTIONS
        FOREIGN_LOCK = 1
        LOCK_FAILURE = 2
. " ICL_CVERM_UNI_ENQUEUE




ABAP code using 7.40 inline data declarations to call FM ICL_CVERM_UNI_ENQUEUE

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 NAME FROM DCOBJDEF INTO @DATA(ld_i_tabname).
 
 
 
 
 


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!