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

Function DEQUEUE_E_SRT_UDS_CFG 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_SRT_UDS_CFG'"Release lock on object E_SRT_UDS_CFG.
EXPORTING
* MODE_SRT_UDS_CONFIG = 'X' "Lock mode for table SRT_UDS_CONFIG
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* INTERFACE = "02th enqueue argument
* OPERATION = "03th enqueue argument
* ADDRESSING_TYPE = "04th enqueue argument
* X_INTERFACE = ' ' "Fill argument 02 with initial value?
* X_OPERATION = ' ' "Fill argument 03 with initial value?
* X_ADDRESSING_TYPE = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
IMPORTING Parameters details for DEQUEUE_E_SRT_UDS_CFG
MODE_SRT_UDS_CONFIG - Lock mode for table SRT_UDS_CONFIG
Data type: ENQMODEDefault: 'X'
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: SRT_UDS_CONFIG-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
INTERFACE - 02th enqueue argument
Data type: SRT_UDS_CONFIG-INTERFACEOptional: Yes
Call by Reference: No ( called with pass by value option)
OPERATION - 03th enqueue argument
Data type: SRT_UDS_CONFIG-OPERATIONOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESSING_TYPE - 04th enqueue argument
Data type: SRT_UDS_CONFIG-ADDRESSING_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_INTERFACE - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_OPERATION - Fill argument 03 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_ADDRESSING_TYPE - 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_E_SRT_UDS_CFG 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_srt_uds_config | TYPE ENQMODE, " 'X' | |||
| lv__synchron | TYPE ENQMODE, " SPACE | |||
| lv__collect | TYPE DDENQCOLL, " ' ' | |||
| lv_mandt | TYPE SRT_UDS_CONFIG-MANDT, " SY-MANDT | |||
| lv_interface | TYPE SRT_UDS_CONFIG-INTERFACE, " | |||
| lv_operation | TYPE SRT_UDS_CONFIG-OPERATION, " | |||
| lv_addressing_type | TYPE SRT_UDS_CONFIG-ADDRESSING_TYPE, " | |||
| lv_x_interface | TYPE SRT_UDS_CONFIG, " SPACE | |||
| lv_x_operation | TYPE SRT_UDS_CONFIG, " SPACE | |||
| lv_x_addressing_type | TYPE SRT_UDS_CONFIG, " SPACE | |||
| lv__scope | TYPE SRT_UDS_CONFIG. " '3' |
|   CALL FUNCTION 'DEQUEUE_E_SRT_UDS_CFG' "Release lock on object E_SRT_UDS_CFG |
| EXPORTING | ||
| MODE_SRT_UDS_CONFIG | = lv_mode_srt_uds_config | |
| _SYNCHRON | = lv__synchron | |
| _COLLECT | = lv__collect | |
| MANDT | = lv_mandt | |
| INTERFACE | = lv_interface | |
| OPERATION | = lv_operation | |
| ADDRESSING_TYPE | = lv_addressing_type | |
| X_INTERFACE | = lv_x_interface | |
| X_OPERATION | = lv_x_operation | |
| X_ADDRESSING_TYPE | = lv_x_addressing_type | |
| _SCOPE | = lv__scope | |
| . " DEQUEUE_E_SRT_UDS_CFG | ||
ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_SRT_UDS_CFG
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_srt_uds_config) | = 'X'. | |||
| DATA(ld__synchron) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
| "SELECT single MANDT FROM SRT_UDS_CONFIG INTO @DATA(ld_mandt). | ||||
| DATA(ld_mandt) | = SY-MANDT. | |||
| "SELECT single INTERFACE FROM SRT_UDS_CONFIG INTO @DATA(ld_interface). | ||||
| "SELECT single OPERATION FROM SRT_UDS_CONFIG INTO @DATA(ld_operation). | ||||
| "SELECT single ADDRESSING_TYPE FROM SRT_UDS_CONFIG INTO @DATA(ld_addressing_type). | ||||
| DATA(ld_x_interface) | = ' '. | |||
| DATA(ld_x_operation) | = ' '. | |||
| DATA(ld_x_addressing_type) | = ' '. | |||
| DATA(ld__scope) | = '3'. | |||
Search for further information about these or an SAP related objects