SAP TR_TASK_OVERVIEW Function Module for Set current requests and development classes in Transport Organizer

Search SAP Function Modules

TR_TASK_OVERVIEW is a standard tr task overview SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set current requests and development classes in Transport Organizer processing and below is the pattern details for this FM, 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 tr task overview FM, simply by entering the name TR_TASK_OVERVIEW into the relevant SAP transaction such as SE37 or SE38.

Function Group: STRG
Program Name: SAPLSTRG
Main Program:
Appliation area: S
Release date: 26-Mar-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TR_TASK_OVERVIEW 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 'TR_TASK_OVERVIEW'"Set current requests and development classes in Transport Organizer
  EXPORTING
*  IV_USERNAME = SY-UNAME "User whose settings are being edited
*  IV_CATEGORY = 'SYST' "Request category: SYST, CUST, CUSY
*  IV_CLIENT = SY-MANDT "Request source client (for type W)

 IMPORTING
   EV_ORDER =  "Request set
   EV_TASK =  "Task set
   EV_VALIDDAYS =  "Period of validity set for setting in days
   EV_DEVCLASS =  "Development class set

EXCEPTIONS
   INVALID_USERNAME = 1    INVALID_CATEGORY = 2    INVALID_CLIENT = 3    INTERNAL_ERROR = 4 

.

IMPORTING Parameters details for TR_TASK_OVERVIEW

IV_USERNAME - User whose settings are being edited

Data type: E070USE-USERNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CATEGORY - Request category: SYST, CUST, CUSY

Data type: E070-KORRDEV
Default: 'SYST'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CLIENT - Request source client (for type W)

Data type: E070C-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TR_TASK_OVERVIEW

EV_ORDER - Request set

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

EV_TASK - Task set

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

EV_VALIDDAYS - Period of validity set for setting in days

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

EV_DEVCLASS - Development class set

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

EXCEPTIONS details

INVALID_USERNAME - Invalid user name

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

INVALID_CATEGORY - Invalid request category

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

INVALID_CLIENT - Invalid request source client

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

INTERNAL_ERROR - Runtime Errors

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

Copy and paste ABAP code example for TR_TASK_OVERVIEW 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.

ABAP code using 7.40 inline data declarations to call FM TR_TASK_OVERVIEW

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