SAP ENQUEUE_EPT5DBY Function Module for Request lock for object EPT5DBY









ENQUEUE_EPT5DBY is a standard enqueue ept5dby 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 EPT5DBY 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 ept5dby FM, simply by entering the name ENQUEUE_EPT5DBY into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_EPT5DBY 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_EPT5DBY'"Request lock for object EPT5DBY
EXPORTING
* MODE_T5DBY = 'E' "Lock mode for table T5DBY
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* ZVKAS = "02th enqueue argument
* RZNUM = "03th enqueue argument
* RZDAT = "04th enqueue argument
* X_ZVKAS = ' ' "Fill argument 02 with initial value?
* X_RZNUM = ' ' "Fill argument 03 with initial value?
* X_RZDAT = ' ' "Fill argument 04 with initial value?
* _SCOPE = '2' "

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_EPT5DBY

MODE_T5DBY - Lock mode for table T5DBY

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

_WAIT -

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)

MANDT - 01th enqueue argument

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

ZVKAS - 02th enqueue argument

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

RZNUM - 03th enqueue argument

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

RZDAT - 04th enqueue argument

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

X_ZVKAS - Fill argument 02 with initial value?

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

X_RZNUM - Fill argument 03 with initial value?

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

X_RZDAT - Fill argument 04 with initial value?

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

_SCOPE -

Data type:
Default: '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_EPT5DBY 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_t5dby  TYPE ENQMODE, "   'E'
lv_foreign_lock  TYPE ENQMODE, "   
lv__wait  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE T5DBY-MANDT, "   SY-MANDT
lv_system_failure  TYPE T5DBY, "   
lv_zvkas  TYPE T5DBY-ZVKAS, "   
lv_rznum  TYPE T5DBY-RZNUM, "   
lv_rzdat  TYPE T5DBY-RZDAT, "   
lv_x_zvkas  TYPE T5DBY, "   SPACE
lv_x_rznum  TYPE T5DBY, "   SPACE
lv_x_rzdat  TYPE T5DBY, "   SPACE
lv__scope  TYPE T5DBY. "   '2'

  CALL FUNCTION 'ENQUEUE_EPT5DBY'  "Request lock for object EPT5DBY
    EXPORTING
         MODE_T5DBY = lv_mode_t5dby
         _WAIT = lv__wait
         _COLLECT = lv__collect
         MANDT = lv_mandt
         ZVKAS = lv_zvkas
         RZNUM = lv_rznum
         RZDAT = lv_rzdat
         X_ZVKAS = lv_x_zvkas
         X_RZNUM = lv_x_rznum
         X_RZDAT = lv_x_rzdat
         _SCOPE = lv__scope
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_EPT5DBY




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_EPT5DBY

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_t5dby) = 'E'.
 
 
DATA(ld__wait) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM T5DBY INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single ZVKAS FROM T5DBY INTO @DATA(ld_zvkas).
 
"SELECT single RZNUM FROM T5DBY INTO @DATA(ld_rznum).
 
"SELECT single RZDAT FROM T5DBY INTO @DATA(ld_rzdat).
 
DATA(ld_x_zvkas) = ' '.
 
DATA(ld_x_rznum) = ' '.
 
DATA(ld_x_rzdat) = ' '.
 
DATA(ld__scope) = '2'.
 


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!