DEQUEUE_ESDOC SAP Function module - Release lock on object ESDOC

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

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

Pattern for FM DEQUEUE_ESDOC - DEQUEUE ESDOC

CALL FUNCTION 'DEQUEUE_ESDOC' "Release lock on object ESDOC
* EXPORTING
*   mode_dokhl = 'E'            " enqmode       Lock mode for table DOKHL
*   id =                        " dokhl-id      01th enqueue argument
*   object =                    " dokhl-object  02th enqueue argument
*   langu =                     " dokhl-langu   03th enqueue argument
*   typ =                       " dokhl-typ     04th enqueue argument
*   dokversion =                " dokhl-dokversion  05th enqueue argument
*   x_id = SPACE                "               Fill argument 01 with initial value?
*   x_object = SPACE            "               Fill argument 02 with initial value?
*   x_langu = SPACE             "               Fill argument 03 with initial value?
*   x_typ = SPACE               "               Fill argument 04 with initial value?
*   x_dokversion = SPACE        "               Fill argument 05 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_ESDOC

ABAP code example for Function Module DEQUEUE_ESDOC

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

SELECT single ID 
  FROM DOKHL 
  INTO @DATA(ld_id).

 

SELECT single OBJECT 
  FROM DOKHL 
  INTO @DATA(ld_object).

 

SELECT single LANGU 
  FROM DOKHL 
  INTO @DATA(ld_langu).

 

SELECT single TYP 
  FROM DOKHL 
  INTO @DATA(ld_typ).

 

SELECT single DOKVERSION 
  FROM DOKHL 
  INTO @DATA(ld_dokversion).


DATA(ld_x_id) = 'some text here'.

DATA(ld_x_object) = 'some text here'.

DATA(ld_x_langu) = 'some text here'.

DATA(ld_x_typ) = 'some text here'.

DATA(ld_x_dokversion) = 'some text here'.

DATA(ld__scope) = 'some text here'.

DATA(ld__synchron) = 'some text here'.

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

CALL FUNCTION 'DEQUEUE_ESDOC'
* EXPORTING
*   mode_dokhl =                 ld_mode_dokhl
*   id =                         ld_id
*   object =                     ld_object
*   langu =                      ld_langu
*   typ =                        ld_typ
*   dokversion =                 ld_dokversion
*   x_id =                       ld_x_id
*   x_object =                   ld_x_object
*   x_langu =                    ld_x_langu
*   x_typ =                      ld_x_typ
*   x_dokversion =               ld_x_dokversion
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_ESDOC

IF SY-SUBRC EQ 0.
  "All OK
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_dokhl
 
 TYPE ENQMODE ,
ld_id
 
 TYPE DOKHL-ID ,
ld_object
 
 TYPE DOKHL-OBJECT ,
ld_langu
 
 TYPE DOKHL-LANGU ,
ld_typ
 
 TYPE DOKHL-TYP ,
ld_dokversion
 
 TYPE DOKHL-DOKVERSION ,
ld_x_id
 
 TYPE STRING ,
ld_x_object
 
 TYPE STRING ,
ld_x_langu
 
 TYPE STRING ,
ld_x_typ
 
 TYPE STRING ,
ld_x_dokversion
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_dokhl = 'Check type of data required'.

SELECT single ID 
  FROM DOKHL 
  INTO ld_id.


SELECT single OBJECT 
  FROM DOKHL 
  INTO ld_object.


SELECT single LANGU 
  FROM DOKHL 
  INTO ld_langu.


SELECT single TYP 
  FROM DOKHL 
  INTO ld_typ.


SELECT single DOKVERSION 
  FROM DOKHL 
  INTO ld_dokversion.

ld_x_id = 'some text here'.
ld_x_object = 'some text here'.
ld_x_langu = 'some text here'.
ld_x_typ = 'some text here'.
ld_x_dokversion = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.