Entering content frameProcedure documentation Choosing a Transport Strategy Locate the document in its SAP Library structure

Use

Before you transport requests between systems, choose a transport strategy that meets your requirements.

For more information, see Structure link Transport Strategy in the CTS.

Note

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.

Prerequisites

You have configured transport routes between the systems.

Procedure

  1. In the TMS initial screen, choose This graphic is explained in the accompanying text. The screen Display Transport Routes appears displaying the existing transport routes in the transport domain.
  2. Switch to the change mode by choosing Configuration ® Display <-> Change.
  3. Position the cursor on the SAP System for which you want to choose a transport strategy.
  4. Choose Edit ® System ® Change. The dialog box Change System Attributes appears.
  5. Choose the tab System attributes and choose your transport strategy.
  6. Note

    Within a system group you must set all systems either to Queue-controlled transports or Workflow-controlled transports. If you choose the strategy Workflow-controlled transports for one system in a system group, TMS also chooses this strategies for all other systems in the system group. You can, however, set Mass transports or Single transports for individual systems.

  7. Choose Copy.
  8. Choose Configuration ® Distribute and activate.

Result

The following settings are made, according to transport strategy:

By default, the import option Leave transport request in queue for later import is activated.

Note

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).

Note

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 Structure link Transport Workflow.

See also:

Transport Control Parameters

 

 

Leaving content frame