SAP DEQUEUE_ET863X Function Module for









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

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



Function DEQUEUE_ET863X 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_ET863X'"
EXPORTING
* MODE_T863X = 'E' "
* X_PEVON = ' ' "
* X_PEBIS = ' ' "
* X_RVERS = ' ' "
* _SCOPE = '3' "
* _SYNCHRON = ' ' "
* _COLLECT = ' ' "
* MANDT = SY-MANDT "
* RSUBD = "
* RYEAR = "
* PEVON = "
* PEBIS = "
* RVERS = "
* X_RSUBD = ' ' "
* X_RYEAR = ' ' "
.



IMPORTING Parameters details for DEQUEUE_ET863X

MODE_T863X -

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

X_PEVON -

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

X_PEBIS -

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

X_RVERS -

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 -

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

_COLLECT -

Data type: DDENQ_LIKE-COLLECT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDT -

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

RSUBD -

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

RYEAR -

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

PEVON -

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

PEBIS -

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

RVERS -

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

X_RSUBD -

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

X_RYEAR -

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

Copy and paste ABAP code example for DEQUEUE_ET863X 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_t863x  TYPE DD26E-ENQMODE, "   'E'
lv_x_pevon  TYPE DD26E, "   SPACE
lv_x_pebis  TYPE DD26E, "   SPACE
lv_x_rvers  TYPE DD26E, "   SPACE
lv__scope  TYPE DD26E, "   '3'
lv__synchron  TYPE DD26E, "   SPACE
lv__collect  TYPE DDENQ_LIKE-COLLECT, "   ' '
lv_mandt  TYPE T863X-MANDT, "   SY-MANDT
lv_rsubd  TYPE T863X-RSUBD, "   
lv_ryear  TYPE T863X-RYEAR, "   
lv_pevon  TYPE T863X-PEVON, "   
lv_pebis  TYPE T863X-PEBIS, "   
lv_rvers  TYPE T863X-RVERS, "   
lv_x_rsubd  TYPE T863X, "   SPACE
lv_x_ryear  TYPE T863X. "   SPACE

  CALL FUNCTION 'DEQUEUE_ET863X'  "
    EXPORTING
         MODE_T863X = lv_mode_t863x
         X_PEVON = lv_x_pevon
         X_PEBIS = lv_x_pebis
         X_RVERS = lv_x_rvers
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         RSUBD = lv_rsubd
         RYEAR = lv_ryear
         PEVON = lv_pevon
         PEBIS = lv_pebis
         RVERS = lv_rvers
         X_RSUBD = lv_x_rsubd
         X_RYEAR = lv_x_ryear
. " DEQUEUE_ET863X




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ET863X

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_t863x).
DATA(ld_mode_t863x) = 'E'.
 
DATA(ld_x_pevon) = ' '.
 
DATA(ld_x_pebis) = ' '.
 
DATA(ld_x_rvers) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
"SELECT single COLLECT FROM DDENQ_LIKE INTO @DATA(ld__collect).
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM T863X INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single RSUBD FROM T863X INTO @DATA(ld_rsubd).
 
"SELECT single RYEAR FROM T863X INTO @DATA(ld_ryear).
 
"SELECT single PEVON FROM T863X INTO @DATA(ld_pevon).
 
"SELECT single PEBIS FROM T863X INTO @DATA(ld_pebis).
 
"SELECT single RVERS FROM T863X INTO @DATA(ld_rvers).
 
DATA(ld_x_rsubd) = ' '.
 
DATA(ld_x_ryear) = ' '.
 


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!