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 CTS offers the following functions for using mass imports in your system landscape:
Queue-controlled mass transports are based on the following process flow:
Configuretransport routes between your development, quality assurance and production clients.
If you mainly develop Customizing and work with multiple clients in one SAP System, use
You also need to define mass imports as the import method for the relevant systems. To do this, choose thetransport strategy Queue-controlled mass imports.
You can also choose to activate theTMS 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 thetransport 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.