SAP ISM_ENQUEUE_EVVBAKE Function Module for Request Enqueue Lock for Object EJHAK
ISM_ENQUEUE_EVVBAKE is a standard ism enqueue evvbake 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 EJHAK 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 evvbake FM, simply by entering the name ISM_ENQUEUE_EVVBAKE 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_EVVBAKE 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_EVVBAKE'"Request Enqueue Lock for Object EJHAK.
EXPORTING
* MODE_JHAK = 'E' "
* MANDT = SY-MANDT "01. Enqueue Argument
* AVM_NR = "02. Enqueue Argument
* X_AVM_NR = ' ' "Fill Argument 02 with Initial Value?
* _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_EVVBAKE
MODE_JHAK -
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - 01. Enqueue Argument
Data type: JHAK-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
AVM_NR - 02. Enqueue Argument
Data type: JHAK-AVM_NROptional: Yes
Call by Reference: No ( called with pass by value option)
X_AVM_NR - 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: DDENQCOLLDefault: ' '
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_EVVBAKE 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_jhak | TYPE ENQMODE, " 'E' | |||
| lv_foreign_lock | TYPE ENQMODE, " | |||
| lv_mandt | TYPE JHAK-MANDT, " SY-MANDT | |||
| lv_system_failure | TYPE JHAK, " | |||
| lv_avm_nr | TYPE JHAK-AVM_NR, " | |||
| lv_x_avm_nr | TYPE JHAK, " SPACE | |||
| lv__scope | TYPE JHAK, " '2' | |||
| lv__wait | TYPE JHAK, " SPACE | |||
| lv__collect | TYPE DDENQCOLL. " ' ' |
|   CALL FUNCTION 'ISM_ENQUEUE_EVVBAKE' "Request Enqueue Lock for Object EJHAK |
| EXPORTING | ||
| MODE_JHAK | = lv_mode_jhak | |
| MANDT | = lv_mandt | |
| AVM_NR | = lv_avm_nr | |
| X_AVM_NR | = lv_x_avm_nr | |
| _SCOPE | = lv__scope | |
| _WAIT | = lv__wait | |
| _COLLECT | = lv__collect | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " ISM_ENQUEUE_EVVBAKE | ||
ABAP code using 7.40 inline data declarations to call FM ISM_ENQUEUE_EVVBAKE
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_jhak) | = 'E'. | |||
| "SELECT single MANDT FROM JHAK INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single AVM_NR FROM JHAK INTO @DATA(ld_avm_nr). | ||||
| DATA(ld_x_avm_nr) | = ' '. | |||
| DATA(ld__scope) | = '2'. | |||
| DATA(ld__wait) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects