DEQUEUE_E_OIGCM SAP Function module - Release lock on object E_OIGCM

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

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

Pattern for FM DEQUEUE_E_OIGCM - DEQUEUE E OIGCM

CALL FUNCTION 'DEQUEUE_E_OIGCM' "Release lock on object E_OIGCM
* EXPORTING
*   mode_oigcm = 'E'            " enqmode       Lock mode for table OIGCM
*   client = SY-MANDT           " oigcm-client  01th enqueue argument
*   tu_metnmbr =                " oigcm-tu_metnmbr  02th enqueue argument
*   x_tu_metnmbr = SPACE        "               Fill argument 02 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_E_OIGCM

ABAP code example for Function Module DEQUEUE_E_OIGCM

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

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

 

SELECT single TU_METNMBR 
  FROM OIGCM 
  INTO @DATA(ld_tu_metnmbr).


DATA(ld_x_tu_metnmbr) = '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_OIGCM'
* EXPORTING
*   mode_oigcm =                 ld_mode_oigcm
*   client =                     ld_client
*   tu_metnmbr =                 ld_tu_metnmbr
*   x_tu_metnmbr =               ld_x_tu_metnmbr
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_E_OIGCM

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_oigcm
 
 TYPE ENQMODE ,
ld_client
 
 TYPE OIGCM-CLIENT ,
ld_tu_metnmbr
 
 TYPE OIGCM-TU_METNMBR ,
ld_x_tu_metnmbr
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_oigcm = 'Check type of data required'.

SELECT single CLIENT 
  FROM OIGCM 
  INTO ld_client.


SELECT single TU_METNMBR 
  FROM OIGCM 
  INTO ld_tu_metnmbr.

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