SAP ENQUEUE_/BOBF/E_TOOL_UPD Function Module for Request lock for object /BOBF/E_TOOL_UPD









ENQUEUE_/BOBF/E_TOOL_UPD is a standard enqueue /bobf/e tool upd 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 /BOBF/E_TOOL_UPD 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 /bobf/e tool upd FM, simply by entering the name ENQUEUE_/BOBF/E_TOOL_UPD into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_/BOBF/E_TOOL_UPD 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_/BOBF/E_TOOL_UPD'"Request lock for object /BOBF/E_TOOL_UPD
EXPORTING
* MODE_/BOBF/S_TOOL_ENQUEUE_UP00 = 'X' "Lock mode for table /BOBF/S_TOOL_ENQUEUE_UPDATE
* TRANSACTION_ID = "01th enqueue argument
* BO_KEY = "02th enqueue argument
* X_TRANSACTION_ID = ' ' "Fill argument 01 with initial value?
* X_BO_KEY = ' ' "Fill argument 02 with initial value?
* _SCOPE = '2' "
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_/BOBF/E_TOOL_UPD

MODE_/BOBF/S_TOOL_ENQUEUE_UP00 - Lock mode for table /BOBF/S_TOOL_ENQUEUE_UPDATE

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

TRANSACTION_ID - 01th enqueue argument

Data type: /BOBF/S_TOOL_ENQUEUE_UPDATE-TRANSACTION_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

BO_KEY - 02th enqueue argument

Data type: /BOBF/S_TOOL_ENQUEUE_UPDATE-BO_KEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_TRANSACTION_ID - Fill argument 01 with initial value?

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

X_BO_KEY - Fill argument 02 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_/BOBF/E_TOOL_UPD 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_/bobf/s_tool_enqueue_up00  TYPE ENQMODE, "   'X'
lv_system_failure  TYPE ENQMODE, "   
lv_transaction_id  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE-TRANSACTION_ID, "   
lv_bo_key  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE-BO_KEY, "   
lv_x_transaction_id  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE, "   SPACE
lv_x_bo_key  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE, "   SPACE
lv__scope  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE, "   '2'
lv__wait  TYPE /BOBF/S_TOOL_ENQUEUE_UPDATE, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'ENQUEUE_/BOBF/E_TOOL_UPD'  "Request lock for object /BOBF/E_TOOL_UPD
    EXPORTING
         MODE_/BOBF/S_TOOL_ENQUEUE_UP00 = lv_mode_/bobf/s_tool_enqueue_up00
         TRANSACTION_ID = lv_transaction_id
         BO_KEY = lv_bo_key
         X_TRANSACTION_ID = lv_x_transaction_id
         X_BO_KEY = lv_x_bo_key
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_/BOBF/E_TOOL_UPD




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_/BOBF/E_TOOL_UPD

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_/bobf/s_tool_enqueue_up00) = 'X'.
 
 
"SELECT single TRANSACTION_ID FROM /BOBF/S_TOOL_ENQUEUE_UPDATE INTO @DATA(ld_transaction_id).
 
"SELECT single BO_KEY FROM /BOBF/S_TOOL_ENQUEUE_UPDATE INTO @DATA(ld_bo_key).
 
DATA(ld_x_transaction_id) = ' '.
 
DATA(ld_x_bo_key) = ' '.
 
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!