SAP LXE_ENQUEUE_DEQ_WRKLOCK Function Module for WRKLOCK dequeue









LXE_ENQUEUE_DEQ_WRKLOCK is a standard lxe enqueue deq wrklock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for WRKLOCK dequeue 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 lxe enqueue deq wrklock FM, simply by entering the name LXE_ENQUEUE_DEQ_WRKLOCK into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_ENQUEUE_DEQ_WRKLOCK 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 'LXE_ENQUEUE_DEQ_WRKLOCK'"WRKLOCK dequeue
EXPORTING
* MODE_LXE_WRKLOCK = 'E' "Lock mode
* TARGETLANG = "Translation Language
* CUSTMNR = "Translation Area
* OBJTYPE = "Type of Translation Object
* OBJNAME = "Name of Translation Object
* _SCOPE = '3' "
* _SYNCHRON = ' ' "
.



IMPORTING Parameters details for LXE_ENQUEUE_DEQ_WRKLOCK

MODE_LXE_WRKLOCK - Lock mode

Data type: ENQMODE
Default: 'E'
Optional: Yes
Call by Reference: Yes

TARGETLANG - Translation Language

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

CUSTMNR - Translation Area

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

OBJTYPE - Type of Translation Object

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

OBJNAME - Name of Translation Object

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

_SCOPE -

Data type:
Default: '3'
Optional: Yes
Call by Reference: Yes

_SYNCHRON -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LXE_ENQUEUE_DEQ_WRKLOCK 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_mode_lxe_wrklock  TYPE ENQMODE, "   'E'
lv_targetlang  TYPE LXEISOLANG, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_objname  TYPE LXEOBJNAME, "   
lv__scope  TYPE LXEOBJNAME, "   '3'
lv__synchron  TYPE LXEOBJNAME. "   SPACE

  CALL FUNCTION 'LXE_ENQUEUE_DEQ_WRKLOCK'  "WRKLOCK dequeue
    EXPORTING
         MODE_LXE_WRKLOCK = lv_mode_lxe_wrklock
         TARGETLANG = lv_targetlang
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         OBJNAME = lv_objname
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " LXE_ENQUEUE_DEQ_WRKLOCK




ABAP code using 7.40 inline data declarations to call FM LXE_ENQUEUE_DEQ_WRKLOCK

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.

DATA(ld_mode_lxe_wrklock) = 'E'.
 
 
 
 
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 


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!