SAP DEQUEUE_EDICONFIG Function Module for









DEQUEUE_EDICONFIG is a standard dequeue ediconfig SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ediconfig FM, simply by entering the name DEQUEUE_EDICONFIG into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_EDICONFIG 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_EDICONFIG'"
EXPORTING
* MODE_EDICONFIG = 'E' "Lock mode for table EDICONFIG
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* UNAME = "02th enqueue argument
* EDI_PROG = "03th enqueue argument
* EDI_PARAM = "04th enqueue argument
* X_UNAME = ' ' "Fill argument 02 with initial value?
* X_EDI_PROG = ' ' "Fill argument 03 with initial value?
* X_EDI_PARAM = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_EDICONFIG

MODE_EDICONFIG - Lock mode for table EDICONFIG

Data type: DD26E-ENQMODE
Default: 'E'
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: DDENQ_LIKE-COLLECT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDT - 01th enqueue argument

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

UNAME - 02th enqueue argument

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

EDI_PROG - 03th enqueue argument

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

EDI_PARAM - 04th enqueue argument

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

X_UNAME - Fill argument 02 with initial value?

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

X_EDI_PROG - Fill argument 03 with initial value?

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

X_EDI_PARAM - 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: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DEQUEUE_EDICONFIG 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_ediconfig  TYPE DD26E-ENQMODE, "   'E'
lv__synchron  TYPE DD26E, "   SPACE
lv__collect  TYPE DDENQ_LIKE-COLLECT, "   ' '
lv_mandt  TYPE EDICONFIG-MANDT, "   SY-MANDT
lv_uname  TYPE EDICONFIG-UNAME, "   
lv_edi_prog  TYPE EDICONFIG-EDI_PROG, "   
lv_edi_param  TYPE EDICONFIG-EDI_PARAM, "   
lv_x_uname  TYPE EDICONFIG, "   SPACE
lv_x_edi_prog  TYPE EDICONFIG, "   SPACE
lv_x_edi_param  TYPE EDICONFIG, "   SPACE
lv__scope  TYPE EDICONFIG. "   '3'

  CALL FUNCTION 'DEQUEUE_EDICONFIG'  "
    EXPORTING
         MODE_EDICONFIG = lv_mode_ediconfig
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         UNAME = lv_uname
         EDI_PROG = lv_edi_prog
         EDI_PARAM = lv_edi_param
         X_UNAME = lv_x_uname
         X_EDI_PROG = lv_x_edi_prog
         X_EDI_PARAM = lv_x_edi_param
         _SCOPE = lv__scope
. " DEQUEUE_EDICONFIG




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EDICONFIG

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.

"SELECT single ENQMODE FROM DD26E INTO @DATA(ld_mode_ediconfig).
DATA(ld_mode_ediconfig) = 'E'.
 
DATA(ld__synchron) = ' '.
 
"SELECT single COLLECT FROM DDENQ_LIKE INTO @DATA(ld__collect).
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM EDICONFIG INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single UNAME FROM EDICONFIG INTO @DATA(ld_uname).
 
"SELECT single EDI_PROG FROM EDICONFIG INTO @DATA(ld_edi_prog).
 
"SELECT single EDI_PARAM FROM EDICONFIG INTO @DATA(ld_edi_param).
 
DATA(ld_x_uname) = ' '.
 
DATA(ld_x_edi_prog) = ' '.
 
DATA(ld_x_edi_param) = ' '.
 
DATA(ld__scope) = '3'.
 


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!