ENQUEUE_ELINEBAL SAP Function module - Request lock for object ELINEBAL

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

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

Pattern for FM ENQUEUE_ELINEBAL - ENQUEUE ELINEBAL

CALL FUNCTION 'ENQUEUE_ELINEBAL' "Request lock for object ELINEBAL
* EXPORTING
*   mode_linebal_enq = 'E'      " enqmode       Lock mode for table LINEBAL_ENQ
*   mandt = SY-MANDT            " linebal_enq-mandt  01th enqueue argument
*   lbname =                    " linebal_enq-lbname  02th enqueue argument
*   x_lbname = 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_ELINEBAL

ABAP code example for Function Module ENQUEUE_ELINEBAL

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


DATA(ld_mandt) = Check type of data required


DATA(ld_lbname) = some text here

DATA(ld_x_lbname) = '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_ELINEBAL'
* EXPORTING
*   mode_linebal_enq =           ld_mode_linebal_enq
*   mandt =                      ld_mandt
*   lbname =                     ld_lbname
*   x_lbname =                   ld_x_lbname
*   _scope =                     ld__scope
*   _wait =                      ld__wait
*   _collect =                   ld__collect
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  ENQUEUE_ELINEBAL

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_linebal_enq
 
 TYPE ENQMODE ,
ld_mandt
 
 TYPE LINEBAL_ENQ-MANDT ,
ld_lbname
 
 TYPE LINEBAL_ENQ-LBNAME ,
ld_x_lbname
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__wait
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_linebal_enq = 'Check type of data required'.

ld_mandt = Check type of data required

ld_lbname = some text here
ld_x_lbname = 'some text here'.
ld__scope = 'some text here'.
ld__wait = 'some text here'.
ld__collect = 'Check type of data required'.