SAP DEQUEUE_ESSGRABDS Function Module for Release lock on object ESSGRABDS









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

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



Function DEQUEUE_ESSGRABDS 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_ESSGRABDS'"Release lock on object ESSGRABDS
EXPORTING
* MODE_STXBITMAPS = 'E' "Lock mode for table STXBITMAPS
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* TDOBJECT = "01th enqueue argument
* TDNAME = "02th enqueue argument
* TDID = "03th enqueue argument
* TDBTYPE = "04th enqueue argument
* X_TDOBJECT = ' ' "Fill argument 01 with initial value?
* X_TDNAME = ' ' "Fill argument 02 with initial value?
* X_TDID = ' ' "Fill argument 03 with initial value?
* X_TDBTYPE = ' ' "Fill argument 04 with initial value?
.



IMPORTING Parameters details for DEQUEUE_ESSGRABDS

MODE_STXBITMAPS - Lock mode for table STXBITMAPS

Data type: ENQMODE
Default: 'E'
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)

TDOBJECT - 01th enqueue argument

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

TDNAME - 02th enqueue argument

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

TDID - 03th enqueue argument

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

TDBTYPE - 04th enqueue argument

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

X_TDOBJECT - Fill argument 01 with initial value?

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

X_TDNAME - Fill argument 02 with initial value?

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

X_TDID - Fill argument 03 with initial value?

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

X_TDBTYPE - Fill argument 04 with initial value?

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

Copy and paste ABAP code example for DEQUEUE_ESSGRABDS 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_stxbitmaps  TYPE ENQMODE, "   'E'
lv__scope  TYPE ENQMODE, "   '3'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_tdobject  TYPE STXBITMAPS-TDOBJECT, "   
lv_tdname  TYPE STXBITMAPS-TDNAME, "   
lv_tdid  TYPE STXBITMAPS-TDID, "   
lv_tdbtype  TYPE STXBITMAPS-TDBTYPE, "   
lv_x_tdobject  TYPE STXBITMAPS, "   SPACE
lv_x_tdname  TYPE STXBITMAPS, "   SPACE
lv_x_tdid  TYPE STXBITMAPS, "   SPACE
lv_x_tdbtype  TYPE STXBITMAPS. "   SPACE

  CALL FUNCTION 'DEQUEUE_ESSGRABDS'  "Release lock on object ESSGRABDS
    EXPORTING
         MODE_STXBITMAPS = lv_mode_stxbitmaps
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         TDOBJECT = lv_tdobject
         TDNAME = lv_tdname
         TDID = lv_tdid
         TDBTYPE = lv_tdbtype
         X_TDOBJECT = lv_x_tdobject
         X_TDNAME = lv_x_tdname
         X_TDID = lv_x_tdid
         X_TDBTYPE = lv_x_tdbtype
. " DEQUEUE_ESSGRABDS




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ESSGRABDS

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_stxbitmaps) = 'E'.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single TDOBJECT FROM STXBITMAPS INTO @DATA(ld_tdobject).
 
"SELECT single TDNAME FROM STXBITMAPS INTO @DATA(ld_tdname).
 
"SELECT single TDID FROM STXBITMAPS INTO @DATA(ld_tdid).
 
"SELECT single TDBTYPE FROM STXBITMAPS INTO @DATA(ld_tdbtype).
 
DATA(ld_x_tdobject) = ' '.
 
DATA(ld_x_tdname) = ' '.
 
DATA(ld_x_tdid) = ' '.
 
DATA(ld_x_tdbtype) = ' '.
 


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!