DEQUEUE_E_ACTIONS SAP Function module - Release lock on object E_ACTIONS

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

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

Pattern for FM DEQUEUE_E_ACTIONS - DEQUEUE E ACTIONS

CALL FUNCTION 'DEQUEUE_E_ACTIONS' "Release lock on object E_ACTIONS
* EXPORTING
*   mode_pcl3 = 'E'             " enqmode       Lock mode for table PCL3
*   client = SY-MANDT           " pcl3-client   01th enqueue argument
*   relid =                     " pcl3-relid    02th enqueue argument
*   srtfd =                     " pcl3-srtfd    03th enqueue argument
*   x_relid = SPACE             "               Fill argument 02 with initial value?
*   x_srtfd = SPACE             "               Fill argument 03 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_E_ACTIONS

ABAP code example for Function Module DEQUEUE_E_ACTIONS

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

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

 

SELECT single RELID 
  FROM PCL3 
  INTO @DATA(ld_relid).

 

SELECT single SRTFD 
  FROM PCL3 
  INTO @DATA(ld_srtfd).


DATA(ld_x_relid) = 'some text here'.

DATA(ld_x_srtfd) = '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_E_ACTIONS'
* EXPORTING
*   mode_pcl3 =                  ld_mode_pcl3
*   client =                     ld_client
*   relid =                      ld_relid
*   srtfd =                      ld_srtfd
*   x_relid =                    ld_x_relid
*   x_srtfd =                    ld_x_srtfd
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_E_ACTIONS

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_pcl3
 
 TYPE ENQMODE ,
ld_client
 
 TYPE PCL3-CLIENT ,
ld_relid
 
 TYPE PCL3-RELID ,
ld_srtfd
 
 TYPE PCL3-SRTFD ,
ld_x_relid
 
 TYPE STRING ,
ld_x_srtfd
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_pcl3 = 'Check type of data required'.

SELECT single CLIENT 
  FROM PCL3 
  INTO ld_client.


SELECT single RELID 
  FROM PCL3 
  INTO ld_relid.


SELECT single SRTFD 
  FROM PCL3 
  INTO ld_srtfd.

ld_x_relid = 'some text here'.
ld_x_srtfd = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.