SAP TRINT_READ_REQUEST Function Module for Read Individual Parts of a Request (Subsequently)
TRINT_READ_REQUEST is a standard trint read request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Individual Parts of a Request (Subsequently) 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 read request FM, simply by entering the name TRINT_READ_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCTS_REQUEST_SELECTION
Program Name: SAPLSCTS_REQUEST_SELECTION
Main Program: SAPLSCTS_REQUEST_SELECTION
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function TRINT_READ_REQUEST 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_READ_REQUEST'"Read Individual Parts of a Request (Subsequently).
EXPORTING
* IV_READ_E070 = ' ' "'X': Read request header information
* IV_READ_E07T = ' ' "'X': Read request short text
* IV_READ_E070C = ' ' "'X': Read request client
* IV_READ_E070M = ' ' "'X': Read request client
* IV_READ_OBJS_KEYS = ' ' "'X': Read objects and key of the request
* IV_READ_OBJS = ' ' "
* IV_READ_ATTRIBUTES = ' ' "'X': Read request attributes
* IV_SUPPRESS_LOCKFLAG_HANDLING = ' ' "
IMPORTING
EV_E07T_DOESNT_EXIST = "
EV_E070C_DOESNT_EXIST = "
EV_E070M_DOESNT_EXIST = "
CHANGING
CS_REQUEST = "Complete request
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for TRINT_READ_REQUEST
IV_READ_E070 - 'X': Read request header information
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_E07T - 'X': Read request short text
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_E070C - 'X': Read request client
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_E070M - 'X': Read request client
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_OBJS_KEYS - 'X': Read objects and key of the request
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_OBJS -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_ATTRIBUTES - 'X': Read request attributes
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUPPRESS_LOCKFLAG_HANDLING -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TRINT_READ_REQUEST
EV_E07T_DOESNT_EXIST -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EV_E070C_DOESNT_EXIST -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EV_E070M_DOESNT_EXIST -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for TRINT_READ_REQUEST
CS_REQUEST - Complete request
Data type: TRWBO_REQUESTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OCCURED - Error during reading
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRINT_READ_REQUEST 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_cs_request | TYPE TRWBO_REQUEST, " | |||
lv_iv_read_e070 | TYPE C, " ' ' | |||
lv_error_occured | TYPE C, " | |||
lv_ev_e07t_doesnt_exist | TYPE C, " | |||
lv_iv_read_e07t | TYPE C, " ' ' | |||
lv_ev_e070c_doesnt_exist | TYPE C, " | |||
lv_iv_read_e070c | TYPE C, " ' ' | |||
lv_ev_e070m_doesnt_exist | TYPE C, " | |||
lv_iv_read_e070m | TYPE C, " ' ' | |||
lv_iv_read_objs_keys | TYPE C, " ' ' | |||
lv_iv_read_objs | TYPE C, " ' ' | |||
lv_iv_read_attributes | TYPE C, " ' ' | |||
lv_iv_suppress_lockflag_handling | TYPE C. " ' ' |
  CALL FUNCTION 'TRINT_READ_REQUEST' "Read Individual Parts of a Request (Subsequently) |
EXPORTING | ||
IV_READ_E070 | = lv_iv_read_e070 | |
IV_READ_E07T | = lv_iv_read_e07t | |
IV_READ_E070C | = lv_iv_read_e070c | |
IV_READ_E070M | = lv_iv_read_e070m | |
IV_READ_OBJS_KEYS | = lv_iv_read_objs_keys | |
IV_READ_OBJS | = lv_iv_read_objs | |
IV_READ_ATTRIBUTES | = lv_iv_read_attributes | |
IV_SUPPRESS_LOCKFLAG_HANDLING | = lv_iv_suppress_lockflag_handling | |
IMPORTING | ||
EV_E07T_DOESNT_EXIST | = lv_ev_e07t_doesnt_exist | |
EV_E070C_DOESNT_EXIST | = lv_ev_e070c_doesnt_exist | |
EV_E070M_DOESNT_EXIST | = lv_ev_e070m_doesnt_exist | |
CHANGING | ||
CS_REQUEST | = lv_cs_request | |
EXCEPTIONS | ||
ERROR_OCCURED = 1 | ||
. " TRINT_READ_REQUEST |
ABAP code using 7.40 inline data declarations to call FM TRINT_READ_REQUEST
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_read_e070) | = ' '. | |||
DATA(ld_iv_read_e07t) | = ' '. | |||
DATA(ld_iv_read_e070c) | = ' '. | |||
DATA(ld_iv_read_e070m) | = ' '. | |||
DATA(ld_iv_read_objs_keys) | = ' '. | |||
DATA(ld_iv_read_objs) | = ' '. | |||
DATA(ld_iv_read_attributes) | = ' '. | |||
DATA(ld_iv_suppress_lockflag_handling) | = ' '. | |||
Search for further information about these or an SAP related objects