SAP DEQUEUE_EN1ME_MEORDER Function Module for Release lock on object EN1ME_MEORDER









DEQUEUE_EN1ME_MEORDER is a standard dequeue en1me meorder 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 EN1ME_MEORDER 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 en1me meorder FM, simply by entering the name DEQUEUE_EN1ME_MEORDER into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_EN1ME_MEORDER 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_EN1ME_MEORDER'"Release lock on object EN1ME_MEORDER
EXPORTING
* MODE_RN1ME_LOCK_ORDER = 'E' "Lock mode for table RN1ME_LOCK_ORDER
* MANDT = SY-MANDT "01th enqueue argument
* PATNR = "02th enqueue argument
* MEORDID = "03th enqueue argument
* X_PATNR = ' ' "Fill argument 02 with initial value?
* X_MEORDID = ' ' "Fill argument 03 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_EN1ME_MEORDER

MODE_RN1ME_LOCK_ORDER - Lock mode for table RN1ME_LOCK_ORDER

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

MANDT - 01th enqueue argument

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

PATNR - 02th enqueue argument

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

MEORDID - 03th enqueue argument

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

X_PATNR - Fill argument 02 with initial value?

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

X_MEORDID - 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)

_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_EN1ME_MEORDER 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_rn1me_lock_order  TYPE ENQMODE, "   'E'
lv_mandt  TYPE RN1ME_LOCK_ORDER-MANDT, "   SY-MANDT
lv_patnr  TYPE RN1ME_LOCK_ORDER-PATNR, "   
lv_meordid  TYPE RN1ME_LOCK_ORDER-MEORDID, "   
lv_x_patnr  TYPE RN1ME_LOCK_ORDER, "   SPACE
lv_x_meordid  TYPE RN1ME_LOCK_ORDER, "   SPACE
lv__scope  TYPE RN1ME_LOCK_ORDER, "   '3'
lv__synchron  TYPE RN1ME_LOCK_ORDER, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_EN1ME_MEORDER'  "Release lock on object EN1ME_MEORDER
    EXPORTING
         MODE_RN1ME_LOCK_ORDER = lv_mode_rn1me_lock_order
         MANDT = lv_mandt
         PATNR = lv_patnr
         MEORDID = lv_meordid
         X_PATNR = lv_x_patnr
         X_MEORDID = lv_x_meordid
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_EN1ME_MEORDER




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EN1ME_MEORDER

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_rn1me_lock_order) = 'E'.
 
"SELECT single MANDT FROM RN1ME_LOCK_ORDER INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single PATNR FROM RN1ME_LOCK_ORDER INTO @DATA(ld_patnr).
 
"SELECT single MEORDID FROM RN1ME_LOCK_ORDER INTO @DATA(ld_meordid).
 
DATA(ld_x_patnr) = ' '.
 
DATA(ld_x_meordid) = ' '.
 
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!