SAP DX_TASK_CHANGE Function Module for









DX_TASK_CHANGE is a standard dx task change 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 dx task change FM, simply by entering the name DX_TASK_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DX_TASK
Program Name: SAPLDX_TASK
Main Program: SAPLDX_TASK
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DX_TASK_CHANGE 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 'DX_TASK_CHANGE'"
  EXPORTING
   PROJECT =  "
   SUBPROJECT =  "
   RUNDEF =  "
   TASK =  "
*  TEXT =  "
*  DIALOG = 'X' "

 IMPORTING
   TASKDATA =  "
   TASKTEXT =  "

EXCEPTIONS
   RUNDEF_DOES_NOT_EXIST = 1    TASK_DOES_NOT_EXIST = 2    RUNS_ALREADY_EXIST = 3    PROGTYPE_NOT_VALID = 4    CANCELED_BY_USER = 5    DB_ERROR = 6    NO_AUTHORITY = 7
.



IMPORTING Parameters details for DX_TASK_CHANGE

PROJECT -

Data type: DXTASKS-PROJECT
Optional: No
Call by Reference: Yes

SUBPROJECT -

Data type: DXTASKS-SUBPROJECT
Optional: No
Call by Reference: Yes

RUNDEF -

Data type: DXTASKS-RUNDEF
Optional: No
Call by Reference: Yes

TASK -

Data type: DXTASKS-TASK
Optional: No
Call by Reference: Yes

TEXT -

Data type: DXTASKS_T-TEXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

DIALOG -

Data type: DXFIELDS-DIALOG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for DX_TASK_CHANGE

TASKDATA -

Data type: DXTASKS
Optional: No
Call by Reference: Yes

TASKTEXT -

Data type: DXTASKS_T-TEXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

RUNDEF_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TASK_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RUNS_ALREADY_EXIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PROGTYPE_NOT_VALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCELED_BY_USER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DB_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DX_TASK_CHANGE 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_project  TYPE DXTASKS-PROJECT, "   
lv_taskdata  TYPE DXTASKS, "   
lv_rundef_does_not_exist  TYPE DXTASKS, "   
lv_tasktext  TYPE DXTASKS_T-TEXT, "   
lv_subproject  TYPE DXTASKS-SUBPROJECT, "   
lv_task_does_not_exist  TYPE DXTASKS, "   
lv_rundef  TYPE DXTASKS-RUNDEF, "   
lv_runs_already_exist  TYPE DXTASKS, "   
lv_task  TYPE DXTASKS-TASK, "   
lv_progtype_not_valid  TYPE DXTASKS, "   
lv_text  TYPE DXTASKS_T-TEXT, "   
lv_canceled_by_user  TYPE DXTASKS_T, "   
lv_dialog  TYPE DXFIELDS-DIALOG, "   'X'
lv_db_error  TYPE DXFIELDS, "   
lv_no_authority  TYPE DXFIELDS. "   

  CALL FUNCTION 'DX_TASK_CHANGE'  "
    EXPORTING
         PROJECT = lv_project
         SUBPROJECT = lv_subproject
         RUNDEF = lv_rundef
         TASK = lv_task
         TEXT = lv_text
         DIALOG = lv_dialog
    IMPORTING
         TASKDATA = lv_taskdata
         TASKTEXT = lv_tasktext
    EXCEPTIONS
        RUNDEF_DOES_NOT_EXIST = 1
        TASK_DOES_NOT_EXIST = 2
        RUNS_ALREADY_EXIST = 3
        PROGTYPE_NOT_VALID = 4
        CANCELED_BY_USER = 5
        DB_ERROR = 6
        NO_AUTHORITY = 7
. " DX_TASK_CHANGE




ABAP code using 7.40 inline data declarations to call FM DX_TASK_CHANGE

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 PROJECT FROM DXTASKS INTO @DATA(ld_project).
 
 
 
"SELECT single TEXT FROM DXTASKS_T INTO @DATA(ld_tasktext).
 
"SELECT single SUBPROJECT FROM DXTASKS INTO @DATA(ld_subproject).
 
 
"SELECT single RUNDEF FROM DXTASKS INTO @DATA(ld_rundef).
 
 
"SELECT single TASK FROM DXTASKS INTO @DATA(ld_task).
 
 
"SELECT single TEXT FROM DXTASKS_T INTO @DATA(ld_text).
 
 
"SELECT single DIALOG FROM DXFIELDS INTO @DATA(ld_dialog).
DATA(ld_dialog) = 'X'.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!