SAP TR_SCHEDULE_TRANSP_DISP Function Module for Scheduling of the transport displatcher as a background job
TR_SCHEDULE_TRANSP_DISP is a standard tr schedule transp disp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Scheduling of the transport displatcher as a background job 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 tr schedule transp disp FM, simply by entering the name TR_SCHEDULE_TRANSP_DISP into the relevant SAP transaction such as SE37 or SE38.
Function Group: STRS
Program Name: SAPLSTRS
Main Program:
Appliation area: S
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TR_SCHEDULE_TRANSP_DISP 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_SCHEDULE_TRANSP_DISP'"Scheduling of the transport displatcher as a background job.
EXPORTING
* IV_BY_EVENT = 'X' "Flag:'X'=start of transp. disp. after event
* IV_LOG_TO_FILE = ' ' "Flag:'X'=log interface used
* IV_FORCED = ' ' "Flag:'X'=overwrite existing schedule
* IV_JOBCLASS = 'C' "
EXCEPTIONS
SCHEDULE_FAILED = 1 NO_AUTHORIZATION = 2
IMPORTING Parameters details for TR_SCHEDULE_TRANSP_DISP
IV_BY_EVENT - Flag:'X'=start of transp. disp. after event
Data type: TRPARI-W_VALIDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOG_TO_FILE - Flag:'X'=log interface used
Data type: TRPARI-W_VALIDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_FORCED - Flag:'X'=overwrite existing schedule
Data type: TRPARI-W_VALIDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_JOBCLASS -
Data type: BTCJOBCLASDefault: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SCHEDULE_FAILED - Scheduling of transport dispatcher failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORIZATION - No authorization for execution
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TR_SCHEDULE_TRANSP_DISP 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_by_event | TYPE TRPARI-W_VALID, " 'X' | |||
| lv_schedule_failed | TYPE TRPARI, " | |||
| lv_iv_log_to_file | TYPE TRPARI-W_VALID, " ' ' | |||
| lv_no_authorization | TYPE TRPARI, " | |||
| lv_iv_forced | TYPE TRPARI-W_VALID, " ' ' | |||
| lv_iv_jobclass | TYPE BTCJOBCLAS. " 'C' |
|   CALL FUNCTION 'TR_SCHEDULE_TRANSP_DISP' "Scheduling of the transport displatcher as a background job |
| EXPORTING | ||
| IV_BY_EVENT | = lv_iv_by_event | |
| IV_LOG_TO_FILE | = lv_iv_log_to_file | |
| IV_FORCED | = lv_iv_forced | |
| IV_JOBCLASS | = lv_iv_jobclass | |
| EXCEPTIONS | ||
| SCHEDULE_FAILED = 1 | ||
| NO_AUTHORIZATION = 2 | ||
| . " TR_SCHEDULE_TRANSP_DISP | ||
ABAP code using 7.40 inline data declarations to call FM TR_SCHEDULE_TRANSP_DISP
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 W_VALID FROM TRPARI INTO @DATA(ld_iv_by_event). | ||||
| DATA(ld_iv_by_event) | = 'X'. | |||
| "SELECT single W_VALID FROM TRPARI INTO @DATA(ld_iv_log_to_file). | ||||
| DATA(ld_iv_log_to_file) | = ' '. | |||
| "SELECT single W_VALID FROM TRPARI INTO @DATA(ld_iv_forced). | ||||
| DATA(ld_iv_forced) | = ' '. | |||
| DATA(ld_iv_jobclass) | = 'C'. | |||
Search for further information about these or an SAP related objects