SAP TRINT_LAST_TASK_SET Function Module for

Search SAP Function Modules

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

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

Function TRINT_LAST_TASK_SET 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 'TRINT_LAST_TASK_SET'"
  EXPORTING
*  IV_ORDER_TYPE = 'K' "Request type (K, L, W)
*  IV_CATEGORY = 'SYST' "Request category: SYST, CUST, CUSYq
*  IV_CLIENT = SY-MANDT "Request source client (for type W)
*  IV_ORDER = ' ' "Request last used
*  IV_TASK = ' ' "Task last used

EXCEPTIONS
   INVALID_USERNAME = 1    INVALID_ORDER_TYPE = 2    INVALID_CATEGORY = 3    INVALID_CLIENT = 4    INVALID_ORDER = 5    INVALID_TASK = 6 

.

IMPORTING Parameters details for TRINT_LAST_TASK_SET

IV_ORDER_TYPE - Request type (K, L, W)

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

IV_CATEGORY - Request category: SYST, CUST, CUSYq

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)

IV_ORDER - Request last used

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

IV_TASK - Task last used

Data type: E070-TRKORR
Default: SPACE
Optional: Yes
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_ORDER_TYPE - Invalid request type

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)

INVALID_ORDER - Invalid request

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

INVALID_TASK - Invalid task

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

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

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