DEQUEUE_EJJAPREL SAP Function module - Release lock on object EJJAPREL

DEQUEUE_EJJAPREL 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_EJJAPREL 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_EJJAPREL - DEQUEUE EJJAPREL

CALL FUNCTION 'DEQUEUE_EJJAPREL' "Release lock on object EJJAPREL
* EXPORTING
*   mode_but050 = 'E'           " enqmode       Lock mode for table BUT050
*   client = SY-MANDT           " but050-client  01th enqueue argument
*   relnr =                     " but050-relnr  02th enqueue argument
*   partner1 =                  " but050-partner1  03th enqueue argument
*   partner2 =                  " but050-partner2  04th enqueue argument
*   date_to =                   " but050-date_to  05th enqueue argument
*   x_relnr = SPACE             "               Fill argument 02 with initial value?
*   x_partner1 = SPACE          "               Fill argument 03 with initial value?
*   x_partner2 = SPACE          "               Fill argument 04 with initial value?
*   x_date_to = SPACE           "               Fill argument 05 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_EJJAPREL

ABAP code example for Function Module DEQUEUE_EJJAPREL

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

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

 

SELECT single RELNR 
  FROM BUT050 
  INTO @DATA(ld_relnr).

 

SELECT single PARTNER1 
  FROM BUT050 
  INTO @DATA(ld_partner1).

 

SELECT single PARTNER2 
  FROM BUT050 
  INTO @DATA(ld_partner2).

 

SELECT single DATE_TO 
  FROM BUT050 
  INTO @DATA(ld_date_to).


DATA(ld_x_relnr) = 'some text here'.

DATA(ld_x_partner1) = 'some text here'.

DATA(ld_x_partner2) = 'some text here'.

DATA(ld_x_date_to) = '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_EJJAPREL'
* EXPORTING
*   mode_but050 =                ld_mode_but050
*   client =                     ld_client
*   relnr =                      ld_relnr
*   partner1 =                   ld_partner1
*   partner2 =                   ld_partner2
*   date_to =                    ld_date_to
*   x_relnr =                    ld_x_relnr
*   x_partner1 =                 ld_x_partner1
*   x_partner2 =                 ld_x_partner2
*   x_date_to =                  ld_x_date_to
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_EJJAPREL

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_but050
 
 TYPE ENQMODE ,
ld_client
 
 TYPE BUT050-CLIENT ,
ld_relnr
 
 TYPE BUT050-RELNR ,
ld_partner1
 
 TYPE BUT050-PARTNER1 ,
ld_partner2
 
 TYPE BUT050-PARTNER2 ,
ld_date_to
 
 TYPE BUT050-DATE_TO ,
ld_x_relnr
 
 TYPE STRING ,
ld_x_partner1
 
 TYPE STRING ,
ld_x_partner2
 
 TYPE STRING ,
ld_x_date_to
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_but050 = 'Check type of data required'.

SELECT single CLIENT 
  FROM BUT050 
  INTO ld_client.


SELECT single RELNR 
  FROM BUT050 
  INTO ld_relnr.


SELECT single PARTNER1 
  FROM BUT050 
  INTO ld_partner1.


SELECT single PARTNER2 
  FROM BUT050 
  INTO ld_partner2.


SELECT single DATE_TO 
  FROM BUT050 
  INTO ld_date_to.

ld_x_relnr = 'some text here'.
ld_x_partner1 = 'some text here'.
ld_x_partner2 = 'some text here'.
ld_x_date_to = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.