SAP Function Modules

ENQUEUE_E_BDLSPOS SAP Function module - Request lock for object E_BDLSPOS







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

Associated Function Group: DWBEN/SAPLSEN0003
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ENQUEUE_E_BDLSPOS - ENQUEUE E BDLSPOS





CALL FUNCTION 'ENQUEUE_E_BDLSPOS' "Request lock for object E_BDLSPOS
* EXPORTING
*   mode_bdlspos = 'E'          " enqmode       Lock mode for table BDLSPOS
*   client = SY-MANDT           " bdlspos-client  01th enqueue argument
*   cuid =                      " bdlspos-cuid  02th enqueue argument
*   tabname =                   " bdlspos-tabname  03th enqueue argument
*   fldname =                   " bdlspos-fldname  04th enqueue argument
*   x_cuid = SPACE              "               Fill argument 02 with initial value?
*   x_tabname = SPACE           "               Fill argument 03 with initial value?
*   x_fldname = SPACE           "               Fill argument 04 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_E_BDLSPOS

ABAP code example for Function Module ENQUEUE_E_BDLSPOS





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

SELECT single CLIENT
FROM BDLSPOS
INTO @DATA(ld_client).


SELECT single CUID
FROM BDLSPOS
INTO @DATA(ld_cuid).


SELECT single TABNAME
FROM BDLSPOS
INTO @DATA(ld_tabname).


SELECT single FLDNAME
FROM BDLSPOS
INTO @DATA(ld_fldname).

DATA(ld_x_cuid) = 'some text here'.
DATA(ld_x_tabname) = 'some text here'.
DATA(ld_x_fldname) = '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_E_BDLSPOS' * EXPORTING * mode_bdlspos = ld_mode_bdlspos * client = ld_client * cuid = ld_cuid * tabname = ld_tabname * fldname = ld_fldname * x_cuid = ld_x_cuid * x_tabname = ld_x_tabname * x_fldname = ld_x_fldname * _scope = ld__scope * _wait = ld__wait * _collect = ld__collect EXCEPTIONS FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2 . " ENQUEUE_E_BDLSPOS
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_bdlspos  TYPE ENQMODE ,
ld_client  TYPE BDLSPOS-CLIENT ,
ld_cuid  TYPE BDLSPOS-CUID ,
ld_tabname  TYPE BDLSPOS-TABNAME ,
ld_fldname  TYPE BDLSPOS-FLDNAME ,
ld_x_cuid  TYPE STRING ,
ld_x_tabname  TYPE STRING ,
ld_x_fldname  TYPE STRING ,
ld__scope  TYPE STRING ,
ld__wait  TYPE STRING ,
ld__collect  TYPE DDENQCOLL .

ld_mode_bdlspos = 'Check type of data required'.

SELECT single CLIENT
FROM BDLSPOS
INTO ld_client.


SELECT single CUID
FROM BDLSPOS
INTO ld_cuid.


SELECT single TABNAME
FROM BDLSPOS
INTO ld_tabname.


SELECT single FLDNAME
FROM BDLSPOS
INTO ld_fldname.

ld_x_cuid = 'some text here'.
ld_x_tabname = 'some text here'.
ld_x_fldname = 'some text here'.
ld__scope = 'some text here'.
ld__wait = 'some text here'.
ld__collect = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ENQUEUE_E_BDLSPOS or its description.