SAP ENQUEUE_EQQMTB1 Function Module for Request lock for object EQQMTB1

Search SAP Function Modules

ENQUEUE_EQQMTB1 is a standard enqueue eqqmtb1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object EQQMTB1 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 enqueue eqqmtb1 FM, simply by entering the name ENQUEUE_EQQMTB1 into the relevant SAP transaction such as SE37 or SE38.

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

Function ENQUEUE_EQQMTB1 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 'ENQUEUE_EQQMTB1'"Request lock for object EQQMTB1
  EXPORTING
*  MODE_QMTB = 'E' "Lock mode for table QMTB
*  _WAIT = ' ' "
*  _COLLECT = ' ' "Initially only collect lock
*  MANDT = SY-MANDT "01th enqueue argument
*  WERKS =  "02th enqueue argument
*  PMTNR =  "03th enqueue argument
*  VERSION =  "04th enqueue argument
*  X_WERKS = ' ' "Fill argument 02 with initial value?
*  X_PMTNR = ' ' "Fill argument 03 with initial value?
*  X_VERSION = ' ' "Fill argument 04 with initial value?
*  _SCOPE = '2' "

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2 

.

IMPORTING Parameters details for ENQUEUE_EQQMTB1

MODE_QMTB - Lock mode for table QMTB

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

_WAIT -

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

_COLLECT - Initially only collect lock

Data type: DDENQ_LIKE-COLLECT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDT - 01th enqueue argument

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

WERKS - 02th enqueue argument

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

PMTNR - 03th enqueue argument

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

VERSION - 04th enqueue argument

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

X_WERKS - Fill argument 02 with initial value?

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

X_PMTNR - 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: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FOREIGN_LOCK - Object already locked

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

SYSTEM_FAILURE - Internal error from enqueue server

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

Copy and paste ABAP code example for ENQUEUE_EQQMTB1 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.

ABAP code using 7.40 inline data declarations to call FM ENQUEUE_EQQMTB1

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.

Search for further information about these or an SAP related objects