ENQUEUE_ECSL_M SAP Function module - Request lock for object ECSL_M

ENQUEUE_ECSL_M is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ENQUEUE_ECSL_M into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: DWBEN/SAPLSEN0007
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ENQUEUE_ECSL_M - ENQUEUE ECSL M

CALL FUNCTION 'ENQUEUE_ECSL_M' "Request lock for object ECSL_M
* EXPORTING
*   mode_csl_m = 'E'            " enqmode       Lock mode for table CSL_M
*   msy =                       " csl_m-msy     01th enqueue argument
*   mnu =                       " csl_m-mnu     02th enqueue argument
*   x_msy = SPACE               "               Fill argument 01 with initial value?
*   x_mnu = SPACE               "               Fill argument 02 with initial value?
*   _scope = '2'                "
*   _wait = SPACE               "
*   _collect = ' '              " ddenqcoll     Initially only collect lock
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Object already locked
    SYSTEM_FAILURE = 2          "               Internal error from enqueue server
    .  "  ENQUEUE_ECSL_M

ABAP code example for Function Module ENQUEUE_ECSL_M

The ABAP code below is a full code listing to execute function module ENQUEUE_ECSL_M including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_mode_csl_m) = 'Check type of data required'.
 

SELECT single MSY 
  FROM CSL_M 
  INTO @DATA(ld_msy).

 

SELECT single MNU 
  FROM CSL_M 
  INTO @DATA(ld_mnu).


DATA(ld_x_msy) = 'some text here'.

DATA(ld_x_mnu) = 'some text here'.

DATA(ld__scope) = 'some text here'.

DATA(ld__wait) = 'some text here'.

DATA(ld__collect) = 'Check type of data required'.
.

CALL FUNCTION 'ENQUEUE_ECSL_M'
* EXPORTING
*   mode_csl_m =                 ld_mode_csl_m
*   msy =                        ld_msy
*   mnu =                        ld_mnu
*   x_msy =                      ld_x_msy
*   x_mnu =                      ld_x_mnu
*   _scope =                     ld__scope
*   _wait =                      ld__wait
*   _collect =                   ld__collect
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  ENQUEUE_ECSL_M

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_mode_csl_m
 
 TYPE ENQMODE ,
ld_msy
 
 TYPE CSL_M-MSY ,
ld_mnu
 
 TYPE CSL_M-MNU ,
ld_x_msy
 
 TYPE STRING ,
ld_x_mnu
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__wait
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_csl_m = 'Check type of data required'.

SELECT single MSY 
  FROM CSL_M 
  INTO ld_msy.


SELECT single MNU 
  FROM CSL_M 
  INTO ld_mnu.

ld_x_msy = 'some text here'.
ld_x_mnu = 'some text here'.
ld__scope = 'some text here'.
ld__wait = 'some text here'.
ld__collect = 'Check type of data required'.