SAP DEQUEUE_E_MDC_HDB_MTC Function Module for Release lock on object E_MDC_HDB_MTC









DEQUEUE_E_MDC_HDB_MTC is a standard dequeue e mdc hdb mtc 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_MDC_HDB_MTC 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 mdc hdb mtc FM, simply by entering the name DEQUEUE_E_MDC_HDB_MTC into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_MDC_HDB_MTC 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_MDC_HDB_MTC'"Release lock on object E_MDC_HDB_MTC
EXPORTING
* MODE_MDC_CONF_HEADER = 'S' "Lock mode for table MDC_CONF_HEADER
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MODE_MDC_CONF_DETAIL = 'E' "Lock mode for table MDC_CONF_DETAIL
* CONF_ID = "01th enqueue argument
* TABLE_NAME = "02th enqueue argument
* FIELD_NAME = "03th enqueue argument
* X_CONF_ID = ' ' "Fill argument 01 with initial value?
* X_TABLE_NAME = ' ' "Fill argument 02 with initial value?
* X_FIELD_NAME = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_MDC_HDB_MTC

MODE_MDC_CONF_HEADER - Lock mode for table MDC_CONF_HEADER

Data type: ENQMODE
Default: 'S'
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)

MODE_MDC_CONF_DETAIL - Lock mode for table MDC_CONF_DETAIL

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

CONF_ID - 01th enqueue argument

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

TABLE_NAME - 02th enqueue argument

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

FIELD_NAME - 03th enqueue argument

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

X_CONF_ID - Fill argument 01 with initial value?

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

X_TABLE_NAME - Fill argument 02 with initial value?

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

X_FIELD_NAME - Fill argument 03 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_MDC_HDB_MTC 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_mdc_conf_header  TYPE ENQMODE, "   'S'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mode_mdc_conf_detail  TYPE ENQMODE, "   'E'
lv_conf_id  TYPE MDC_CONF_HEADER-CONF_ID, "   
lv_table_name  TYPE MDC_CONF_DETAIL-TABLE_NAME, "   
lv_field_name  TYPE MDC_CONF_DETAIL-FIELD_NAME, "   
lv_x_conf_id  TYPE MDC_CONF_DETAIL, "   SPACE
lv_x_table_name  TYPE MDC_CONF_DETAIL, "   SPACE
lv_x_field_name  TYPE MDC_CONF_DETAIL, "   SPACE
lv__scope  TYPE MDC_CONF_DETAIL. "   '3'

  CALL FUNCTION 'DEQUEUE_E_MDC_HDB_MTC'  "Release lock on object E_MDC_HDB_MTC
    EXPORTING
         MODE_MDC_CONF_HEADER = lv_mode_mdc_conf_header
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MODE_MDC_CONF_DETAIL = lv_mode_mdc_conf_detail
         CONF_ID = lv_conf_id
         TABLE_NAME = lv_table_name
         FIELD_NAME = lv_field_name
         X_CONF_ID = lv_x_conf_id
         X_TABLE_NAME = lv_x_table_name
         X_FIELD_NAME = lv_x_field_name
         _SCOPE = lv__scope
. " DEQUEUE_E_MDC_HDB_MTC




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_MDC_HDB_MTC

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_mdc_conf_header) = 'S'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
DATA(ld_mode_mdc_conf_detail) = 'E'.
 
"SELECT single CONF_ID FROM MDC_CONF_HEADER INTO @DATA(ld_conf_id).
 
"SELECT single TABLE_NAME FROM MDC_CONF_DETAIL INTO @DATA(ld_table_name).
 
"SELECT single FIELD_NAME FROM MDC_CONF_DETAIL INTO @DATA(ld_field_name).
 
DATA(ld_x_conf_id) = ' '.
 
DATA(ld_x_table_name) = ' '.
 
DATA(ld_x_field_name) = ' '.
 
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!