SAP ENQUEUE_EVIBEWE Function Module for Request lock for object EVIBEWE









ENQUEUE_EVIBEWE is a standard enqueue evibewe SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object EVIBEWE 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 enqueue evibewe FM, simply by entering the name ENQUEUE_EVIBEWE into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_EVIBEWE 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 'ENQUEUE_EVIBEWE'"Request lock for object EVIBEWE
  EXPORTING
*  MODE_VIWEENQ = 'E' "Lock mode for table VIWEENQ
*  MANDT = SY-MANDT "01th enqueue argument
*  BUKRS =  "02th enqueue argument
*  SWENR =  "03th enqueue argument
*  X_BUKRS = ' ' "Fill argument 02 with initial value?
*  X_SWENR = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '2' "
*  _WAIT = ' ' "
*  _COLLECT = ' ' "Initially only collect lock

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_EVIBEWE

MODE_VIWEENQ - Lock mode for table VIWEENQ

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

MANDT - 01th enqueue argument

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

BUKRS - 02th enqueue argument

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

SWENR - 03th enqueue argument

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

X_BUKRS - Fill argument 02 with initial value?

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

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

_WAIT -

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)

EXCEPTIONS details

FOREIGN_LOCK - Object already locked

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

SYSTEM_FAILURE - Internal error from enqueue server

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

Copy and paste ABAP code example for ENQUEUE_EVIBEWE 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_foreign_lock  TYPE STRING, "   
lv_mode_viweenq  TYPE ENQMODE, "   'E'
lv_mandt  TYPE VIWEENQ-MANDT, "   SY-MANDT
lv_system_failure  TYPE VIWEENQ, "   
lv_bukrs  TYPE VIWEENQ-BUKRS, "   
lv_swenr  TYPE VIWEENQ-SWENR, "   
lv_x_bukrs  TYPE VIWEENQ, "   SPACE
lv_x_swenr  TYPE VIWEENQ, "   SPACE
lv__scope  TYPE VIWEENQ, "   '2'
lv__wait  TYPE VIWEENQ, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'ENQUEUE_EVIBEWE'  "Request lock for object EVIBEWE
    EXPORTING
         MODE_VIWEENQ = lv_mode_viweenq
         MANDT = lv_mandt
         BUKRS = lv_bukrs
         SWENR = lv_swenr
         X_BUKRS = lv_x_bukrs
         X_SWENR = lv_x_swenr
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_EVIBEWE




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_EVIBEWE

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_viweenq) = 'E'.
 
"SELECT single MANDT FROM VIWEENQ INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single BUKRS FROM VIWEENQ INTO @DATA(ld_bukrs).
 
"SELECT single SWENR FROM VIWEENQ INTO @DATA(ld_swenr).
 
DATA(ld_x_bukrs) = ' '.
 
DATA(ld_x_swenr) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 
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!