SAP ISM_ENQUEUE_EVVBRKE Function Module for Request Enqueue Lock for Object EJHJHTFK

Search SAP Function Modules

ISM_ENQUEUE_EVVBRKE is a standard ism enqueue evvbrke 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 Enqueue Lock for Object EJHJHTFK 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 ism enqueue evvbrke FM, simply by entering the name ISM_ENQUEUE_EVVBRKE into the relevant SAP transaction such as SE37 or SE38.

Function Group: JHAD
Program Name: SAPLJHAD
Main Program: SAPLJHAD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_ENQUEUE_EVVBRKE 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 'ISM_ENQUEUE_EVVBRKE'"Request Enqueue Lock for Object EJHJHTFK
  EXPORTING
*  MODE_JHTFK = 'E' "
*  MANDT = SY-MANDT "01. Enqueue Argument
*  VBELN =  "02. Enqueue Argument
*  X_VBELN = ' ' "
*  _SCOPE = '2' "
*  _WAIT = ' ' "
*  _COLLECT = ' ' "Initially only collect lock

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJHAD_001 IS-M/AM: Output Control for Contract Settlement Fill KOMKBJK
EXIT_SAPLJHAD_004 IS-M/AM: Contract Output Control: Communication Structure, Partner
EXIT_SAPLJHAD_005 IS-M: Modify a Follow-On Contract
EXIT_SAPLJHAD_006 IS-M: Define Default Contract Header
EXIT_SAPLJHAD_007 IS-M: Influence Overlap Check

IMPORTING Parameters details for ISM_ENQUEUE_EVVBRKE

MODE_JHTFK -

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

MANDT - 01. Enqueue Argument

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

VBELN - 02. Enqueue Argument

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

X_VBELN -

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: Yes

SYSTEM_FAILURE - Internal Error from Enqueue Server

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_ENQUEUE_EVVBRKE 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.

ABAP code using 7.40 inline data declarations to call FM ISM_ENQUEUE_EVVBRKE

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.

Search for further information about these or an SAP related objects