SAP DEQUEUE_EJBDVTMD Function Module for Release lock on object EJBDVTMD









DEQUEUE_EJBDVTMD is a standard dequeue ejbdvtmd 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 EJBDVTMD 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 ejbdvtmd FM, simply by entering the name DEQUEUE_EJBDVTMD into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/JEN0000
Program Name: /1BCDWBEN/SAPLJEN0000
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DEQUEUE_EJBDVTMD 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_EJBDVTMD'"Release lock on object EJBDVTMD
EXPORTING
* MODE_JBDVTMD_LOCK = 'E' "Lock mode for table JBDVTMD_LOCK
* MANDT = SY-MANDT "01th enqueue argument
* COM_CODE = "02th enqueue argument
* VTNUM = "03th enqueue argument
* X_COM_CODE = ' ' "Fill argument 02 with initial value?
* X_VTNUM = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_EJBDVTMD

MODE_JBDVTMD_LOCK - Lock mode for table JBDVTMD_LOCK

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

MANDT - 01th enqueue argument

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

COM_CODE - 02th enqueue argument

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

VTNUM - 03th enqueue argument

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

X_COM_CODE - Fill argument 02 with initial value?

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

X_VTNUM - Fill argument 03 with initial value?

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

_SCOPE -

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

_SYNCHRON - Synchonous unlock

Data type:
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_EJBDVTMD 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_jbdvtmd_lock  TYPE ENQMODE, "   'E'
lv_mandt  TYPE JBDVTMD_LOCK-MANDT, "   SY-MANDT
lv_com_code  TYPE JBDVTMD_LOCK-COM_CODE, "   
lv_vtnum  TYPE JBDVTMD_LOCK-VTNUM, "   
lv_x_com_code  TYPE JBDVTMD_LOCK, "   SPACE
lv_x_vtnum  TYPE JBDVTMD_LOCK, "   SPACE
lv__scope  TYPE JBDVTMD_LOCK, "   '3'
lv__synchron  TYPE JBDVTMD_LOCK, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_EJBDVTMD'  "Release lock on object EJBDVTMD
    EXPORTING
         MODE_JBDVTMD_LOCK = lv_mode_jbdvtmd_lock
         MANDT = lv_mandt
         COM_CODE = lv_com_code
         VTNUM = lv_vtnum
         X_COM_CODE = lv_x_com_code
         X_VTNUM = lv_x_vtnum
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_EJBDVTMD




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EJBDVTMD

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_jbdvtmd_lock) = 'E'.
 
"SELECT single MANDT FROM JBDVTMD_LOCK INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single COM_CODE FROM JBDVTMD_LOCK INTO @DATA(ld_com_code).
 
"SELECT single VTNUM FROM JBDVTMD_LOCK INTO @DATA(ld_vtnum).
 
DATA(ld_x_com_code) = ' '.
 
DATA(ld_x_vtnum) = ' '.
 
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!