SAP DEQUEUE_E_POOL Function Module for Release lock on object E_POOL









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

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



Function DEQUEUE_E_POOL 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_POOL'"Release lock on object E_POOL
  EXPORTING
*  MODE_TRET_SEC_POOL = 'E' "Lock mode for table TRET_SEC_POOL
*  MANDT = SY-MANDT "01th enqueue argument
*  SECURITY_ID =  "02th enqueue argument
*  COMPANY_CODE =  "03th enqueue argument
*  X_SECURITY_ID = ' ' "Fill argument 02 with initial value?
*  X_COMPANY_CODE = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_E_POOL

MODE_TRET_SEC_POOL - Lock mode for table TRET_SEC_POOL

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

MANDT - 01th enqueue argument

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

SECURITY_ID - 02th enqueue argument

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

COMPANY_CODE - 03th enqueue argument

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

X_SECURITY_ID - Fill argument 02 with initial value?

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

X_COMPANY_CODE - Fill argument 03 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_POOL 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_tret_sec_pool  TYPE ENQMODE, "   'E'
lv_mandt  TYPE TRET_SEC_POOL-MANDT, "   SY-MANDT
lv_security_id  TYPE TRET_SEC_POOL-SECURITY_ID, "   
lv_company_code  TYPE TRET_SEC_POOL-COMPANY_CODE, "   
lv_x_security_id  TYPE TRET_SEC_POOL, "   SPACE
lv_x_company_code  TYPE TRET_SEC_POOL, "   SPACE
lv__scope  TYPE TRET_SEC_POOL, "   '3'
lv__synchron  TYPE TRET_SEC_POOL, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_E_POOL'  "Release lock on object E_POOL
    EXPORTING
         MODE_TRET_SEC_POOL = lv_mode_tret_sec_pool
         MANDT = lv_mandt
         SECURITY_ID = lv_security_id
         COMPANY_CODE = lv_company_code
         X_SECURITY_ID = lv_x_security_id
         X_COMPANY_CODE = lv_x_company_code
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_E_POOL




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_POOL

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_tret_sec_pool) = 'E'.
 
"SELECT single MANDT FROM TRET_SEC_POOL INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single SECURITY_ID FROM TRET_SEC_POOL INTO @DATA(ld_security_id).
 
"SELECT single COMPANY_CODE FROM TRET_SEC_POOL INTO @DATA(ld_company_code).
 
DATA(ld_x_security_id) = ' '.
 
DATA(ld_x_company_code) = ' '.
 
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!