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

Function TRINT_TRANSPORT_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_TRANSPORT_REQUEST'".
EXPORTING
* IV_DIALOG = ' ' "
* IV_SUCCESS_MESSAGE = ' ' "
* IV_CALLED_BY_PERFORCE = ' ' "General Indicator
* IV_DISPLAY_EXPORT_LOG = 'X' "Boolean
* IV_SIMULATION = ' ' "
CHANGING
CS_REQUEST = "
EXCEPTIONS
CTS_INITIALIZATION_FAILURE = 1 ENQUEUE_FAILED = 2 EXPORT_FAILED = 3 INVALID_REQUEST = 4
IMPORTING Parameters details for TRINT_TRANSPORT_REQUEST
IV_DIALOG -
Data type: TRBOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUCCESS_MESSAGE -
Data type: TRBOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CALLED_BY_PERFORCE - General Indicator
Data type: TRBOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DISPLAY_EXPORT_LOG - Boolean
Data type: TRBOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SIMULATION -
Data type: TRBOOLEANDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for TRINT_TRANSPORT_REQUEST
CS_REQUEST -
Data type: TRWBO_REQUESTOptional: No
Call by Reference: Yes
EXCEPTIONS details
CTS_INITIALIZATION_FAILURE - System name cannot be determined or invalid length
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORT_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_REQUEST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRINT_TRANSPORT_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_iv_dialog | TYPE TRBOOLEAN, " ' ' | |||
| lv_cs_request | TYPE TRWBO_REQUEST, " | |||
| lv_cts_initialization_failure | TYPE TRWBO_REQUEST, " | |||
| lv_enqueue_failed | TYPE TRWBO_REQUEST, " | |||
| lv_iv_success_message | TYPE TRBOOLEAN, " ' ' | |||
| lv_export_failed | TYPE TRBOOLEAN, " | |||
| lv_iv_called_by_perforce | TYPE TRBOOLEAN, " ' ' | |||
| lv_invalid_request | TYPE TRBOOLEAN, " | |||
| lv_iv_display_export_log | TYPE TRBOOLEAN, " 'X' | |||
| lv_iv_simulation | TYPE TRBOOLEAN. " ' ' |
|   CALL FUNCTION 'TRINT_TRANSPORT_REQUEST' " |
| EXPORTING | ||
| IV_DIALOG | = lv_iv_dialog | |
| IV_SUCCESS_MESSAGE | = lv_iv_success_message | |
| IV_CALLED_BY_PERFORCE | = lv_iv_called_by_perforce | |
| IV_DISPLAY_EXPORT_LOG | = lv_iv_display_export_log | |
| IV_SIMULATION | = lv_iv_simulation | |
| CHANGING | ||
| CS_REQUEST | = lv_cs_request | |
| EXCEPTIONS | ||
| CTS_INITIALIZATION_FAILURE = 1 | ||
| ENQUEUE_FAILED = 2 | ||
| EXPORT_FAILED = 3 | ||
| INVALID_REQUEST = 4 | ||
| . " TRINT_TRANSPORT_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM TRINT_TRANSPORT_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_dialog) | = ' '. | |||
| DATA(ld_iv_success_message) | = ' '. | |||
| DATA(ld_iv_called_by_perforce) | = ' '. | |||
| DATA(ld_iv_display_export_log) | = 'X'. | |||
| DATA(ld_iv_simulation) | = ' '. | |||
Search for further information about these or an SAP related objects