Before you transport requests between systems, choose a transport strategy that meets your requirements.
For more information, see Transport Strategy in the CTS.
The transport strategy is set by default to queue-controlled mass transports. If you want to work with single transports or workflow-controlled transports instead, change the configuration as described here.
You have configured transport routes between the systems.
Within a system group you must set all systems either to Queue-controlled transports or Workflow-controlled transports.
The following settings are made, according to transport strategy:
By default, the import option Leave transport request in queue for later import is activated.
The import option Leave transport request in queue for later import causes requests that have been imported as single transports to be imported in the correct order in the next import of all requests. This option is useful if you have to make preliminary imports for individual requests. This prevents older objects from being imported at the next regular import of all the requests (overshooter problem).
By default, the import option Leave transport request in queue for later import is deactivated.
If you supply a system only with single transports, this option is not useful since the requests remain in the queue after the import and have to be manually deleted from the import queue.
For more information, see Transport Workflow.
See also: