SAP DEQUEUE_E_MDQ_RULE_DATA Function Module for Release lock on object E_MDQ_RULE_DATA









DEQUEUE_E_MDQ_RULE_DATA is a standard dequeue e mdq rule data 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_MDQ_RULE_DATA 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 mdq rule data FM, simply by entering the name DEQUEUE_E_MDQ_RULE_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_MDQ_RULE_DATA 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_MDQ_RULE_DATA'"Release lock on object E_MDQ_RULE_DATA
EXPORTING
* MODE_MDQ_RULE_DATA = 'E' "Lock mode for table MDQ_RULE_DATA
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* RULE_REPOSITORY = "02th enqueue argument
* RULE_ID = "03th enqueue argument
* VERSION = "04th enqueue argument
* X_RULE_REPOSITORY = ' ' "Fill argument 02 with initial value?
* X_RULE_ID = ' ' "Fill argument 03 with initial value?
* X_VERSION = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_MDQ_RULE_DATA

MODE_MDQ_RULE_DATA - Lock mode for table MDQ_RULE_DATA

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)

MANDT - 01th enqueue argument

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

RULE_REPOSITORY - 02th enqueue argument

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

RULE_ID - 03th enqueue argument

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

VERSION - 04th enqueue argument

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

X_RULE_REPOSITORY - Fill argument 02 with initial value?

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

X_RULE_ID - Fill argument 03 with initial value?

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

X_VERSION - 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_MDQ_RULE_DATA 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_mdq_rule_data  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE MDQ_RULE_DATA-MANDT, "   SY-MANDT
lv_rule_repository  TYPE MDQ_RULE_DATA-RULE_REPOSITORY, "   
lv_rule_id  TYPE MDQ_RULE_DATA-RULE_ID, "   
lv_version  TYPE MDQ_RULE_DATA-VERSION, "   
lv_x_rule_repository  TYPE MDQ_RULE_DATA, "   SPACE
lv_x_rule_id  TYPE MDQ_RULE_DATA, "   SPACE
lv_x_version  TYPE MDQ_RULE_DATA, "   SPACE
lv__scope  TYPE MDQ_RULE_DATA. "   '3'

  CALL FUNCTION 'DEQUEUE_E_MDQ_RULE_DATA'  "Release lock on object E_MDQ_RULE_DATA
    EXPORTING
         MODE_MDQ_RULE_DATA = lv_mode_mdq_rule_data
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         RULE_REPOSITORY = lv_rule_repository
         RULE_ID = lv_rule_id
         VERSION = lv_version
         X_RULE_REPOSITORY = lv_x_rule_repository
         X_RULE_ID = lv_x_rule_id
         X_VERSION = lv_x_version
         _SCOPE = lv__scope
. " DEQUEUE_E_MDQ_RULE_DATA




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_MDQ_RULE_DATA

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_mdq_rule_data) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM MDQ_RULE_DATA INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single RULE_REPOSITORY FROM MDQ_RULE_DATA INTO @DATA(ld_rule_repository).
 
"SELECT single RULE_ID FROM MDQ_RULE_DATA INTO @DATA(ld_rule_id).
 
"SELECT single VERSION FROM MDQ_RULE_DATA INTO @DATA(ld_version).
 
DATA(ld_x_rule_repository) = ' '.
 
DATA(ld_x_rule_id) = ' '.
 
DATA(ld_x_version) = ' '.
 
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!