Mass Transports (SAP Library - Change and Transport System)

Mass Transports

Purpose

Mass transports are a good solution if you have a large number of transports to administrate and want to automate the process as much as possible.

The continuous use of mass transports is the most secure way of keeping your system synchronized and consistent.

Before you import mass imports into your production systems, you must check all requests in the quality assurance system and confirm their transport into other systems. Use the TMS Quality Assurance procedure when doing this.

If you only want to import some of your development projects into your production systems, use the projects to control the transports. You can then pick and choose the requests you want to transport by project.

Features

The CTS offers the following functions for using mass imports in your system landscape:

When you release requests in the Transport Organizer, the requests are automatically placed in the import queue of the target system (usually the quality assurance system).
You can display the import queues in TMS, and then schedule or start the imports.
You can use the import monitor to check any imports that are running.
All completed import steps are recorded by the system. You can then display them in the import history.
TMS registers transport errors as alerts, which you can then display and analyze in the CCMS Alert Monitor.

Process Flow

Queue-controlled mass transports are based on the following process flow:

Configure transport routes between your development, quality assurance and production clients.

Note

If you mainly develop Customizing and work with multiple clients in one SAP System, use Extended Transport Control to define transport routes between clients more exactly.

You also need to define mass imports as the import method for the relevant systems. To do this, choose the transport strategy Queue-controlled mass imports.

You can also choose to activate the TMS quality assurance procedure to protect your production systems.

Specify the dates on which you want to make transports into the different clients in your system landscape. Announce these dates and times to all users; for example, developers need to know when transports are made into the production system so that they can check whether the relevant functions are in the QA system beforehand.

The administrator can schedule the imports periodically in TMS, or start each import manually.

Only import single change requests (single imports) before others in the queue in special cases. Change requests that are imported in advance by the TMS are imported again in the regular import. You can use the transport workflow to import single imports in advance.

Only delete requests from the import queue in special cases; this applies particularly to the import queue of the production system. Otherwise, the consistency of the systems cannot be guaranteed, resulting in serious problems for development, test and support. If a change request contains objects with errors, then you must correct these errors in the development system. You need to import the change request with the corrected object together with the faulty requests. The correct import sequence makes sure that the corrected version is used.