RSENQ_DEQUEUE SAP Function module - Dequeue Module

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

Associated Function Group: RSENQ
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RSENQ_DEQUEUE - RSENQ DEQUEUE

CALL FUNCTION 'RSENQ_DEQUEUE' "Dequeue Module
* EXPORTING
*   i_lockid =                  " rsenq_lockid
*   i_action =                  " rsenq_action
*   i_t_object =                " rsenq_t_object
*   i_t_subobject =             " rsenq_t_object
*   i_with_message = SPACE      " rs_bool       Boolean
*   i_no_shared_buffer =        " rs_bool       Boolean
* CHANGING
*   c_t_msg =                   " rs_t_msg      BW: Table with Messages (Application Log)
  EXCEPTIONS
    NO_LOCK_FOUND = 1           "               No Lock Found
    .  "  RSENQ_DEQUEUE

ABAP code example for Function Module RSENQ_DEQUEUE

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

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

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

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

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

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

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

CALL FUNCTION 'RSENQ_DEQUEUE'
* EXPORTING
*   i_lockid =                   ld_i_lockid
*   i_action =                   ld_i_action
*   i_t_object =                 ld_i_t_object
*   i_t_subobject =              ld_i_t_subobject
*   i_with_message =             ld_i_with_message
*   i_no_shared_buffer =         ld_i_no_shared_buffer
* CHANGING
*   c_t_msg =                    ld_c_t_msg
  EXCEPTIONS
    NO_LOCK_FOUND =              1
    .  "  RSENQ_DEQUEUE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_c_t_msg
 
 TYPE RS_T_MSG ,
ld_i_lockid
 
 TYPE RSENQ_LOCKID ,
ld_i_action
 
 TYPE RSENQ_ACTION ,
ld_i_t_object
 
 TYPE RSENQ_T_OBJECT ,
ld_i_t_subobject
 
 TYPE RSENQ_T_OBJECT ,
ld_i_with_message
 
 TYPE RS_BOOL ,
ld_i_no_shared_buffer
 
 TYPE RS_BOOL .


ld_c_t_msg = 'Check type of data required'.
ld_i_lockid = 'Check type of data required'.
ld_i_action = 'Check type of data required'.
ld_i_t_object = 'Check type of data required'.
ld_i_t_subobject = 'Check type of data required'.
ld_i_with_message = 'Check type of data required'.
ld_i_no_shared_buffer = 'Check type of data required'.