SAP SDOK_QUE_ADD_OBJECT Function Module for
SDOK_QUE_ADD_OBJECT is a standard sdok que add object 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 add object FM, simply by entering the name SDOK_QUE_ADD_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDOK_QUEUEING
Program Name: SAPLSDOK_QUEUEING
Main Program: SAPLSDOK_QUEUEING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDOK_QUE_ADD_OBJECT 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_ADD_OBJECT'".
EXPORTING
IS_OBJECT_PARAMS = "
* IV_PRESELECT_TIME = "
* IV_PRESELECT_DATE = "
EXCEPTIONS
INVALID_CUSTOMIZING = 1 INVALID_IMPORT_PARAM = 2
IMPORTING Parameters details for SDOK_QUE_ADD_OBJECT
IS_OBJECT_PARAMS -
Data type: SDOK_OBJECT_TO_QUEUEOptional: No
Call by Reference: Yes
IV_PRESELECT_TIME -
Data type: SY-UZEITOptional: Yes
Call by Reference: Yes
IV_PRESELECT_DATE -
Data type: SY-DATUMOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_CUSTOMIZING -
Data type:Optional: No
Call by Reference: Yes
INVALID_IMPORT_PARAM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDOK_QUE_ADD_OBJECT 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_is_object_params | TYPE SDOK_OBJECT_TO_QUEUE, " | |||
| lv_invalid_customizing | TYPE SDOK_OBJECT_TO_QUEUE, " | |||
| lv_iv_preselect_time | TYPE SY-UZEIT, " | |||
| lv_invalid_import_param | TYPE SY, " | |||
| lv_iv_preselect_date | TYPE SY-DATUM. " |
|   CALL FUNCTION 'SDOK_QUE_ADD_OBJECT' " |
| EXPORTING | ||
| IS_OBJECT_PARAMS | = lv_is_object_params | |
| IV_PRESELECT_TIME | = lv_iv_preselect_time | |
| IV_PRESELECT_DATE | = lv_iv_preselect_date | |
| EXCEPTIONS | ||
| INVALID_CUSTOMIZING = 1 | ||
| INVALID_IMPORT_PARAM = 2 | ||
| . " SDOK_QUE_ADD_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM SDOK_QUE_ADD_OBJECT
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 UZEIT FROM SY INTO @DATA(ld_iv_preselect_time). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_iv_preselect_date). | ||||
Search for further information about these or an SAP related objects