DEQUEUE_EJVZEBU_SH SAP Function module - Release lock on object EJVZEBU_SH

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

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

Pattern for FM DEQUEUE_EJVZEBU_SH - DEQUEUE EJVZEBU SH

CALL FUNCTION 'DEQUEUE_EJVZEBU_SH' "Release lock on object EJVZEBU_SH
* EXPORTING
*   mode_jvtplzzebu = 'S'       " enqmode       Lock mode for table JVTPLZZEBU
*   mandt = SY-MANDT            " jvtplzzebu-mandt  01th enqueue argument
*   land1 =                     " jvtplzzebu-land1  02th enqueue argument
*   plz =                       " jvtplzzebu-plz  03th enqueue argument
*   x_land1 = SPACE             "               Fill argument 02 with initial value?
*   x_plz = SPACE               "               Fill argument 03 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_EJVZEBU_SH

ABAP code example for Function Module DEQUEUE_EJVZEBU_SH

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

SELECT single MANDT 
  FROM JVTPLZZEBU 
  INTO @DATA(ld_mandt).

 

SELECT single LAND1 
  FROM JVTPLZZEBU 
  INTO @DATA(ld_land1).

 

SELECT single PLZ 
  FROM JVTPLZZEBU 
  INTO @DATA(ld_plz).


DATA(ld_x_land1) = 'some text here'.

DATA(ld_x_plz) = '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_EJVZEBU_SH'
* EXPORTING
*   mode_jvtplzzebu =            ld_mode_jvtplzzebu
*   mandt =                      ld_mandt
*   land1 =                      ld_land1
*   plz =                        ld_plz
*   x_land1 =                    ld_x_land1
*   x_plz =                      ld_x_plz
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_EJVZEBU_SH

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_jvtplzzebu
 
 TYPE ENQMODE ,
ld_mandt
 
 TYPE JVTPLZZEBU-MANDT ,
ld_land1
 
 TYPE JVTPLZZEBU-LAND1 ,
ld_plz
 
 TYPE JVTPLZZEBU-PLZ ,
ld_x_land1
 
 TYPE STRING ,
ld_x_plz
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_jvtplzzebu = 'Check type of data required'.

SELECT single MANDT 
  FROM JVTPLZZEBU 
  INTO ld_mandt.


SELECT single LAND1 
  FROM JVTPLZZEBU 
  INTO ld_land1.


SELECT single PLZ 
  FROM JVTPLZZEBU 
  INTO ld_plz.

ld_x_land1 = 'some text here'.
ld_x_plz = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.