SAP SDOK_QUE_DEL_TRACE_VALUE Function Module for
SDOK_QUE_DEL_TRACE_VALUE is a standard sdok que del trace value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sdok que del trace value FM, simply by entering the name SDOK_QUE_DEL_TRACE_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDOK_QUEUEING_TRACING
Program Name: SAPLSDOK_QUEUEING_TRACING
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDOK_QUE_DEL_TRACE_VALUE 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 'SDOK_QUE_DEL_TRACE_VALUE'".
EXPORTING
* IF_GLOBAL_DELETE = "
TABLES
QUERY = "
IMPORTING Parameters details for SDOK_QUE_DEL_TRACE_VALUE
IF_GLOBAL_DELETE -
Data type: SY-DATAROptional: Yes
Call by Reference: Yes
TABLES Parameters details for SDOK_QUE_DEL_TRACE_VALUE
QUERY -
Data type: SDOKQUPROPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDOK_QUE_DEL_TRACE_VALUE 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: | ||||
| lt_query | TYPE STANDARD TABLE OF SDOKQUPROP, " | |||
| lv_if_global_delete | TYPE SY-DATAR. " |
|   CALL FUNCTION 'SDOK_QUE_DEL_TRACE_VALUE' " |
| EXPORTING | ||
| IF_GLOBAL_DELETE | = lv_if_global_delete | |
| TABLES | ||
| QUERY | = lt_query | |
| . " SDOK_QUE_DEL_TRACE_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM SDOK_QUE_DEL_TRACE_VALUE
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.| "SELECT single DATAR FROM SY INTO @DATA(ld_if_global_delete). | ||||
Search for further information about these or an SAP related objects