Transports of SAP XI/PI/PO objects have always been something that has not really improved much over time.
Once support to export transport via CTS+ nothing more happened. Sure you could bundle it with ChaRM to get some better processes.
It still had a number of drawbacks
- You need to document how communication channels should be modified once imported
- You need to perform the change of the channels to match the requirements (and is that done or do they make a few extra changes?
- It is difficult to view which objects has been changed from a transport
- Is the object you change tested
Probably around 50% of SAP PI/PO customers are using CTS+ or ChaRM as a transport process because it has come connections with parts of the delivery process. We needed to find a good way to support it.
We have now created a solution that allows using your normal CTS+ transport process, but instead spending time handling manual steps and approvals. The Figaf DevOps Tool can handle much of the process, so the delivery process becomes much easier.
You will still need to perform some manual steps in your process, but they will be easier to see what is going on and how make which changes.
The process is shown on this slide
You can see the tool in action in this video.
What to give it a try
If you want to see how to set it up the manual https://figaf.com/help/irt/latest/#e2e-development-flow-cts-transports
It is pretty simple to get started. In most cases you can try it out on your laptop in 1-2 hours.
Just sign up for the DevOps Tool on the page and get started.