Why are transport requests not included in the TM Workflow?

Owned by Alena Saeuberlich
Last updated: May 19, 2021 by Maria Hald
3 min read

Problem

After approval, transport requests are not automatically included in the Transport Management Workflow.

 

Cause

Different causes are possible depending on the configuration. The following are known causes:

  1. The BADIs for inclusion in the Workflow are not active

  2. The user does not have sufficient permissions

  3. POC users have been maintained in the BADI configuration

  4. There is an error when using the loader program

  5. Job RDDFDBCK is not scheduled

  6. If a certain SAP release is in use (error occurs with Basis Releases 701 and 702), which has problems reading the ALOG via 'TRINT_FI_READ_ALOG' (see SAP Note 1093839), the BADI 'Feedback-After-Export' not executed.

  7. There is another technical error

 

Solution

Depending on the configuration, the following points must be checked:

General points:

  1. Check the BADI settings in transaction / RTC / TM_BADI. It is important to ensure that the correct SID of the TM server has been entered.

  2. Check whether users are in the POC list.

    1. Users are entered: Only these users have the opportunity to include transports in the TM when they are released

    2. The list is empty: all users have this option

  3. Make sure that both BADIs are active (/ RTC / TM BEFORE EXP 1, / RTC / TM AFTER EXP 01). In some cases it can help to deactivate and reactivate it once.

  4. Check the authorizations of the sharing user. So that the transport can be included in the Transport Management Workflow after it has been released, appropriate authorizations must be assigned for the authorization object ZRTC_TM depending on the project, target route and transport level. You can use transaction SU53 to find out which authorizations the respective user is missing.

  5. Make sure that the job RDDFDBCK is scheduled (is controlled by RDDIMPDP and scheduled by RDDNEWPP)

 

If you use the distribution via the report / RTC / TM_LD_15, please also check the following points:

  1. Make sure that the option "Distribution with report / RTC / TM_LD_15" has been selected in the transaction / RTC / TM_BADI.

  2. Look in transaction / RTC / TM_BADI in the Event ID field to see whether an event has been entered. This event is required to trigger the Loader when a transport request is released on the development system. If no event is specified, it may have to be created first. To do this, call transaction SM62 and create an event (e.g. Z_TM_TRIGGER) and then assign this event in the BADI transaction.

  3. Check whether a variant for the program / RTC / TM_LD_15 has been created on the development system and create it if necessary.

  4. Check whether a periodic job is scheduled on the development system that calls the program / RTC / TM_LD_15. Here again the event that was specified in the BADI transaction; trigger the job. If no job is scheduled, schedule one.

  5. If the loader is configured correctly and the problem occurs only sporadically, contact support for further error analysis.

 

There is a workaround for cause point 6:

ONLY VALID FOR SAP Release 7.01 and 7.02, as the TM-BAdI is not triggered by SAP here.

For distributed scenarios (TM server <> Dev.system)

  • Step 1: Execute report / RTC / TM_AFTER_EXP_01

  • Step 2: Schedule report / RTC / TM_LD_15 in a periodic background job.

Please note the important sequence!

 

For non-distributed scenarios (TM server = Dev.system)

  • only the above-mentioned 1st step - execute report / RTC / TM_AFTER_EXP_01 - is of importance. The 2nd step is completely omitted.