SAP DEQUEUE_E_HDS_TREE Function Module for Release lock on object E_HDS_TREE









DEQUEUE_E_HDS_TREE is a standard dequeue e hds tree 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 E_HDS_TREE 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 e hds tree FM, simply by entering the name DEQUEUE_E_HDS_TREE into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_HDS_TREE 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_E_HDS_TREE'"Release lock on object E_HDS_TREE
EXPORTING
* MODE_HDS_STR_TREE_ENQ = 'E' "Lock mode for table HDS_STR_TREE_ENQ
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* CLIENT = SY-MANDT "01th enqueue argument
* APPL_ID = "02th enqueue argument
* TREECATG = "03th enqueue argument
* TREE_ID = "04th enqueue argument
* X_APPL_ID = ' ' "Fill argument 02 with initial value?
* X_TREECATG = ' ' "Fill argument 03 with initial value?
* X_TREE_ID = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_HDS_TREE

MODE_HDS_STR_TREE_ENQ - Lock mode for table HDS_STR_TREE_ENQ

Data type: ENQMODE
Default: 'E'
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: HDS_STR_TREE_ENQ-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPL_ID - 02th enqueue argument

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

TREECATG - 03th enqueue argument

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

TREE_ID - 04th enqueue argument

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

X_APPL_ID - Fill argument 02 with initial value?

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

X_TREECATG - Fill argument 03 with initial value?

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

X_TREE_ID - Fill argument 04 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)

Copy and paste ABAP code example for DEQUEUE_E_HDS_TREE 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_hds_str_tree_enq  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_client  TYPE HDS_STR_TREE_ENQ-CLIENT, "   SY-MANDT
lv_appl_id  TYPE HDS_STR_TREE_ENQ-APPL_ID, "   
lv_treecatg  TYPE HDS_STR_TREE_ENQ-TREECATG, "   
lv_tree_id  TYPE HDS_STR_TREE_ENQ-TREE_ID, "   
lv_x_appl_id  TYPE HDS_STR_TREE_ENQ, "   SPACE
lv_x_treecatg  TYPE HDS_STR_TREE_ENQ, "   SPACE
lv_x_tree_id  TYPE HDS_STR_TREE_ENQ, "   SPACE
lv__scope  TYPE HDS_STR_TREE_ENQ. "   '3'

  CALL FUNCTION 'DEQUEUE_E_HDS_TREE'  "Release lock on object E_HDS_TREE
    EXPORTING
         MODE_HDS_STR_TREE_ENQ = lv_mode_hds_str_tree_enq
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         CLIENT = lv_client
         APPL_ID = lv_appl_id
         TREECATG = lv_treecatg
         TREE_ID = lv_tree_id
         X_APPL_ID = lv_x_appl_id
         X_TREECATG = lv_x_treecatg
         X_TREE_ID = lv_x_tree_id
         _SCOPE = lv__scope
. " DEQUEUE_E_HDS_TREE




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_HDS_TREE

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_hds_str_tree_enq) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single CLIENT FROM HDS_STR_TREE_ENQ INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single APPL_ID FROM HDS_STR_TREE_ENQ INTO @DATA(ld_appl_id).
 
"SELECT single TREECATG FROM HDS_STR_TREE_ENQ INTO @DATA(ld_treecatg).
 
"SELECT single TREE_ID FROM HDS_STR_TREE_ENQ INTO @DATA(ld_tree_id).
 
DATA(ld_x_appl_id) = ' '.
 
DATA(ld_x_treecatg) = ' '.
 
DATA(ld_x_tree_id) = ' '.
 
DATA(ld__scope) = '3'.
 


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!