Modifiable Transport Requests are now available for SAP cloud modifications as well

I’m pleased to announce the availability of a brand-new feature in SAP Cloud Transport Management. The most recent release, which went live this week, allows you to create modifiable transport requests. Many of you are likely familiar with this feature from the Change and Transport System (CTS) of the ABAP stack; however, this time, it applies to SAP cloud changes that are integrated with SAP Cloud Transport Management, such as numerous SAP BTP changes.

Modifiable transport requests can be manually created with the feature’s initial version. They are still in the process of being fully integrated into the capabilities of SAP Cloud ALM for change and deployment management as well as other UIs from content providers. However, we are collaborating with colleagues to clarify the options for integration and determine the most effective flow with change management. However, you can begin using it right away to gain initial experience.

In particular, you can now create a new modifiable transport request by specifying the source node, content type, and description in the Transport Requests view of SAP Cloud Transport Management. You can now use an open shell to add content to it by clicking on the newly created transport request and going to the Content tab to add or modify the content you want to propagate.

The idea is that you can now test the transport and the involved changes to a defined scope of test nodes (such as TST and PRE-PROD) – you can adapt the scope of test nodes, but it is not allowed to comprise the final node of your transport landscape, as this is considered to be the production node, where no testing should be allowed.

You select the Tracking view for testing: You can then update the content of the transport based on the results of these tests—for example, by adding more files, exchanging files, removing files, or changing the order of comprised files—before testing once more until you are satisfied with the result. Only then, you release the transport request and with this, add it as unmodifiable transport request to the first-level nodes again, but this time as “normal” transport request in status released that you process like any other transport and that can then also go to the last node of your defined transport landscape (considered a production node).