SAP has introduced new way of moving Changes across the systems in the SAP landscape. This concept is called Central CTS (Change & Transport System).
Transport Requests are created in each Development systems for their landscapes, like ECC, BI, Portal, etc. There requests will be combined in one unite for the Development cluster. That will be a new Transport request at cluster level, which helps moving changes from cluster to cluster.
You would need clusters for the different system roles to keep your changes together. So you would e.g. create a development cluster containing the ERP, the BW and the BO development system, a test cluster containing the ERP test system, the BW and the BO test system and a cluster containing the respective productive systems.
Clusters are represented by an SID in TMS like any other system, but it is not a real system that you have to install. You can assign an SID consisting of three letters which does not yet exist in the landscape. Then systems can be added to this cluster.
Clusters are made for combining the systems – in addition, an entity is needed which can contain all the changed objects that require a transport. There has to be something like a transport request for clusters. This entity is called “Transport Collection”. A collection can contain transport requests for all development systems added to the appropriate cluster. There can be several requests created for one of the development systems of the cluster in one collection. It is also valid to have transport requests for only some of the systems inside a collection.
Transport Routes are defined between clusters and Transport Collections are transported between clusters.
- Solution Manager as a Managing System and a Domain Controller
- Clusters are configured in Solution Manager
- Managed systems are controlled by Solution Manager
- Managed Systems can be a Domain Controller of their individual landscape
- Managed System should have Service Plug-in CTS_PLUG_200
- Domain Links are required between Solution Manager and other Domains.
- Solution Manager should be at least on version 7.1 SPS 10
- SAP Solution Manager 7.1 SP10/FP2
- tp version 380.05.18 or higher (720 kernel)
- R3trans with a release date of 06.03.12 or later (720 kernel)
- Managed Systems
- Non-ABAP Systems: CTS+ is configured. It does not matter whether loose or close coupling is used on import or export side. A representation of the non-ABAP systems in TMS is needed.
- Domain Controller/communication system of non-ABAP Systems: If the SAP Solution Manager is not used as DC/communication system for the non-ABAP Systems, the DC/communication system has to be on SAP NetWeaver 7.31 with CTS_PLUG installed at least.
- All managed systems with at least tp version 380.05.18 or higher (720 kernel) and R3trans with a release date of 06.03.12 or later (720 kernel)
- Systems that you want to use with central CTS should meet the requirements specified above.
- Start the Central CTS Configuration Web UI in your central CTS server.
Your central CTS server is your SAP Solution Manager system. Start the Central CTS Configuration Web UI there to perform all configuration tasks, call transaction SZENCONFIG.
- Select the systems that you want to configure for central CTS and validate their statuses.
Before you can start configuring your systems for central CTS you need to find out if the systems fulfill the requirements for this. To do this, select the systems that you want to use with central CTS and choose Validate.
The system checks which configuration tasks have already been performed. Depending on the result, the system shows you which tasks you still need to perform.
- Complete the missing configuration tasks.
An overall status is displayed for each system that has been validated. If all configuration tasks have been performed, this is indicated by a green traffic light icon. If there are configuration tasks missing or if the system could not calculate a result, this is indicated by a red traffic light icon. To view the results, choose See Details in the Status column. The dialog box displays a list of status messages. If you select a status message in the upper area of the dialog box, the long text of the message is displayed in the lower area of the dialog box. If a column contains a link with an error message, selecting the link either lets you perform the configuration task or provides more information about the required task.
This can include the following tasks:
- Creating system clusters
- Creating RFC connections to the managed systems
- Setting TMS parameters that are required for usingcentral CTS
- Distributing plug-ins to the managed systems
Depending on the task that you have performed and on your personal settings, the system may automatically trigger validation (when assigning systems to clusters, for example). If this is not the case, choose Validate after performing the task to retrieve the current configuration status.
- Perform the configuration steps for all systems that you want to configure for central CTS.
If all traffic lights are green for all systems that you want to use with central CTS, you must still perform the following steps.
- Establish connection to the system clusters.
To enable transports between clusters you need to define transport routes between the clusters. You do this in the same way as for systems in Transport Management System in your central CTS server.
- Establish the connection of the individual systems that are contained in the clusters.
After you have configured the transport routes at cluster level, you must define the transport process of the individual systems. You do this by defining the import targets for all target systems that belong to a cluster.
- Activate and Distribute the TMS configuration to all systems in the transport domain.
Perform this task once you have completed the configuration steps for all the systems that you want to use with central CTS. To distribute the configuration to all systems in the transport domain, choose Distribute Configuration in the central CTS Configuration Web UI.
- It gives full control over the change movements and transparency of change executions
- It provides additional function to be used with ChaRM to increase consistency and minimize manual efforts
- It provides fully integrated transports mechanism to manage changes across technology stacks and different application components
- When used with ChaRM, it proves Solution Manager as a Single Source of Truth to avoid and Manage risks of application changes in the projects
- It provides SAP’s best practice utilizing ITIL standards to implement Transport Management