SAP DEQUEUE_EJGVSG Function Module for Release lock on object EJGVSG
DEQUEUE_EJGVSG is a standard dequeue ejgvsg 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 EJGVSG 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 ejgvsg FM, simply by entering the name DEQUEUE_EJGVSG into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/JEN0002
Program Name: /1BCDWBEN/SAPLJEN0002
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function DEQUEUE_EJGVSG 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_EJGVSG'"Release lock on object EJGVSG.
EXPORTING
* MODE_JGTVSG = 'E' "Lock mode for table JGTVSG
* MANDT = SY-MANDT "01th enqueue argument
* VERSERVGES = "02th enqueue argument
* X_VERSERVGES = ' ' "Fill argument 02 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
IMPORTING Parameters details for DEQUEUE_EJGVSG
MODE_JGTVSG - Lock mode for table JGTVSG
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - 01th enqueue argument
Data type: JGTVSG-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
VERSERVGES - 02th enqueue argument
Data type: JGTVSG-VERSERVGESOptional: Yes
Call by Reference: No ( called with pass by value option)
X_VERSERVGES - 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: DDENQCOLLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DEQUEUE_EJGVSG 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_jgtvsg | TYPE ENQMODE, " 'E' | |||
lv_mandt | TYPE JGTVSG-MANDT, " SY-MANDT | |||
lv_verservges | TYPE JGTVSG-VERSERVGES, " | |||
lv_x_verservges | TYPE JGTVSG, " SPACE | |||
lv__scope | TYPE JGTVSG, " '3' | |||
lv__synchron | TYPE JGTVSG, " SPACE | |||
lv__collect | TYPE DDENQCOLL. " ' ' |
  CALL FUNCTION 'DEQUEUE_EJGVSG' "Release lock on object EJGVSG |
EXPORTING | ||
MODE_JGTVSG | = lv_mode_jgtvsg | |
MANDT | = lv_mandt | |
VERSERVGES | = lv_verservges | |
X_VERSERVGES | = lv_x_verservges | |
_SCOPE | = lv__scope | |
_SYNCHRON | = lv__synchron | |
_COLLECT | = lv__collect | |
. " DEQUEUE_EJGVSG |
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EJGVSG
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_jgtvsg) | = 'E'. | |||
"SELECT single MANDT FROM JGTVSG INTO @DATA(ld_mandt). | ||||
DATA(ld_mandt) | = SY-MANDT. | |||
"SELECT single VERSERVGES FROM JGTVSG INTO @DATA(ld_verservges). | ||||
DATA(ld_x_verservges) | = ' '. | |||
DATA(ld__scope) | = '3'. | |||
DATA(ld__synchron) | = ' '. | |||
DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects