SAP TR_READ_TRANSPORT_INFO Function Module for
TR_READ_TRANSPORT_INFO is a standard tr read transport info 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 tr read transport info FM, simply by entering the name TR_READ_TRANSPORT_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: STRQ
Program Name: SAPLSTRQ
Main Program: SAPLSTRQ
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TR_READ_TRANSPORT_INFO 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_READ_TRANSPORT_INFO'".
EXPORTING
* IV_DIRTYPE = 'T' "Directory type: T(ransport), P(ut)
* IV_FROM_DATE = SY-DATUM "Lower date limit for last transp. step
* IV_TO_DATE = SY-DATUM "Upper date limit for last transp. step
* IV_MIN_MAXERR = 0 "Lower limit for max. return code
* IV_COMMIT_COUNT = 50 "Number of file accesses to COMMIT;0 = no COMMIT
TABLES
TT_USER = "User table for transports to be analyzed
TT_TRANSPORT = "Table of transports to be analyzed
TT_SYSTEM = "System table for relevant transp. steps
TT_TRINFO = "Table of transport information read
EXCEPTIONS
NO_INFO_FOUND = 1
IMPORTING Parameters details for TR_READ_TRANSPORT_INFO
IV_DIRTYPE - Directory type: T(ransport), P(ut)
Data type: TSTRF01-DIRTYPEDefault: 'T'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FROM_DATE - Lower date limit for last transp. step
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TO_DATE - Upper date limit for last transp. step
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_MIN_MAXERR - Lower limit for max. return code
Data type: TSTRFCOFIL-RETCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_COMMIT_COUNT - Number of file accesses to COMMIT;0 = no COMMIT
Data type: SY-INDEXDefault: 50
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TR_READ_TRANSPORT_INFO
TT_USER - User table for transports to be analyzed
Data type: TSTRFUSEROptional: No
Call by Reference: No ( called with pass by value option)
TT_TRANSPORT - Table of transports to be analyzed
Data type: TSTRFTRANSOptional: No
Call by Reference: No ( called with pass by value option)
TT_SYSTEM - System table for relevant transp. steps
Data type: TSTRFSYSTOptional: No
Call by Reference: No ( called with pass by value option)
TT_TRINFO - Table of transport information read
Data type: TSTRFTRINFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_INFO_FOUND - Information was not found for any user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TR_READ_TRANSPORT_INFO 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: | ||||
| lt_tt_user | TYPE STANDARD TABLE OF TSTRFUSER, " | |||
| lv_iv_dirtype | TYPE TSTRF01-DIRTYPE, " 'T' | |||
| lv_no_info_found | TYPE TSTRF01, " | |||
| lv_iv_from_date | TYPE SY-DATUM, " SY-DATUM | |||
| lt_tt_transport | TYPE STANDARD TABLE OF TSTRFTRANS, " | |||
| lt_tt_system | TYPE STANDARD TABLE OF TSTRFSYST, " | |||
| lv_iv_to_date | TYPE SY-DATUM, " SY-DATUM | |||
| lt_tt_trinfo | TYPE STANDARD TABLE OF TSTRFTRINF, " | |||
| lv_iv_min_maxerr | TYPE TSTRFCOFIL-RETCODE, " 0 | |||
| lv_iv_commit_count | TYPE SY-INDEX. " 50 |
|   CALL FUNCTION 'TR_READ_TRANSPORT_INFO' " |
| EXPORTING | ||
| IV_DIRTYPE | = lv_iv_dirtype | |
| IV_FROM_DATE | = lv_iv_from_date | |
| IV_TO_DATE | = lv_iv_to_date | |
| IV_MIN_MAXERR | = lv_iv_min_maxerr | |
| IV_COMMIT_COUNT | = lv_iv_commit_count | |
| TABLES | ||
| TT_USER | = lt_tt_user | |
| TT_TRANSPORT | = lt_tt_transport | |
| TT_SYSTEM | = lt_tt_system | |
| TT_TRINFO | = lt_tt_trinfo | |
| EXCEPTIONS | ||
| NO_INFO_FOUND = 1 | ||
| . " TR_READ_TRANSPORT_INFO | ||
ABAP code using 7.40 inline data declarations to call FM TR_READ_TRANSPORT_INFO
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 DIRTYPE FROM TSTRF01 INTO @DATA(ld_iv_dirtype). | ||||
| DATA(ld_iv_dirtype) | = 'T'. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_iv_from_date). | ||||
| DATA(ld_iv_from_date) | = SY-DATUM. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_iv_to_date). | ||||
| DATA(ld_iv_to_date) | = SY-DATUM. | |||
| "SELECT single RETCODE FROM TSTRFCOFIL INTO @DATA(ld_iv_min_maxerr). | ||||
| "SELECT single INDEX FROM SY INTO @DATA(ld_iv_commit_count). | ||||
| DATA(ld_iv_commit_count) | = 50. | |||
Search for further information about these or an SAP related objects