SAP DEQUEUE_EFVIMI26 Function Module for









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

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



Function DEQUEUE_EFVIMI26 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_EFVIMI26'"
EXPORTING
* MODE_VIMI26 = 'E' "
* X_SWENR = ' ' "
* X_SMENR = ' ' "
* X_DKUEZU = ' ' "
* _SCOPE = '3' "
* _SYNCHRON = ' ' "
* _COLLECT = ' ' "
* MANDT = SY-MANDT "
* BUKRS = "
* SMIVE = "
* SWENR = "
* SMENR = "
* DKUEZU = "
* X_BUKRS = ' ' "
* X_SMIVE = ' ' "
.



IMPORTING Parameters details for DEQUEUE_EFVIMI26

MODE_VIMI26 -

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

X_SWENR -

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

X_SMENR -

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

X_DKUEZU -

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: VIMI26-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

BUKRS -

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

SMIVE -

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

SWENR -

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

SMENR -

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

DKUEZU -

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

X_BUKRS -

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

X_SMIVE -

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

Copy and paste ABAP code example for DEQUEUE_EFVIMI26 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_vimi26  TYPE DD26E-ENQMODE, "   'E'
lv_x_swenr  TYPE DD26E, "   SPACE
lv_x_smenr  TYPE DD26E, "   SPACE
lv_x_dkuezu  TYPE DD26E, "   SPACE
lv__scope  TYPE DD26E, "   '3'
lv__synchron  TYPE DD26E, "   SPACE
lv__collect  TYPE DDENQ_LIKE-COLLECT, "   ' '
lv_mandt  TYPE VIMI26-MANDT, "   SY-MANDT
lv_bukrs  TYPE VIMI26-BUKRS, "   
lv_smive  TYPE VIMI26-SMIVE, "   
lv_swenr  TYPE VIMI26-SWENR, "   
lv_smenr  TYPE VIMI26-SMENR, "   
lv_dkuezu  TYPE VIMI26-DKUEZU, "   
lv_x_bukrs  TYPE VIMI26, "   SPACE
lv_x_smive  TYPE VIMI26. "   SPACE

  CALL FUNCTION 'DEQUEUE_EFVIMI26'  "
    EXPORTING
         MODE_VIMI26 = lv_mode_vimi26
         X_SWENR = lv_x_swenr
         X_SMENR = lv_x_smenr
         X_DKUEZU = lv_x_dkuezu
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         BUKRS = lv_bukrs
         SMIVE = lv_smive
         SWENR = lv_swenr
         SMENR = lv_smenr
         DKUEZU = lv_dkuezu
         X_BUKRS = lv_x_bukrs
         X_SMIVE = lv_x_smive
. " DEQUEUE_EFVIMI26




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EFVIMI26

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_vimi26).
DATA(ld_mode_vimi26) = 'E'.
 
DATA(ld_x_swenr) = ' '.
 
DATA(ld_x_smenr) = ' '.
 
DATA(ld_x_dkuezu) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
"SELECT single COLLECT FROM DDENQ_LIKE INTO @DATA(ld__collect).
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM VIMI26 INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single BUKRS FROM VIMI26 INTO @DATA(ld_bukrs).
 
"SELECT single SMIVE FROM VIMI26 INTO @DATA(ld_smive).
 
"SELECT single SWENR FROM VIMI26 INTO @DATA(ld_swenr).
 
"SELECT single SMENR FROM VIMI26 INTO @DATA(ld_smenr).
 
"SELECT single DKUEZU FROM VIMI26 INTO @DATA(ld_dkuezu).
 
DATA(ld_x_bukrs) = ' '.
 
DATA(ld_x_smive) = ' '.
 


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!