SAP DEQUEUE_ELTR_TASKS Function Module for Release lock on object ELTR_TASKS









DEQUEUE_ELTR_TASKS is a standard dequeue eltr tasks SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release lock on object ELTR_TASKS processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for dequeue eltr tasks FM, simply by entering the name DEQUEUE_ELTR_TASKS into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/LEN0001
Program Name: /1BCDWBEN/SAPLLEN0001
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DEQUEUE_ELTR_TASKS pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'DEQUEUE_ELTR_TASKS'"Release lock on object ELTR_TASKS
EXPORTING
* MODE_LTR_TASKS = 'X' "Lock mode for table LTR_TASKS
* X_DATA_PACKAGE = ' ' "Fill argument 05 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* CLIENT = SY-MANDT "01th enqueue argument
* PCL_PACKAGE_ID = "02th enqueue argument
* TS_GUID = "03th enqueue argument
* STEP_KEY = "04th enqueue argument
* DATA_PACKAGE = "05th enqueue argument
* X_PCL_PACKAGE_ID = ' ' "Fill argument 02 with initial value?
* X_TS_GUID = ' ' "Fill argument 03 with initial value?
* X_STEP_KEY = ' ' "Fill argument 04 with initial value?
.



IMPORTING Parameters details for DEQUEUE_ELTR_TASKS

MODE_LTR_TASKS - Lock mode for table LTR_TASKS

Data type: ENQMODE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_DATA_PACKAGE - Fill argument 05 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SCOPE -

Data type:
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SYNCHRON - Synchonous unlock

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

_COLLECT - Initially only collect lock

Data type: DDENQCOLL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLIENT - 01th enqueue argument

Data type: LTR_TASKS-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PCL_PACKAGE_ID - 02th enqueue argument

Data type: LTR_TASKS-PCL_PACKAGE_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

TS_GUID - 03th enqueue argument

Data type: LTR_TASKS-TS_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

STEP_KEY - 04th enqueue argument

Data type: LTR_TASKS-STEP_KEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATA_PACKAGE - 05th enqueue argument

Data type: LTR_TASKS-DATA_PACKAGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PCL_PACKAGE_ID - Fill argument 02 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_TS_GUID - Fill argument 03 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_STEP_KEY - Fill argument 04 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DEQUEUE_ELTR_TASKS Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_mode_ltr_tasks  TYPE ENQMODE, "   'X'
lv_x_data_package  TYPE ENQMODE, "   SPACE
lv__scope  TYPE ENQMODE, "   '3'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_client  TYPE LTR_TASKS-CLIENT, "   SY-MANDT
lv_pcl_package_id  TYPE LTR_TASKS-PCL_PACKAGE_ID, "   
lv_ts_guid  TYPE LTR_TASKS-TS_GUID, "   
lv_step_key  TYPE LTR_TASKS-STEP_KEY, "   
lv_data_package  TYPE LTR_TASKS-DATA_PACKAGE, "   
lv_x_pcl_package_id  TYPE LTR_TASKS, "   SPACE
lv_x_ts_guid  TYPE LTR_TASKS, "   SPACE
lv_x_step_key  TYPE LTR_TASKS. "   SPACE

  CALL FUNCTION 'DEQUEUE_ELTR_TASKS'  "Release lock on object ELTR_TASKS
    EXPORTING
         MODE_LTR_TASKS = lv_mode_ltr_tasks
         X_DATA_PACKAGE = lv_x_data_package
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         CLIENT = lv_client
         PCL_PACKAGE_ID = lv_pcl_package_id
         TS_GUID = lv_ts_guid
         STEP_KEY = lv_step_key
         DATA_PACKAGE = lv_data_package
         X_PCL_PACKAGE_ID = lv_x_pcl_package_id
         X_TS_GUID = lv_x_ts_guid
         X_STEP_KEY = lv_x_step_key
. " DEQUEUE_ELTR_TASKS




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ELTR_TASKS

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

DATA(ld_mode_ltr_tasks) = 'X'.
 
DATA(ld_x_data_package) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single CLIENT FROM LTR_TASKS INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single PCL_PACKAGE_ID FROM LTR_TASKS INTO @DATA(ld_pcl_package_id).
 
"SELECT single TS_GUID FROM LTR_TASKS INTO @DATA(ld_ts_guid).
 
"SELECT single STEP_KEY FROM LTR_TASKS INTO @DATA(ld_step_key).
 
"SELECT single DATA_PACKAGE FROM LTR_TASKS INTO @DATA(ld_data_package).
 
DATA(ld_x_pcl_package_id) = ' '.
 
DATA(ld_x_ts_guid) = ' '.
 
DATA(ld_x_step_key) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!