SAP DEQUEUE_EPIC_PI_LOCK Function Module for Release lock on object EPIC_PI_LOCK

Search SAP Function Modules

DEQUEUE_EPIC_PI_LOCK is a standard dequeue epic pi lock 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 EPIC_PI_LOCK 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 epic pi lock FM, simply by entering the name DEQUEUE_EPIC_PI_LOCK into the relevant SAP transaction such as SE37 or SE38.

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

Function DEQUEUE_EPIC_PI_LOCK 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_EPIC_PI_LOCK'"Release lock on object EPIC_PI_LOCK
  EXPORTING
*  MODE_EPIC_S_PI_LOCK = 'E' "Lock mode for table EPIC_S_PI_LOCK
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
*  MANDT = SY-MANDT "Enqueue argument 01
*  BUKRS =  "Enqueue argument 02
*  HKTID =  "Enqueue argument 03
*  HBKID =  "Enqueue argument 04
*  X_BUKRS = ' ' "Fill argument 02 with initial value?
*  X_HKTID = ' ' "Fill argument 03 with initial value?
*  X_HBKID = ' ' "Fill argument 04 with initial value?
*  _SCOPE = '3' "

.

IMPORTING Parameters details for DEQUEUE_EPIC_PI_LOCK

MODE_EPIC_S_PI_LOCK - Lock mode for table EPIC_S_PI_LOCK

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 - Enqueue argument 01

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

BUKRS - Enqueue argument 02

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

HKTID - Enqueue argument 03

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

HBKID - Enqueue argument 04

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

X_BUKRS - Fill argument 02 with initial value?

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

X_HKTID - Fill argument 03 with initial value?

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

X_HBKID - 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_EPIC_PI_LOCK 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 DEQUEUE_EPIC_PI_LOCK

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