SAP UCI_DE_ENQUEUE_1 Function Module for
UCI_DE_ENQUEUE_1 is a standard uci de enqueue 1 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 uci de enqueue 1 FM, simply by entering the name UCI_DE_ENQUEUE_1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: UCI1
Program Name: SAPLUCI1
Main Program: SAPLUCI1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UCI_DE_ENQUEUE_1 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 'UCI_DE_ENQUEUE_1'".
EXPORTING
I_INFOPROV = "InfoProvider
I_ENQMODE = "Lock Mode
I_T_RANGE = "
I_S_LOCK_INFO = "
IMPORTING
E_LOCK_HNDL = "UUID in compressed form (22 character UUENCODEd)
E_S_MSG = "Application Log: Message Data
EXCEPTIONS
ILLEGAL_RESTRICTIONS = 1 FOREIGN_LOCK = 2 FAILED = 3
IMPORTING Parameters details for UCI_DE_ENQUEUE_1
I_INFOPROV - InfoProvider
Data type: RSINFOPROVOptional: No
Call by Reference: Yes
I_ENQMODE - Lock Mode
Data type: ENQMODEOptional: No
Call by Reference: Yes
I_T_RANGE -
Data type: UGBW_T_RANGEOptional: No
Call by Reference: Yes
I_S_LOCK_INFO -
Data type: UGBW_S_LOCK_INFOOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UCI_DE_ENQUEUE_1
E_LOCK_HNDL - UUID in compressed form (22 character UUENCODEd)
Data type: SYSUUID_22Optional: No
Call by Reference: Yes
E_S_MSG - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
ILLEGAL_RESTRICTIONS - Incorrect Lock Area (Error in Restrictions)
Data type:Optional: No
Call by Reference: Yes
FOREIGN_LOCK - Locking Error
Data type:Optional: No
Call by Reference: Yes
FAILED - Problem with Lock Server
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UCI_DE_ENQUEUE_1 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_infoprov | TYPE RSINFOPROV, " | |||
| lv_e_lock_hndl | TYPE SYSUUID_22, " | |||
| lv_illegal_restrictions | TYPE SYSUUID_22, " | |||
| lv_e_s_msg | TYPE BAL_S_MSG, " | |||
| lv_i_enqmode | TYPE ENQMODE, " | |||
| lv_foreign_lock | TYPE ENQMODE, " | |||
| lv_failed | TYPE ENQMODE, " | |||
| lv_i_t_range | TYPE UGBW_T_RANGE, " | |||
| lv_i_s_lock_info | TYPE UGBW_S_LOCK_INFO. " |
|   CALL FUNCTION 'UCI_DE_ENQUEUE_1' " |
| EXPORTING | ||
| I_INFOPROV | = lv_i_infoprov | |
| I_ENQMODE | = lv_i_enqmode | |
| I_T_RANGE | = lv_i_t_range | |
| I_S_LOCK_INFO | = lv_i_s_lock_info | |
| IMPORTING | ||
| E_LOCK_HNDL | = lv_e_lock_hndl | |
| E_S_MSG | = lv_e_s_msg | |
| EXCEPTIONS | ||
| ILLEGAL_RESTRICTIONS = 1 | ||
| FOREIGN_LOCK = 2 | ||
| FAILED = 3 | ||
| . " UCI_DE_ENQUEUE_1 | ||
ABAP code using 7.40 inline data declarations to call FM UCI_DE_ENQUEUE_1
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