ENQUEUE_EROBLROLB SAP Function module - Request lock for object EROBLROLB

ENQUEUE_EROBLROLB 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_EROBLROLB into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: DWBEN/SAPLSEN0006
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ENQUEUE_EROBLROLB - ENQUEUE EROBLROLB

CALL FUNCTION 'ENQUEUE_EROBLROLB' "Request lock for object EROBLROLB
* EXPORTING
*   mode_mdoblrol = 'E'         " enqmode       Lock mode for table MDOBLROL
*   roletype =                  " mdoblrol-roletype  01th enqueue argument
*   x_roletype = SPACE          " ddenqxpar     Fill argument 01 with initial value?
*   _scope = '2'                " ddenqscope
*   _wait = SPACE               " ddenqwait
*   _collect = ' '              " ddenqcoll     Initially only collect lock
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Object already locked
    SYSTEM_FAILURE = 2          "               Internal error from enqueue server
    .  "  ENQUEUE_EROBLROLB

ABAP code example for Function Module ENQUEUE_EROBLROLB

The ABAP code below is a full code listing to execute function module ENQUEUE_EROBLROLB 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_mdoblrol) = 'Check type of data required'.
 

SELECT single ROLETYPE 
  FROM MDOBLROL 
  INTO @DATA(ld_roletype).


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

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

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

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

CALL FUNCTION 'ENQUEUE_EROBLROLB'
* EXPORTING
*   mode_mdoblrol =              ld_mode_mdoblrol
*   roletype =                   ld_roletype
*   x_roletype =                 ld_x_roletype
*   _scope =                     ld__scope
*   _wait =                      ld__wait
*   _collect =                   ld__collect
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  ENQUEUE_EROBLROLB

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_mdoblrol
 
 TYPE ENQMODE ,
ld_roletype
 
 TYPE MDOBLROL-ROLETYPE ,
ld_x_roletype
 
 TYPE DDENQXPAR ,
ld__scope
 
 TYPE DDENQSCOPE ,
ld__wait
 
 TYPE DDENQWAIT ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_mdoblrol = 'Check type of data required'.

SELECT single ROLETYPE 
  FROM MDOBLROL 
  INTO ld_roletype.

ld_x_roletype = 'Check type of data required'.
ld__scope = 'Check type of data required'.
ld__wait = 'Check type of data required'.
ld__collect = 'Check type of data required'.