SAP Cloud Transport Management for BTP and Hybrid Landscapes

Keep this: job aid

CTMS release checklist

• Service in a central subaccount (not the Cloud ALM one), on the standard application plan.
• Developers: export rights only. Release team: landscape and import rights. Pipelines: export instance plan.
• Source node allows uploads; target nodes have a content type and a destination to the right space.
• Test node forward mode Manual or On Success; no automatic imports into production behind Pre-Import.
• Keep released archives in your repository; the service keeps files only for the retention period.
• Error: fix in development and re-export. Fatal: fix destination or authentication, then reimport.
• Stage-specific values via MTA extension descriptors; credentials maintained per target.
• Hybrid releases: ABAP first, then integration, then apps, then switches; one record of every request.
• Evidence names transport request IDs and content versions that will move to production.