DEQUEUE_E_VERI_JOIN SAP Function module - Release lock on object E_VERI_JOIN

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

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

Pattern for FM DEQUEUE_E_VERI_JOIN - DEQUEUE E VERI JOIN

CALL FUNCTION 'DEQUEUE_E_VERI_JOIN' "Release lock on object E_VERI_JOIN
* EXPORTING
*   mode_veri_join = 'E'        " enqmode       Lock mode for table VERI_JOIN
*   client = SY-MANDT           " veri_join-client  01th enqueue argument
*   arg1 =                      " veri_join-arg1  02th enqueue argument
*   arg2 =                      " veri_join-arg2  03th enqueue argument
*   x_arg1 = SPACE              "               Fill argument 02 with initial value?
*   x_arg2 = SPACE              "               Fill argument 03 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_E_VERI_JOIN

ABAP code example for Function Module DEQUEUE_E_VERI_JOIN

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

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

 

SELECT single ARG1 
  FROM VERI_JOIN 
  INTO @DATA(ld_arg1).

 

SELECT single ARG2 
  FROM VERI_JOIN 
  INTO @DATA(ld_arg2).


DATA(ld_x_arg1) = 'some text here'.

DATA(ld_x_arg2) = '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_VERI_JOIN'
* EXPORTING
*   mode_veri_join =             ld_mode_veri_join
*   client =                     ld_client
*   arg1 =                       ld_arg1
*   arg2 =                       ld_arg2
*   x_arg1 =                     ld_x_arg1
*   x_arg2 =                     ld_x_arg2
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_E_VERI_JOIN

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_veri_join
 
 TYPE ENQMODE ,
ld_client
 
 TYPE VERI_JOIN-CLIENT ,
ld_arg1
 
 TYPE VERI_JOIN-ARG1 ,
ld_arg2
 
 TYPE VERI_JOIN-ARG2 ,
ld_x_arg1
 
 TYPE STRING ,
ld_x_arg2
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_veri_join = 'Check type of data required'.

SELECT single CLIENT 
  FROM VERI_JOIN 
  INTO ld_client.


SELECT single ARG1 
  FROM VERI_JOIN 
  INTO ld_arg1.


SELECT single ARG2 
  FROM VERI_JOIN 
  INTO ld_arg2.

ld_x_arg1 = 'some text here'.
ld_x_arg2 = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.