SAP DEQUEUE_E_IODIR Function Module for Release lock on object E_IODIR









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

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



Function DEQUEUE_E_IODIR 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_IODIR'"Release lock on object E_IODIR
  EXPORTING
*  MODE_IODIR = 'E' "Lock mode for table IODIR
*  _COLLECT = ' ' "Initially only collect lock
*  PGMID =  "01th enqueue argument
*  OBJECT =  "02th enqueue argument
*  OBJ_NAME =  "03th enqueue argument
*  X_PGMID = ' ' "Fill argument 01 with initial value?
*  X_OBJECT = ' ' "Fill argument 02 with initial value?
*  X_OBJ_NAME = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
.



IMPORTING Parameters details for DEQUEUE_E_IODIR

MODE_IODIR - Lock mode for table IODIR

Data type: ENQMODE
Default: 'E'
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)

PGMID - 01th enqueue argument

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

OBJECT - 02th enqueue argument

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

OBJ_NAME - 03th enqueue argument

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

X_PGMID - Fill argument 01 with initial value?

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

X_OBJECT - Fill argument 02 with initial value?

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

X_OBJ_NAME - 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)

Copy and paste ABAP code example for DEQUEUE_E_IODIR 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_iodir  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_pgmid  TYPE IODIR-PGMID, "   
lv_object  TYPE IODIR-OBJECT, "   
lv_obj_name  TYPE IODIR-OBJ_NAME, "   
lv_x_pgmid  TYPE IODIR, "   SPACE
lv_x_object  TYPE IODIR, "   SPACE
lv_x_obj_name  TYPE IODIR, "   SPACE
lv__scope  TYPE IODIR, "   '3'
lv__synchron  TYPE IODIR. "   SPACE

  CALL FUNCTION 'DEQUEUE_E_IODIR'  "Release lock on object E_IODIR
    EXPORTING
         MODE_IODIR = lv_mode_iodir
         _COLLECT = lv__collect
         PGMID = lv_pgmid
         OBJECT = lv_object
         OBJ_NAME = lv_obj_name
         X_PGMID = lv_x_pgmid
         X_OBJECT = lv_x_object
         X_OBJ_NAME = lv_x_obj_name
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
. " DEQUEUE_E_IODIR




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_IODIR

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_iodir) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single PGMID FROM IODIR INTO @DATA(ld_pgmid).
 
"SELECT single OBJECT FROM IODIR INTO @DATA(ld_object).
 
"SELECT single OBJ_NAME FROM IODIR INTO @DATA(ld_obj_name).
 
DATA(ld_x_pgmid) = ' '.
 
DATA(ld_x_object) = ' '.
 
DATA(ld_x_obj_name) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 


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!