SAP ENQUEUE_ECSMBK Function Module for Request lock for object ECSMBK









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

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



Function ENQUEUE_ECSMBK 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_ECSMBK'"Request lock for object ECSMBK
  EXPORTING
*  MODE_CSMBK = 'E' "Lock mode for table CSMBK
*  _COLLECT = ' ' "Initially only collect lock
*  CCMS_OBJ =  "01th enqueue argument
*  TOKEN =  "02th enqueue argument
*  VALUE =  "03th enqueue argument
*  X_CCMS_OBJ = ' ' "Fill argument 01 with initial value?
*  X_TOKEN = ' ' "Fill argument 02 with initial value?
*  X_VALUE = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '2' "
*  _WAIT = ' ' "

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_ECSMBK

MODE_CSMBK - Lock mode for table CSMBK

Data type: ENQMODE
Default: 'E'
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)

CCMS_OBJ - 01th enqueue argument

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

TOKEN - 02th enqueue argument

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

VALUE - 03th enqueue argument

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

X_CCMS_OBJ - Fill argument 01 with initial value?

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

X_TOKEN - Fill argument 02 with initial value?

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

X_VALUE - 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)

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_ECSMBK 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_csmbk  TYPE ENQMODE, "   'E'
lv_foreign_lock  TYPE ENQMODE, "   
lv__collect  TYPE DDENQCOLL, "   ' '
lv_ccms_obj  TYPE CSMBK-CCMS_OBJ, "   
lv_system_failure  TYPE CSMBK, "   
lv_token  TYPE CSMBK-TOKEN, "   
lv_value  TYPE CSMBK-VALUE, "   
lv_x_ccms_obj  TYPE CSMBK, "   SPACE
lv_x_token  TYPE CSMBK, "   SPACE
lv_x_value  TYPE CSMBK, "   SPACE
lv__scope  TYPE CSMBK, "   '2'
lv__wait  TYPE CSMBK. "   SPACE

  CALL FUNCTION 'ENQUEUE_ECSMBK'  "Request lock for object ECSMBK
    EXPORTING
         MODE_CSMBK = lv_mode_csmbk
         _COLLECT = lv__collect
         CCMS_OBJ = lv_ccms_obj
         TOKEN = lv_token
         VALUE = lv_value
         X_CCMS_OBJ = lv_x_ccms_obj
         X_TOKEN = lv_x_token
         X_VALUE = lv_x_value
         _SCOPE = lv__scope
         _WAIT = lv__wait
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_ECSMBK




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_ECSMBK

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_csmbk) = 'E'.
 
 
DATA(ld__collect) = ' '.
 
"SELECT single CCMS_OBJ FROM CSMBK INTO @DATA(ld_ccms_obj).
 
 
"SELECT single TOKEN FROM CSMBK INTO @DATA(ld_token).
 
"SELECT single VALUE FROM CSMBK INTO @DATA(ld_value).
 
DATA(ld_x_ccms_obj) = ' '.
 
DATA(ld_x_token) = ' '.
 
DATA(ld_x_value) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 


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!