SAP Cloud Transport Management service (cTMS)
Short definition
cTMS is a cloud service on SAP BTP that transports development content such as UI5 apps, MTA projects, ABAP Cloud objects or iFlows across different subaccounts. For BTP, it therefore plays the role that STMS and CTS play in the ABAP world. It is aimed mainly at development teams and system administrators who want to move BTP content securely and consistently.
Context
cTMS is part of software logistics on BTP. SAP Continuous Integration and Delivery, SAP Business Application Studio and SAP Cloud Transport Management are part of SAP Build. Upstream, cTMS connects to the change management tools: SAP Cloud ALM and SAP Solution Manager.
In depth
How it works and its building blocks
cTMS does not work on its own. It is an additional service that has to be integrated into the existing development processes of the cloud services or applications whose content it transports. The source tool exports content to cTMS, and cTMS then distributes it along the landscape. Transports can be triggered directly from tools that have been enabled for this, for example the web UI of SAP Cloud Integration.
The landscape consists of transport nodes, each representing a target subaccount or target system, and transport routes between these nodes. A node is connected to its target through a destination, in Cloud Foundry for example to the deploy service of the relevant space. For exports you need a service instance, which is created in a space of the subscribing subaccount.
The range of supported environments has grown. cTMS manages transports between accounts in different environments such as Cloud Foundry, ABAP and Neo. Since release 2302, lifecycle management for the BTP ABAP Environment can be integrated with cTMS, and since version 2023.16 SAP Analytics Cloud can transport Content Network packages via cTMS.
How it differs from similar terms
- CTS/STMS: transports ABAP transport requests between ABAP systems. cTMS transports cloud content between subaccounts and environments.
- SAP Continuous Integration and Delivery: builds and tests content. cTMS then takes care of controlled distribution.
- Cloud ALM / ChaRM: control the process and approvals but do not transport anything themselves. They hand deployments over to CTS or cTMS.
In practice: prerequisites, set-up, pitfalls
SAP recommends a separate administration subaccount for the subscription and the service instance. Licensing is via Pay-As-You-Go for SAP BTP or the SAP BTP Enterprise Agreement; according to an SAP presentation, cTMS is also available in the free tier model.
Most of the effort goes into the connectivity. For Cloud Integration, for example, you create instances and service keys for the Content Agent service, the Process Integration Runtime and cTMS, and set up a total of five destinations in the development subaccount. The destination to cTMS usually authenticates via OAuth 2.0 with the client ID and client secret from the service key.
My own assessment, not sourced: typical pitfalls are missing role collections for transport operators, expired or wrongly assigned service keys, and destinations that point to the wrong space.
Comparison with Solution Manager
cTMS can be integrated with ChaRM and Quality Gate Management in Solution Manager. On-premise ABAP transports and cloud transports are then delivered in sync. In Cloud ALM, the feature bundles the transports instead of the change document. A transport created directly in SAP Cloud Integration can be assigned to a feature via the cTMS integration. Cloud ALM connects CTS for S/4HANA Cloud Private Edition and on-premise AS ABAP systems, and cTMS for, among others, BTP Cloud Foundry, Neo, Cloud Integration and API Management. External transports without a direct integration, such as configuration bundles in SAP SuccessFactors, are documented manually via transport references.
Current status
The integration of Cloud ALM and cTMS has been generally available since May 2022. SAP recommends one or more cTMS instances of your own in your own global account rather than the instance in the Cloud ALM global account, partly because several instances can then be connected. On 21 April 2026, SAP offered the online session “Govern your cloud deliveries with SAP Cloud ALM and SAP Cloud Transport Management”. No specific cTMS innovations from 2026 were found during research.
Consultant's view
Customer question: “We run ChaRM in Solution Manager and have our first Integration Suite scenarios. Should we connect cTMS to Solution Manager now or wait for Cloud ALM?”
Answer: cTMS is the same transport layer in both cases. What you build now – nodes, routes and destinations – carries over when you move to Cloud ALM. Only the control layer is reconnected: the ChaRM change becomes the feature in Cloud ALM. I would therefore introduce cTMS straight away in its own subaccount and connect it to ChaRM. When you migrate, you connect the same instance to Cloud ALM.
Quiz
1. What does the SAP Cloud Transport Management service transport?
cTMS is a BTP service for development content across subaccounts. Classic ABAP transports run via CTS/STMS.
2. How is SAP Cloud Transport Management licensed?
According to the SAP product page, via Pay-As-You-Go or the BTP Enterprise Agreement; an SAP presentation also mentions the free tier model.
3. How do you handle SuccessFactors configuration bundles in Cloud ALM that have no direct deployment integration?
External transports without a direct integration can be documented manually in Cloud ALM via transport references.
Follow-up: Can cTMS run in the Cloud ALM subaccount?
In short: technically this used to be the case, but today SAP recommends a cTMS instance of your own in your own BTP global account, ideally in a central administration subaccount.
Previously: when SAP Cloud ALM was introduced, the Cloud ALM account included cTMS by default. For newly provisioned Cloud ALM tenants, cTMS was already subscribed in the BTP subaccount. This subaccount sits in the global account that was created when Cloud ALM was requested.
Today: the new recommended integration has replaced the variant with cTMS in the Cloud ALM subaccount. SAP Knowledge Base Article 3775175 describes how to move an existing subscription to a global account of your own, because the old set-up may stop working after a back-end change. There is a dedicated SAP blog on migrating existing landscapes.
Why an instance of your own: several cTMS instances can be connected to one Cloud ALM instance, and Cloud ALM can then also transport content from SAP Analytics Cloud, which is not possible with instances in the Cloud ALM account. SAP recommends a separate administration subaccount for access control and separation of duties; source and target subaccounts may sit in different global accounts.
Not confirmed: a user blog from 2024 describes transport services via the Cloud ALM API with a bandwidth allowance included in the Cloud ALM usage rights. Whether this still applies after the switch is unclear; clarify licensing with SAP before quoting customers.
Sources
- REALTECH: SAP Cloud Transport Management (cTMS)
- SAP Help Portal: SAP Cloud Transport Management
- SAP Developers: Get Started with SAP Cloud Transport Management Service
- SAP: Cloud Transport Management product page
- SAP Architecture Center: DevOps with SAP BTP
- SAP Community: cTMS for the BTP ABAP Environment
- SAP Community: SAC Content Network via cTMS
- SAP Community: Setting up cTMS for Cloud Integration
- SAP Community: Transporting MTAs with Cloud ALM and cTMS
- SAP Community: New Integration of SAP Cloud Transport Management and SAP Cloud ALM
- SAP KBA 3775175: Moving the cTMS subscription from the Cloud ALM account to your own global account
- SAP Learning: Integrating DevOps Services into SAP's Strategic Operations Platforms
- SAP Learning: Configuring Implementation (Cloud ALM)
- SAP Learning: Managing the Hybrid Deployment
- SAP Community: Getting ready for Change & Deployment Management in Cloud ALM
- SAP Support: Software Logistics for SAP BTP
- SAP presentation: Integrate SAP Cloud Transport Management
- SAP event: Govern your cloud deliveries (21 April 2026)
- SAP Community (user blog): Integration of CTMS as part of SAP Cloud ALM and ChaRM