SAP OXT_TASK_CHECK Function Module for
OXT_TASK_CHECK is a standard oxt task check 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 oxt task check FM, simply by entering the name OXT_TASK_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: OXT_TASK_API
Program Name: SAPLOXT_TASK_API
Main Program: SAPLOXT_TASK_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function OXT_TASK_CHECK 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 'OXT_TASK_CHECK'".
EXPORTING
IV_TASKGUID = "ID of OXT Task
IV_DEVCLASS = "Package
IV_SETTYPENAME = "Set type for OXT task
TABLES
T_RETURN = "Return Parameters
T_TRANSPORTS = "Transports of an EEW Project
IMPORTING Parameters details for OXT_TASK_CHECK
IV_TASKGUID - ID of OXT Task
Data type: OXT_TASKIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_DEVCLASS - Package
Data type: DEVCLASSOptional: No
Call by Reference: No ( called with pass by value option)
IV_SETTYPENAME - Set type for OXT task
Data type: OXT_SETTYPENAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OXT_TASK_CHECK
T_RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
T_TRANSPORTS - Transports of an EEW Project
Data type: OXT_RT_TRANSPORTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXT_TASK_CHECK 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_t_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_taskguid | TYPE OXT_TASKID, " | |||
| lv_iv_devclass | TYPE DEVCLASS, " | |||
| lt_t_transports | TYPE STANDARD TABLE OF OXT_RT_TRANSPORT, " | |||
| lv_iv_settypename | TYPE OXT_SETTYPENAME. " |
|   CALL FUNCTION 'OXT_TASK_CHECK' " |
| EXPORTING | ||
| IV_TASKGUID | = lv_iv_taskguid | |
| IV_DEVCLASS | = lv_iv_devclass | |
| IV_SETTYPENAME | = lv_iv_settypename | |
| TABLES | ||
| T_RETURN | = lt_t_return | |
| T_TRANSPORTS | = lt_t_transports | |
| . " OXT_TASK_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM OXT_TASK_CHECK
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.Search for further information about these or an SAP related objects