SAP DEQUEUE_E_GLOSSAR Function Module for Release lock on object E_GLOSSAR









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

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



Function DEQUEUE_E_GLOSSAR 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_GLOSSAR'"Release lock on object E_GLOSSAR
  EXPORTING
*  MODE_GLOSSARY3 = 'E' "Lock mode for table GLOSSARY3
*  MODE_GLOSSARY1 = 'E' "Lock mode for table GLOSSARY1
*  GUID_GLOS =  "01th enqueue argument
*  GUID =  "02th enqueue argument
*  X_GUID_GLOS = ' ' "Fill argument 01 with initial value?
*  X_GUID = ' ' "Fill argument 02 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_E_GLOSSAR

MODE_GLOSSARY3 - Lock mode for table GLOSSARY3

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

MODE_GLOSSARY1 - Lock mode for table GLOSSARY1

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

GUID_GLOS - 01th enqueue argument

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

GUID - 02th enqueue argument

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

X_GUID_GLOS - Fill argument 01 with initial value?

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

X_GUID - Fill argument 02 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_E_GLOSSAR 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_glossary3  TYPE ENQMODE, "   'E'
lv_mode_glossary1  TYPE ENQMODE, "   'E'
lv_guid_glos  TYPE GLOSSARY3-GUID_GLOS, "   
lv_guid  TYPE GLOSSARY1-GUID, "   
lv_x_guid_glos  TYPE GLOSSARY1, "   SPACE
lv_x_guid  TYPE GLOSSARY1, "   SPACE
lv__scope  TYPE GLOSSARY1, "   '3'
lv__synchron  TYPE GLOSSARY1, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_E_GLOSSAR'  "Release lock on object E_GLOSSAR
    EXPORTING
         MODE_GLOSSARY3 = lv_mode_glossary3
         MODE_GLOSSARY1 = lv_mode_glossary1
         GUID_GLOS = lv_guid_glos
         GUID = lv_guid
         X_GUID_GLOS = lv_x_guid_glos
         X_GUID = lv_x_guid
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_E_GLOSSAR




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_GLOSSAR

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_glossary3) = 'E'.
 
DATA(ld_mode_glossary1) = 'E'.
 
"SELECT single GUID_GLOS FROM GLOSSARY3 INTO @DATA(ld_guid_glos).
 
"SELECT single GUID FROM GLOSSARY1 INTO @DATA(ld_guid).
 
DATA(ld_x_guid_glos) = ' '.
 
DATA(ld_x_guid) = ' '.
 
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!