SAP DEQUEUE_EPOWL_QUERY_EDIT Function Module for Release lock on object EPOWL_QUERY_EDIT
DEQUEUE_EPOWL_QUERY_EDIT is a standard dequeue epowl query edit 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 EPOWL_QUERY_EDIT 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 epowl query edit FM, simply by entering the name DEQUEUE_EPOWL_QUERY_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/GEN0000
Program Name: /1BCDWBEN/SAPLGEN0000
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DEQUEUE_EPOWL_QUERY_EDIT 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_EPOWL_QUERY_EDIT'"Release lock on object EPOWL_QUERY_EDIT.
EXPORTING
* MODE_POWL_RESULT = 'X' "Lock mode for table POWL_RESULT
* RESULT_CACHE_ID = "01th enqueue argument
* X_RESULT_CACHE_ID = ' ' "Fill argument 01 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
IMPORTING Parameters details for DEQUEUE_EPOWL_QUERY_EDIT
MODE_POWL_RESULT - Lock mode for table POWL_RESULT
Data type: ENQMODEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
RESULT_CACHE_ID - 01th enqueue argument
Data type: POWL_RESULT-RESULT_CACHE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
X_RESULT_CACHE_ID - Fill argument 01 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: DDENQCOLLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DEQUEUE_EPOWL_QUERY_EDIT 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_powl_result | TYPE ENQMODE, " 'X' | |||
| lv_result_cache_id | TYPE POWL_RESULT-RESULT_CACHE_ID, " | |||
| lv_x_result_cache_id | TYPE POWL_RESULT, " SPACE | |||
| lv__scope | TYPE POWL_RESULT, " '3' | |||
| lv__synchron | TYPE POWL_RESULT, " SPACE | |||
| lv__collect | TYPE DDENQCOLL. " ' ' |
|   CALL FUNCTION 'DEQUEUE_EPOWL_QUERY_EDIT' "Release lock on object EPOWL_QUERY_EDIT |
| EXPORTING | ||
| MODE_POWL_RESULT | = lv_mode_powl_result | |
| RESULT_CACHE_ID | = lv_result_cache_id | |
| X_RESULT_CACHE_ID | = lv_x_result_cache_id | |
| _SCOPE | = lv__scope | |
| _SYNCHRON | = lv__synchron | |
| _COLLECT | = lv__collect | |
| . " DEQUEUE_EPOWL_QUERY_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_EPOWL_QUERY_EDIT
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_powl_result) | = 'X'. | |||
| "SELECT single RESULT_CACHE_ID FROM POWL_RESULT INTO @DATA(ld_result_cache_id). | ||||
| DATA(ld_x_result_cache_id) | = ' '. | |||
| DATA(ld__scope) | = '3'. | |||
| DATA(ld__synchron) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects