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

Function DEQUEUE_ET52SPS 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_ET52SPS'"Release lock on object ET52SPS.
EXPORTING
* MODE_T52SPS = 'X' "Lock mode for table T52SPS
* X_PARAID = ' ' "Fill argument 05 with initial value?
* _SCOPE = '3' "
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* PROCESSID = "02th enqueue argument
* STEPID = "03th enqueue argument
* RUNID = "04th enqueue argument
* PARAID = "05th enqueue argument
* X_PROCESSID = ' ' "Fill argument 02 with initial value?
* X_STEPID = ' ' "Fill argument 03 with initial value?
* X_RUNID = ' ' "Fill argument 04 with initial value?
IMPORTING Parameters details for DEQUEUE_ET52SPS
MODE_T52SPS - Lock mode for table T52SPS
Data type: ENQMODEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_PARAID - Fill argument 05 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)
MANDT - 01th enqueue argument
Data type: T52SPS-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROCESSID - 02th enqueue argument
Data type: T52SPS-PROCESSIDOptional: Yes
Call by Reference: No ( called with pass by value option)
STEPID - 03th enqueue argument
Data type: T52SPS-STEPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
RUNID - 04th enqueue argument
Data type: T52SPS-RUNIDOptional: Yes
Call by Reference: No ( called with pass by value option)
PARAID - 05th enqueue argument
Data type: T52SPS-PARAIDOptional: Yes
Call by Reference: No ( called with pass by value option)
X_PROCESSID - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_STEPID - Fill argument 03 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_RUNID - Fill argument 04 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DEQUEUE_ET52SPS 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_t52sps | TYPE ENQMODE, " 'X' | |||
| lv_x_paraid | TYPE ENQMODE, " SPACE | |||
| lv__scope | TYPE ENQMODE, " '3' | |||
| lv__synchron | TYPE ENQMODE, " SPACE | |||
| lv__collect | TYPE DDENQCOLL, " ' ' | |||
| lv_mandt | TYPE T52SPS-MANDT, " SY-MANDT | |||
| lv_processid | TYPE T52SPS-PROCESSID, " | |||
| lv_stepid | TYPE T52SPS-STEPID, " | |||
| lv_runid | TYPE T52SPS-RUNID, " | |||
| lv_paraid | TYPE T52SPS-PARAID, " | |||
| lv_x_processid | TYPE T52SPS, " SPACE | |||
| lv_x_stepid | TYPE T52SPS, " SPACE | |||
| lv_x_runid | TYPE T52SPS. " SPACE |
|   CALL FUNCTION 'DEQUEUE_ET52SPS' "Release lock on object ET52SPS |
| EXPORTING | ||
| MODE_T52SPS | = lv_mode_t52sps | |
| X_PARAID | = lv_x_paraid | |
| _SCOPE | = lv__scope | |
| _SYNCHRON | = lv__synchron | |
| _COLLECT | = lv__collect | |
| MANDT | = lv_mandt | |
| PROCESSID | = lv_processid | |
| STEPID | = lv_stepid | |
| RUNID | = lv_runid | |
| PARAID | = lv_paraid | |
| X_PROCESSID | = lv_x_processid | |
| X_STEPID | = lv_x_stepid | |
| X_RUNID | = lv_x_runid | |
| . " DEQUEUE_ET52SPS | ||
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_ET52SPS
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_t52sps) | = 'X'. | |||
| DATA(ld_x_paraid) | = ' '. | |||
| DATA(ld__scope) | = '3'. | |||
| DATA(ld__synchron) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
| "SELECT single MANDT FROM T52SPS INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single PROCESSID FROM T52SPS INTO @DATA(ld_processid). | ||||
| "SELECT single STEPID FROM T52SPS INTO @DATA(ld_stepid). | ||||
| "SELECT single RUNID FROM T52SPS INTO @DATA(ld_runid). | ||||
| "SELECT single PARAID FROM T52SPS INTO @DATA(ld_paraid). | ||||
| DATA(ld_x_processid) | = ' '. | |||
| DATA(ld_x_stepid) | = ' '. | |||
| DATA(ld_x_runid) | = ' '. | |||
Search for further information about these or an SAP related objects