SAP DEQUEUE_E_TM_LOCK Function Module for Release lock on object E_TM_LOCK









DEQUEUE_E_TM_LOCK is a standard dequeue e tm lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release lock on object E_TM_LOCK 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 dequeue e tm lock FM, simply by entering the name DEQUEUE_E_TM_LOCK into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/CEN0017
Program Name: /1BCDWBEN/SAPLCEN0017
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DEQUEUE_E_TM_LOCK 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 'DEQUEUE_E_TM_LOCK'"Release lock on object E_TM_LOCK
  EXPORTING
*  MODE_CRMD_TM_LOCK = 'X' "Lock mode for table CRMD_TM_LOCK
*  CLIENT = SY-MANDT "Enqueue argument 01
*  PID =  "Enqueue argument 02
*  RESOURCE_ID =  "Enqueue argument 03
*  X_PID = ' ' "Fill argument 02 with initial value?
*  X_RESOURCE_ID = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_E_TM_LOCK

MODE_CRMD_TM_LOCK - Lock mode for table CRMD_TM_LOCK

Data type: ENQMODE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLIENT - Enqueue argument 01

Data type: CRMD_TM_LOCK-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PID - Enqueue argument 02

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

RESOURCE_ID - Enqueue argument 03

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

X_PID - Fill argument 02 with initial value?

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

X_RESOURCE_ID - Fill argument 03 with initial value?

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

_SCOPE -

Data type: DDENQSCOPE
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SYNCHRON - Synchonous unlock

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

_COLLECT - Initially only collect lock

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

Copy and paste ABAP code example for DEQUEUE_E_TM_LOCK 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_crmd_tm_lock  TYPE ENQMODE, "   'X'
lv_client  TYPE CRMD_TM_LOCK-CLIENT, "   SY-MANDT
lv_pid  TYPE CRMD_TM_LOCK-PID, "   
lv_resource_id  TYPE CRMD_TM_LOCK-RESOURCE_ID, "   
lv_x_pid  TYPE DDENQXPAR, "   SPACE
lv_x_resource_id  TYPE DDENQXPAR, "   SPACE
lv__scope  TYPE DDENQSCOPE, "   '3'
lv__synchron  TYPE DDENQSYNC, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_E_TM_LOCK'  "Release lock on object E_TM_LOCK
    EXPORTING
         MODE_CRMD_TM_LOCK = lv_mode_crmd_tm_lock
         CLIENT = lv_client
         PID = lv_pid
         RESOURCE_ID = lv_resource_id
         X_PID = lv_x_pid
         X_RESOURCE_ID = lv_x_resource_id
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_E_TM_LOCK




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_TM_LOCK

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_crmd_tm_lock) = 'X'.
 
"SELECT single CLIENT FROM CRMD_TM_LOCK INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single PID FROM CRMD_TM_LOCK INTO @DATA(ld_pid).
 
"SELECT single RESOURCE_ID FROM CRMD_TM_LOCK INTO @DATA(ld_resource_id).
 
DATA(ld_x_pid) = ' '.
 
DATA(ld_x_resource_id) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 


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!