Show TOC

Component documentationCentral Change and Transport System Locate this document in the navigation structure


The central Change and Transport System (central CTS) enhances the classic CTS with functions for complex heterogenous system landscapes, which allow you to control transports within a transport landscape centrally. This means you can combine multiple systems in your transport landscape into system clusters. You can bundle transports between these clusters using transport collections. A transport collection is a combination of the transports from the different systems of a cluster.

SAP Solution Manager represents the central CTS server that is responsible for the central management of the transport landscape. You can control transports in the managed systems from the central CTS server.

Implementation Considerations

The functions of the central CTS are provided as an add-on to SAP Solution Manager, the CTS plug-in. The CTS plug-in is part of the SL Toolset product.

Central CTS is available for SAP Solution Manager 7.1 SP 10 and higher.

Managed systems can have the following releases:

  • ABAP systems: For more information on the releases of the managed systems that are supported by central CTS plus the required tp and R3trans versions, refer to SAP Note 1665940.

  • Non-ABAP systems: The enhanced CTS must be configured for the non-ABAP system and SAP Solution Manager must be used as the domain controller and communication system.

You can use the central CTS functions if the CTS plug-in is installed in SAP Solution Manager. The CTS plug-in is part of the SAP Solution Manager SP stack. You obtain it by importing the SP stack. For more information on the installation of the CTS plug-in, refer to SAP Note 1665940.

Use of central CTS is optional. You can use it to exploit the enhanced flexibility functions in Change Request Management (ChaRM) and Quality Gate Management (QGM). Before you implement central CTS for your transports, you should check whether it is suitable for your situation. You can also continue to use classic CTS, TMS, or classic ChaRM and QGM.

If you want to test whether the functions of central CTS are suitable for your requirements, you can use the central CTS at first just for part of your landscape or for part of your projects, or even for a test project.


Central CTS enhances the existing Change and Transport System. You can only use central CTS in connection with the existing CTS. Depending on the configuration of central CTS, it is possible that some functions of the existing CTS are disabled. For example, if the central control of transports is activated, then the local execution of transports in the systems can be deactivated. Central CTS is integrated in ChaRM and QGM of SAP Solution Manager. It is required if you want to use the enhanced flexibility functions.


Combine individual systems with content dependencies into system clusters

  • Those systems in your transport landscape that you want to supply with transports at the same time can be grouped into clusters. In this way you can, for example, combine Business Suite development systems with a Portal development system into a single cluster. You can also combine the relevant consolidation, test, and production systems into their own clusters. This means, you create system clusters for systems that have the same role (for example, DEV, QAS, and PRD).

  • You can combine ABAP and non-ABAP systems into a system cluster.

  • System cluster definitions are made centrally for your transport landscapes in the central CTS server.

Combine transports into transport collections

  • You create transport collections to combine transports from different systems. In this way you can, for example, transport ABAP developments together with non-ABAP developments.

  • After exporting a transport collection you can add further transport requests to the transport collection. The transport collection can then be imported again. Only the changed transport requests are imported again. This means, for example, you can collect all related transport requests in a collection which contains both a new version of an application as well as the necessary corrections for that application.

    Note Note

    You create transport collections in ChaRM or QGM.

    End of the note.