SAP DEQUEUE_ESZDM_CC_TBTRACE Function Module for Release lock on object ESZDM_CC_TBTRACE









DEQUEUE_ESZDM_CC_TBTRACE is a standard dequeue eszdm cc tbtrace 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 ESZDM_CC_TBTRACE 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 eszdm cc tbtrace FM, simply by entering the name DEQUEUE_ESZDM_CC_TBTRACE into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_ESZDM_CC_TBTRACE 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_ESZDM_CC_TBTRACE'"Release lock on object ESZDM_CC_TBTRACE
EXPORTING
* MODE_SZDM_CC_TB_TRACE = 'E' "Lock mode for table SZDM_CC_TB_TRACE
* OBJECT_TYPE = "Enqueue argument 01
* OBJECT_NAME = "Enqueue argument 02
* X_OBJECT_TYPE = ' ' "Fill argument 01 with initial value?
* X_OBJECT_NAME = ' ' "Fill argument 02 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_ESZDM_CC_TBTRACE

MODE_SZDM_CC_TB_TRACE - Lock mode for table SZDM_CC_TB_TRACE

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

OBJECT_TYPE - Enqueue argument 01

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

OBJECT_NAME - Enqueue argument 02

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

X_OBJECT_TYPE - Fill argument 01 with initial value?

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

X_OBJECT_NAME - Fill argument 02 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)

Copy and paste ABAP code example for DEQUEUE_ESZDM_CC_TBTRACE 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_szdm_cc_tb_trace  TYPE ENQMODE, "   'E'
lv_object_type  TYPE SZDM_CC_TB_TRACE-OBJECT_TYPE, "   
lv_object_name  TYPE SZDM_CC_TB_TRACE-OBJECT_NAME, "   
lv_x_object_type  TYPE SZDM_CC_TB_TRACE, "   SPACE
lv_x_object_name  TYPE SZDM_CC_TB_TRACE, "   SPACE
lv__scope  TYPE SZDM_CC_TB_TRACE, "   '3'
lv__synchron  TYPE SZDM_CC_TB_TRACE, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_ESZDM_CC_TBTRACE'  "Release lock on object ESZDM_CC_TBTRACE
    EXPORTING
         MODE_SZDM_CC_TB_TRACE = lv_mode_szdm_cc_tb_trace
         OBJECT_TYPE = lv_object_type
         OBJECT_NAME = lv_object_name
         X_OBJECT_TYPE = lv_x_object_type
         X_OBJECT_NAME = lv_x_object_name
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_ESZDM_CC_TBTRACE




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ESZDM_CC_TBTRACE

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_szdm_cc_tb_trace) = 'E'.
 
"SELECT single OBJECT_TYPE FROM SZDM_CC_TB_TRACE INTO @DATA(ld_object_type).
 
"SELECT single OBJECT_NAME FROM SZDM_CC_TB_TRACE INTO @DATA(ld_object_name).
 
DATA(ld_x_object_type) = ' '.
 
DATA(ld_x_object_name) = ' '.
 
DATA(ld__scope) = '3'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 


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!