Central CTS – How is it going?
It has been over a year since we first introduced the concepts behind central CTS here on SDN. We used this time wisely and built, what we believe to be the first step of the most powerful version of the SAP Change and Transport System ever. Over the course of the last year, we wrote a lot of code, discussed concepts, visited customers in the context of the Customer Engagement Initiative, gathered early feedback, presented a first version at SAP TechEd 2010 and made a major step towards a first delivery. However, there might be a little grain of salt here as well: our first shipment (we call it ‘version one’) will most likely not be available for general use, but we plan to make it available to a selected set of customers at first, who agreed to test-drive central CTS during the Customer Engagement Initiative. As we make progress with version two and its delivery, we will keep you informed about a general availability of the release.
For those, who might not really know much about central CTS, its concepts, ideas and solutions, let me give a quick recap on what we intend to deliver. From an evolutionary perspective, one could describe the growth of CTS as a step by step introduction of a set of tools able to handle more and more change management requirements that arose around SAP ecosystems.
It all started with the core CTS introduced in 1992. Over the years it was improved in an iterative fashion. Due to the fact, that system landscape grew more diverse over the years, including non-ABAP and even non-SAP systems, CTS was enhanced in 2007 to handle such landscapes with the well known and supported transport tools. A common transport system for different technologies was highly appreciated. However, it did not cover all aspects arising from divers landscapes: What about cross-technology dependent changes? What about downgrades and so-called ‘over takers’? What about integration into higher level change management tools and processes? With central CTS, we plan to address some of those questions and create the next generation CTS. If you could not make it to SAP TechEd 2010, allow me to share two helpful links with you: the complete set of slides of the session ALM210: CTS – it’s one tool to control your changes is available online, a live recording can be found here: Virtual SAP TechEd. Central CTS is not just an extension or enhancement of CTS, but together with CTS+ and the core CTS it constitutes the next generation CTS.
Please remember, that your feedback is honestly appreciated by the whole team developing central CTS – so keep it coming!
I enjoyed your blog as it allowed me to catch up on CTS as I wasn’t able to go to TechEd this year. I do have a question, how would CTS work with parallel landscapes? We have two streams, one for BAU and one for projects. Will CTS be able to help detect possible conflicts between developments environments?
Hello Christian,
I've been following cCTS now for a couple of years, since 2009 when it was first announced. Is this technology still being progressed?
Hello,
Finally when cCTS is available?
Thank you.
Hi Christian,
Is Central CTS already available in SAP SM 7.1 or has been integrated within SAP SM 7.1 Change Request Management? Still is a prototype and concept?
I've found a very nice whitepaper regarding Central CTS dated from 2009 and since then there's no further info.
Cheers,
Hi Fernando,
thanks for the question!
As a matter of fact, cCTS is not a prototype anymore - it is planned to be delivered publicly as part of SAP Solution Manager 7.1 SP 10 and will be tightly integrated into SAP Change Request Management. Using cCTS, ChaRM will gain project flexibility features, multitrack support and end-to-end downgrade protection.
We are planning a series of blog post about this, I'll update you once they are live.
Best regards,
Christian