When we get to discussions related to release management processes, for example, during the implementation of Change Request Management (ChaRM), it is not uncommon to find extremely complex requirements related to the transport of changes across the system landscape. The use of external transports and reassignment of released changes are just a few of the possible situations that can be easily solved by central Change and Transport System (cCTS). In order to clarify the basic functionalities of cCTS, this document will describe how to use cCTS with ChaRM projects.
cCTS with ChaRM
The usage of cCTS is optional, however, it is not possible to use it as a stand-alone tool.
Therefore, to be able to reproduce this guide you will need:
- ChaRM or QGM implemented
- cCTS implemented
That way, the following steps will describe how to activate cCTS with ChaRM projects.
You will define if cCTS is used or not in the Landscape Definition of the Change Cycle.
On the second step, you have the option to activate the cCTS for this Change Cycle.
Then, the clusters defined in the cCTS configuration should be defined.
In the Transport Track Overview, you can see that the associated clusters are also defined in the systems landscape.
When cCTS is activated, the task list will include also the clusters in the system landscape definition:
From the processual point of view, cCTS does not change how the Change Documents in the ChaRM are processed.
Therefore, only the cCTS functionalities will be additionally provided.
- External transports: Transport requests originated from other systems can be assigned to change documents and transported following all the release definitions by ChaRM.
External transport request imported into de development system.
Assignment of a request from SMD into FSB.
- Decouple/Assignment of released transports: with cCTS it is possible to reassign released transport requests to other Change Documents.
Release transport request.
Assignment of the transport request.
- Transporting request with Task List: with cCTS activated, the import job can be executed for the clusters.
In the Task List, you can also execute the job “Import Transport Request for Cluster”.
The transport should be executed as usual.
The transport history can be tracked in the Transport Request Log.