Show TOC

Component documentationCentral Change and Transport System

 

Central Change and Transport System (central CTS) enhances the classic CTS with functions for complex heterogeneous system landscapes, which allow you to control transports within a transport landscape centrally. This means you can combine multiple systems of 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 into the managed systems from the central CTS server.

Note Note

Before using central CTS on SAP Solution Manager, read SAP Note 2231041Information published on SAP site Collective Note: central CTS with SAP Solution Manager 7.2.

End of the note.

Implementation Considerations

The functions of central CTS on SAP Solution Manager are provided as part of SAP NetWeaver. In addition, the CTS plug-in (software component CTS_PLUG) is installed in SAP Solution Manager. This classifies SAP Solution Manager as a central CTS server and makes the functions of central CTS available for distribution to the managed systems.

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 as well as on the required tp and R3trans versions, refer to SAP Note 1665940Information published on SAP site.

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

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

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

Integration

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, some functions of the existing CTS might be disabled. For example, if the central control of transports is activated, then the local execution of transports in the systems might be deactivated. Central CTS is integrated into Change Request Management and QGM of SAP Solution Manager. It is required if you want to use the enhanced flexibility functions.

Features

Combine individual systems with content dependencies into system clusters

  • All systems in your transport landscape that you want to supply with transports at the same time can be grouped into clusters. You can combine Business Suite development systems and Portal development systems to form a single cluster. You can also combine the relevant consolidation, test, and production systems into clusters of their own. 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 clusters are defined 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. You can then import the transport collection again but only the changed transport requests will be reimported. This means, for example, that 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 Change Request Management or QGM.

    End of the note.