SAP ENQUEUE_E_PVBE_E Function Module for Request lock for object E_PVBE_E









ENQUEUE_E_PVBE_E is a standard enqueue e pvbe e 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 E_PVBE_E 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 e pvbe e FM, simply by entering the name ENQUEUE_E_PVBE_E into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_E_PVBE_E 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_E_PVBE_E'"Request lock for object E_PVBE_E
  EXPORTING
*  MODE_PVBE = 'E' "Lock mode for table PVBE
*  MANDT = SY-MANDT "Enqueue argument 01
*  WERKS =  "Enqueue argument 02
*  PRVBE =  "Enqueue argument 03
*  X_WERKS = ' ' "Fill argument 02 with initial value?
*  X_PRVBE = ' ' "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_E_PVBE_E

MODE_PVBE - Lock mode for table PVBE

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

MANDT - Enqueue argument 01

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

WERKS - Enqueue argument 02

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

PRVBE - Enqueue argument 03

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

X_WERKS - Fill argument 02 with initial value?

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

X_PRVBE - 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_E_PVBE_E 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_pvbe  TYPE ENQMODE, "   'E'
lv_foreign_lock  TYPE ENQMODE, "   
lv_mandt  TYPE PVBE-MANDT, "   SY-MANDT
lv_system_failure  TYPE PVBE, "   
lv_werks  TYPE PVBE-WERKS, "   
lv_prvbe  TYPE PVBE-PRVBE, "   
lv_x_werks  TYPE PVBE, "   SPACE
lv_x_prvbe  TYPE PVBE, "   SPACE
lv__scope  TYPE PVBE, "   '2'
lv__wait  TYPE PVBE, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'ENQUEUE_E_PVBE_E'  "Request lock for object E_PVBE_E
    EXPORTING
         MODE_PVBE = lv_mode_pvbe
         MANDT = lv_mandt
         WERKS = lv_werks
         PRVBE = lv_prvbe
         X_WERKS = lv_x_werks
         X_PRVBE = lv_x_prvbe
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_E_PVBE_E




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_PVBE_E

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_pvbe) = 'E'.
 
 
"SELECT single MANDT FROM PVBE INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
"SELECT single WERKS FROM PVBE INTO @DATA(ld_werks).
 
"SELECT single PRVBE FROM PVBE INTO @DATA(ld_prvbe).
 
DATA(ld_x_werks) = ' '.
 
DATA(ld_x_prvbe) = ' '.
 
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!