SAP OXT_TASKSEQ_DELETE Function Module for
OXT_TASKSEQ_DELETE is a standard oxt taskseq delete 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 taskseq delete FM, simply by entering the name OXT_TASKSEQ_DELETE 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): Normal Function Module
Update:

Function OXT_TASKSEQ_DELETE 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_TASKSEQ_DELETE'".
EXPORTING
IV_EXTENSIONID = "OXT Object GUID
* IV_EXTVERSION_NEW = "Version of an extension
* IV_EXTVERSION_OLD = "Version of an extension
* IV_EXTVERSION_OLD2 = "Version of an extension
* IV_DEVCLASS = "Package
* IV_FLAG_DEL_GEN_OBJS = '' "
* IV_FLAG_DEL_TRANSLIST = '' "
* IV_FLAG_STOP_BEF_GEN = '' "
TABLES
T_RETURN = "Return Parameters
* T_TRANSPORTS = "Transports of an EEW Project
* T_DEVCLASS = "
EXCEPTIONS
TASKFRAMEWORK_ERROR = 1 GENERATOR_ERROR = 2 CONNECTION_ERROR = 3 ACTION_CANCELLED = 4
IMPORTING Parameters details for OXT_TASKSEQ_DELETE
IV_EXTENSIONID - OXT Object GUID
Data type: OXT_EXTENSIONIDOptional: No
Call by Reference: Yes
IV_EXTVERSION_NEW - Version of an extension
Data type: OXT_EXTVERSIONOptional: Yes
Call by Reference: Yes
IV_EXTVERSION_OLD - Version of an extension
Data type: OXT_EXTVERSIONOptional: Yes
Call by Reference: Yes
IV_EXTVERSION_OLD2 - Version of an extension
Data type: OXT_EXTVERSIONOptional: Yes
Call by Reference: Yes
IV_DEVCLASS - Package
Data type: DEVCLASSOptional: Yes
Call by Reference: Yes
IV_FLAG_DEL_GEN_OBJS -
Data type: FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
IV_FLAG_DEL_TRANSLIST -
Data type: FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
IV_FLAG_STOP_BEF_GEN -
Data type: FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for OXT_TASKSEQ_DELETE
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: Yes
Call by Reference: Yes
T_DEVCLASS -
Data type: OXT_RT_DEVCLASSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
TASKFRAMEWORK_ERROR -
Data type:Optional: No
Call by Reference: Yes
GENERATOR_ERROR -
Data type:Optional: No
Call by Reference: Yes
CONNECTION_ERROR - RFC Error
Data type:Optional: No
Call by Reference: Yes
ACTION_CANCELLED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXT_TASKSEQ_DELETE 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_extensionid | TYPE OXT_EXTENSIONID, " | |||
| lv_taskframework_error | TYPE OXT_EXTENSIONID, " | |||
| lt_t_transports | TYPE STANDARD TABLE OF OXT_RT_TRANSPORT, " | |||
| lv_generator_error | TYPE OXT_RT_TRANSPORT, " | |||
| lv_iv_extversion_new | TYPE OXT_EXTVERSION, " | |||
| lt_t_devclass | TYPE STANDARD TABLE OF OXT_RT_DEVCLASS, " | |||
| lv_connection_error | TYPE OXT_RT_DEVCLASS, " | |||
| lv_iv_extversion_old | TYPE OXT_EXTVERSION, " | |||
| lv_action_cancelled | TYPE OXT_EXTVERSION, " | |||
| lv_iv_extversion_old2 | TYPE OXT_EXTVERSION, " | |||
| lv_iv_devclass | TYPE DEVCLASS, " | |||
| lv_iv_flag_del_gen_objs | TYPE FLAG, " '' | |||
| lv_iv_flag_del_translist | TYPE FLAG, " '' | |||
| lv_iv_flag_stop_bef_gen | TYPE FLAG. " '' |
|   CALL FUNCTION 'OXT_TASKSEQ_DELETE' " |
| EXPORTING | ||
| IV_EXTENSIONID | = lv_iv_extensionid | |
| IV_EXTVERSION_NEW | = lv_iv_extversion_new | |
| IV_EXTVERSION_OLD | = lv_iv_extversion_old | |
| IV_EXTVERSION_OLD2 | = lv_iv_extversion_old2 | |
| IV_DEVCLASS | = lv_iv_devclass | |
| IV_FLAG_DEL_GEN_OBJS | = lv_iv_flag_del_gen_objs | |
| IV_FLAG_DEL_TRANSLIST | = lv_iv_flag_del_translist | |
| IV_FLAG_STOP_BEF_GEN | = lv_iv_flag_stop_bef_gen | |
| TABLES | ||
| T_RETURN | = lt_t_return | |
| T_TRANSPORTS | = lt_t_transports | |
| T_DEVCLASS | = lt_t_devclass | |
| EXCEPTIONS | ||
| TASKFRAMEWORK_ERROR = 1 | ||
| GENERATOR_ERROR = 2 | ||
| CONNECTION_ERROR = 3 | ||
| ACTION_CANCELLED = 4 | ||
| . " OXT_TASKSEQ_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM OXT_TASKSEQ_DELETE
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_iv_flag_del_gen_objs) | = ''. | |||
| DATA(ld_iv_flag_del_translist) | = ''. | |||
| DATA(ld_iv_flag_stop_bef_gen) | = ''. | |||
Search for further information about these or an SAP related objects