Transports with Import Queues (SAP Library - Change and Transport System)

Transports with Import Queues

Any changes that your development teams make to Customizing or Repository objects in the development system are not automatically transported to the target systems (such as the quality assurance and production systems) when they are released. When a developer releases a change request, it is only placed in the import queue of the target system. This makes it possible to gather changes in the development system in the import queue over a period of time, and then import them together into a target system (such as the quality assurance system). The request import places the requests in the import queues of the target systems (such as production and training systems). You can make exports and imports into different target systems at different times and with different frequencies.

Note

This allows you, for example, to import a fully tested version of your new developments into your production systems at a time you previously announced to all users.

Import queues can be used as a transition between development and administration. All changes released by developers can be seen immediately by the administrator in the queues. The Transport Management System provides easy-to-use functions for displaying and editing the import queues.

Import queues are a particularly good way of automating transports in your system landscape. They can significantly reduce the amount of work for system administrators responsible for a large number or transports; automation reduces the administrator tasks mainly to monitoring and troubleshooting.

You can choose between two procedures when you use import queues to perform imports:

You can import mass transports into your systems. This procedure imports all requests waiting for import in the queue. All requests are imported into the target systems in the order they were exported. This minimizes the risk of errors in the target systems caused by requests being imported in the wrong order, and the risk of objects being missing in the target system.

Note

Mass imports are particularly well suited for the quality assurance system and production systems in the implementation phase of a project.

You can import single transports into your systems. This procedure makes a selection of requests from the import queue and imports them into the target system. The other requests remain in the import queue, where you can choose to import them later, or not at all. Single imports are the most flexible method, however, they demand more administration.

Note

Single imports are particularly well suited for updating and correcting production systems.

Regardless of whether you choose to import mass imports or single imports into your production systems, we recommend that you use TMS Quality Assurance to protect these systems.