SAP ENQUEUE_E_VTBLS Function Module for Request lock for object E_VTBLS
ENQUEUE_E_VTBLS is a standard enqueue e vtbls SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object E_VTBLS 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 enqueue e vtbls FM, simply by entering the name ENQUEUE_E_VTBLS into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/FEN0005
Program Name: /1BCDWBEN/SAPLFEN0005
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function ENQUEUE_E_VTBLS 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 'ENQUEUE_E_VTBLS'"Request lock for object E_VTBLS.
EXPORTING
* MODE_VTBLS = 'E' "Lock mode for table VTBLS
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* SLA = "02th enqueue argument
* RLV = "03th enqueue argument
* SLH = "04th enqueue argument
* X_SLA = ' ' "Fill argument 02 with initial value?
* X_RLV = ' ' "Fill argument 03 with initial value?
* X_SLH = ' ' "Fill argument 04 with initial value?
* _SCOPE = '2' "
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for ENQUEUE_E_VTBLS
MODE_VTBLS - Lock mode for table VTBLS
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
_WAIT -
Data type: DDENQWAITDefault: 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)
MANDT - 01th enqueue argument
Data type: VTBLS-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
SLA - 02th enqueue argument
Data type: VTBLS-SLAOptional: Yes
Call by Reference: No ( called with pass by value option)
RLV - 03th enqueue argument
Data type: VTBLS-RLVOptional: Yes
Call by Reference: No ( called with pass by value option)
SLH - 04th enqueue argument
Data type: VTBLS-SLHOptional: Yes
Call by Reference: No ( called with pass by value option)
X_SLA - Fill argument 02 with initial value?
Data type: DDENQXPARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_RLV - Fill argument 03 with initial value?
Data type: DDENQXPARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_SLH - Fill argument 04 with initial value?
Data type: DDENQXPARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
_SCOPE -
Data type: DDENQSCOPEDefault: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK - Object already locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - Internal error from enqueue server
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ENQUEUE_E_VTBLS 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_vtbls | TYPE ENQMODE, " 'E' | |||
lv_foreign_lock | TYPE ENQMODE, " | |||
lv__wait | TYPE DDENQWAIT, " SPACE | |||
lv__collect | TYPE DDENQCOLL, " ' ' | |||
lv_mandt | TYPE VTBLS-MANDT, " SY-MANDT | |||
lv_system_failure | TYPE VTBLS, " | |||
lv_sla | TYPE VTBLS-SLA, " | |||
lv_rlv | TYPE VTBLS-RLV, " | |||
lv_slh | TYPE VTBLS-SLH, " | |||
lv_x_sla | TYPE DDENQXPAR, " SPACE | |||
lv_x_rlv | TYPE DDENQXPAR, " SPACE | |||
lv_x_slh | TYPE DDENQXPAR, " SPACE | |||
lv__scope | TYPE DDENQSCOPE. " '2' |
  CALL FUNCTION 'ENQUEUE_E_VTBLS' "Request lock for object E_VTBLS |
EXPORTING | ||
MODE_VTBLS | = lv_mode_vtbls | |
_WAIT | = lv__wait | |
_COLLECT | = lv__collect | |
MANDT | = lv_mandt | |
SLA | = lv_sla | |
RLV | = lv_rlv | |
SLH | = lv_slh | |
X_SLA | = lv_x_sla | |
X_RLV | = lv_x_rlv | |
X_SLH | = lv_x_slh | |
_SCOPE | = lv__scope | |
EXCEPTIONS | ||
FOREIGN_LOCK = 1 | ||
SYSTEM_FAILURE = 2 | ||
. " ENQUEUE_E_VTBLS |
ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_VTBLS
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_vtbls) | = 'E'. | |||
DATA(ld__wait) | = ' '. | |||
DATA(ld__collect) | = ' '. | |||
"SELECT single MANDT FROM VTBLS INTO @DATA(ld_mandt). | ||||
DATA(ld_mandt) | = SY-MANDT. | |||
"SELECT single SLA FROM VTBLS INTO @DATA(ld_sla). | ||||
"SELECT single RLV FROM VTBLS INTO @DATA(ld_rlv). | ||||
"SELECT single SLH FROM VTBLS INTO @DATA(ld_slh). | ||||
DATA(ld_x_sla) | = ' '. | |||
DATA(ld_x_rlv) | = ' '. | |||
DATA(ld_x_slh) | = ' '. | |||
DATA(ld__scope) | = '2'. | |||
Search for further information about these or an SAP related objects