SAP TRINT_CHECK_REQUEST_TASK_ID Function Module for Internal: Check Request Number/Task Number (Type, Assignment)

Search SAP Function Modules

TRINT_CHECK_REQUEST_TASK_ID is a standard trint check request task id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Check Request Number/Task Number (Type, Assignment) 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 trint check request task id FM, simply by entering the name TRINT_CHECK_REQUEST_TASK_ID into the relevant SAP transaction such as SE37 or SE38.

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

Function TRINT_CHECK_REQUEST_TASK_ID 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_CHECK_REQUEST_TASK_ID'"Internal: Check Request Number/Task Number (Type, Assignment)
  EXPORTING
   IV_REQUESTID =  "Request number
*  IV_TASKID =  "Task number

 IMPORTING
   EV_AUTHOR =  "Request author or task author
   EV_TYPE =  "Request type or task type
   EV_CLIENT =  "Source client
   EV_TEXT =  "Request short text

EXCEPTIONS
   NO_REQUEST = 1    NO_TASK = 2    WRONG_REQUEST = 3    NOT_EXIST_E070 = 4    NO_AUTHORIZATION = 5    ELSE = 6 

.

IMPORTING Parameters details for TRINT_CHECK_REQUEST_TASK_ID

IV_REQUESTID - Request number

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

IV_TASKID - Task number

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

EXPORTING Parameters details for TRINT_CHECK_REQUEST_TASK_ID

EV_AUTHOR - Request author or task author

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

EV_TYPE - Request type or task type

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

EV_CLIENT - Source client

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

EV_TEXT - Request short text

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

EXCEPTIONS details

NO_REQUEST - REQUESTID is not a request number

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

NO_TASK - TASKID is not a task number

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

WRONG_REQUEST - Task does not belong to the specified request

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

NOT_EXIST_E070 - Request number or task number does not exist

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

NO_AUTHORIZATION - No authorization

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

ELSE - Other errors

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

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

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