Why aren't transport orders pushed to the next level?

Problem

Cause

These causes are possible:

1. The transport was successfully imported into the target system, but the job for automatic advancement ("switcher job") has not yet run.

2. The transport to the target system was incorrect. A higher return code was reported than was specified in the variant of the switcher job.

3. The transport was successfully imported into the target system, but the time specified in the variant of the switcher job has not yet passed.

4. Several systems are supplied in the current transport stage. You are using the setting "Synchronization at level level" and the transport request has not yet run into every system.

5. For another technical reason, a successfully imported transport request did not receive an import flag.

Solution

Depending on the cause (see above), please check the following points:

1. Make sure that the switcher job runs regularly (e.g. every 2 minutes) on the Transport Management System and, if necessary, schedule this if you want an automated status change. The program / RTC / TM_STATUS_SWITCHER is used by default. A variant is required for each automated status change, usually one variant per transport stage.

2. Check your development and try again. Alternatively, you can increase the threshold value for the return code (do not change if RC> =) for the relevant variant of the switcher job.

3. Wait until the transport job has reached the required minimum age (time after import) or shorten the period (import older than n minutes) for the relevant variant of the switcher job.

4. Wait until all systems in the transport level have been delivered or activate the option "No synchronization at level level" in the global settings.

5. Examine the job logs on the Transport Management System for abnormalities. Sometimes there are e.g. B. Dependencies on other transports or the transport is in a package and can therefore not be pushed further individually.