SAP DEQUEUE_E_MPE_BUYOFF Function Module for Release lock on object E_MPE_BUYOFF









DEQUEUE_E_MPE_BUYOFF is a standard dequeue e mpe buyoff 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_MPE_BUYOFF 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 mpe buyoff FM, simply by entering the name DEQUEUE_E_MPE_BUYOFF 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_MPE_BUYOFF 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_MPE_BUYOFF'"Release lock on object E_MPE_BUYOFF
  EXPORTING
*  MODE_MPE_BUYOFFSTEPS = 'E' "Lock mode for table MPE_BUYOFFSTEPS
*  CLIENT = SY-MANDT "01th enqueue argument
*  MFGBUYOFFCYCLE =  "02th enqueue argument
*  MFGBUYOFFSTEP =  "03th enqueue argument
*  X_MFGBUYOFFCYCLE = ' ' "Fill argument 02 with initial value?
*  X_MFGBUYOFFSTEP = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '3' "
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
.



IMPORTING Parameters details for DEQUEUE_E_MPE_BUYOFF

MODE_MPE_BUYOFFSTEPS - Lock mode for table MPE_BUYOFFSTEPS

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

CLIENT - 01th enqueue argument

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

MFGBUYOFFCYCLE - 02th enqueue argument

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

MFGBUYOFFSTEP - 03th enqueue argument

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

X_MFGBUYOFFCYCLE - Fill argument 02 with initial value?

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

X_MFGBUYOFFSTEP - 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_E_MPE_BUYOFF 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_mpe_buyoffsteps  TYPE ENQMODE, "   'E'
lv_client  TYPE MPE_BUYOFFSTEPS-CLIENT, "   SY-MANDT
lv_mfgbuyoffcycle  TYPE MPE_BUYOFFSTEPS-MFGBUYOFFCYCLE, "   
lv_mfgbuyoffstep  TYPE MPE_BUYOFFSTEPS-MFGBUYOFFINTERNALID, "   
lv_x_mfgbuyoffcycle  TYPE MPE_BUYOFFSTEPS, "   SPACE
lv_x_mfgbuyoffstep  TYPE MPE_BUYOFFSTEPS, "   SPACE
lv__scope  TYPE MPE_BUYOFFSTEPS, "   '3'
lv__synchron  TYPE MPE_BUYOFFSTEPS, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'DEQUEUE_E_MPE_BUYOFF'  "Release lock on object E_MPE_BUYOFF
    EXPORTING
         MODE_MPE_BUYOFFSTEPS = lv_mode_mpe_buyoffsteps
         CLIENT = lv_client
         MFGBUYOFFCYCLE = lv_mfgbuyoffcycle
         MFGBUYOFFSTEP = lv_mfgbuyoffstep
         X_MFGBUYOFFCYCLE = lv_x_mfgbuyoffcycle
         X_MFGBUYOFFSTEP = lv_x_mfgbuyoffstep
         _SCOPE = lv__scope
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
. " DEQUEUE_E_MPE_BUYOFF




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_MPE_BUYOFF

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_mpe_buyoffsteps) = 'E'.
 
"SELECT single CLIENT FROM MPE_BUYOFFSTEPS INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single MFGBUYOFFCYCLE FROM MPE_BUYOFFSTEPS INTO @DATA(ld_mfgbuyoffcycle).
 
"SELECT single MFGBUYOFFINTERNALID FROM MPE_BUYOFFSTEPS INTO @DATA(ld_mfgbuyoffstep).
 
DATA(ld_x_mfgbuyoffcycle) = ' '.
 
DATA(ld_x_mfgbuyoffstep) = ' '.
 
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!