DEQUEUE_ECNVMBTJOBS SAP Function module - Release lock on object ECNVMBTJOBS

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

Associated Function Group: DWBEN/SAPLCEN0014
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM DEQUEUE_ECNVMBTJOBS - DEQUEUE ECNVMBTJOBS

CALL FUNCTION 'DEQUEUE_ECNVMBTJOBS' "Release lock on object ECNVMBTJOBS
* EXPORTING
*   mode_cnvmbtjobs = 'E'       " enqmode       Lock mode for table CNVMBTJOBS
*   client = SY-MANDT           " cnvmbtjobs-client  01th enqueue argument
*   packid =                    " cnvmbtjobs-packid  02th enqueue argument
*   phase =                     " cnvmbtjobs-phase  03th enqueue argument
*   crt_time_id =               " cnvmbtjobs-crt_time_id  04th enqueue argument
*   activity_id =               " cnvmbtjobs-activity_id  05th enqueue argument
*   x_packid = SPACE            " ddenqxpar     Fill argument 02 with initial value?
*   x_phase = SPACE             " ddenqxpar     Fill argument 03 with initial value?
*   x_crt_time_id = SPACE       " ddenqxpar     Fill argument 04 with initial value?
*   x_activity_id = SPACE       " ddenqxpar     Fill argument 05 with initial value?
*   _scope = '3'                " ddenqscope
*   _synchron = SPACE           " ddenqsync     Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_ECNVMBTJOBS

ABAP code example for Function Module DEQUEUE_ECNVMBTJOBS

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

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

 

SELECT single PACKID 
  FROM CNVMBTJOBS 
  INTO @DATA(ld_packid).

 

SELECT single PHASE 
  FROM CNVMBTJOBS 
  INTO @DATA(ld_phase).

 

SELECT single CRT_TIME_ID 
  FROM CNVMBTJOBS 
  INTO @DATA(ld_crt_time_id).

 

SELECT single ACTIVITY_ID 
  FROM CNVMBTJOBS 
  INTO @DATA(ld_activity_id).


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

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

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

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

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

DATA(ld__synchron) = 'some text here'.

DATA(ld__collect) = 'some text here'.
.

CALL FUNCTION 'DEQUEUE_ECNVMBTJOBS'
* EXPORTING
*   mode_cnvmbtjobs =            ld_mode_cnvmbtjobs
*   client =                     ld_client
*   packid =                     ld_packid
*   phase =                      ld_phase
*   crt_time_id =                ld_crt_time_id
*   activity_id =                ld_activity_id
*   x_packid =                   ld_x_packid
*   x_phase =                    ld_x_phase
*   x_crt_time_id =              ld_x_crt_time_id
*   x_activity_id =              ld_x_activity_id
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_ECNVMBTJOBS

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_cnvmbtjobs
 
 TYPE ENQMODE ,
ld_client
 
 TYPE CNVMBTJOBS-CLIENT ,
ld_packid
 
 TYPE CNVMBTJOBS-PACKID ,
ld_phase
 
 TYPE CNVMBTJOBS-PHASE ,
ld_crt_time_id
 
 TYPE CNVMBTJOBS-CRT_TIME_ID ,
ld_activity_id
 
 TYPE CNVMBTJOBS-ACTIVITY_ID ,
ld_x_packid
 
 TYPE DDENQXPAR ,
ld_x_phase
 
 TYPE DDENQXPAR ,
ld_x_crt_time_id
 
 TYPE DDENQXPAR ,
ld_x_activity_id
 
 TYPE DDENQXPAR ,
ld__scope
 
 TYPE DDENQSCOPE ,
ld__synchron
 
 TYPE DDENQSYNC ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_cnvmbtjobs = 'some text here'.

SELECT single CLIENT 
  FROM CNVMBTJOBS 
  INTO ld_client.


SELECT single PACKID 
  FROM CNVMBTJOBS 
  INTO ld_packid.


SELECT single PHASE 
  FROM CNVMBTJOBS 
  INTO ld_phase.


SELECT single CRT_TIME_ID 
  FROM CNVMBTJOBS 
  INTO ld_crt_time_id.


SELECT single ACTIVITY_ID 
  FROM CNVMBTJOBS 
  INTO ld_activity_id.

ld_x_packid = 'some text here'.
ld_x_phase = 'some text here'.
ld_x_crt_time_id = 'some text here'.
ld_x_activity_id = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'some text here'.