SAP Cloud Transport Management Skill
Related Skills
- sap-btp-cloud-platform: Use for BTP subaccount, role collection, and Cloud Foundry runtime setup
- sap-btp-developer-guide: Use for application delivery and CI/CD patterns around transported content
- sap-btp-service-manager: Use for service instances, service keys, and API/service lifecycle operations
- sap-abap: Use when transport flows include ABAP Environment or gCTS-managed content
When to Use This Skill
Use this skill when setting up transport landscapes, creating transport nodes/routes, managing import queues, deploying MTAs across environments, configuring destinations for deployment transport, integrating transports into CI/CD, or troubleshooting TMS import/deployment errors.
Table of Contents
- Overview
- Quick Start: Initial Setup
- Landscape Configuration
- Destination Configuration
- Import Queue Operations
- Transport Request Statuses
- Troubleshooting
- Security
- Bundled Resources
- Integrations
Overview
SAP Cloud Transport Management is a service on SAP BTP that manages software deliverables between accounts of different environments by transporting them across various runtimes. It provides transparency to the audit trail of changes and enables separation of concerns between developers and operations teams.
Supported Environments: Cloud Foundry, Kyma, Neo (deprecated)
Supported Content Types:
- MTA (Multitarget Applications):
.mtarfiles for Cloud Foundry deployments - BTP ABAP: References to ABAP objects in Git repositories
- Application Content: Application-specific formats (
.zip,.rar) - XSC DU: SAP HANA XS classic delivery units
Quick Start: Initial Setup
Prerequisites
- Global account administrator access
- At least one SAP BTP subaccount
- Cloud Foundry environment enabled
Setup Workflow
Step 1: Configure Entitlements
Navigate to: Global Account > Entitlements > Entity Assignments > Add Service Plans
Select "Cloud Transport Management" and choose plans:
Instance plans require an active application plan. The
exportplan is for CI/CD pipelines.
Step 2: Subscribe to the Service
- Navigate to Services > Service Marketplace
- Search for "Cloud Transport Management"
- Select Create from the Actions menu
- Choose a subscription plan (
standard,free, orbuild-runtime) - Verify status shows "Subscribed"
Step 3: Set Up Role Collections
Pre-delivered Role Collections:
TMS_LandscapeOperator_RCTMS_Viewer_RC
Available Roles:
Assign roles: Security > Role Collections > [Collection] > Edit > Users
Step 4: Create Service Instance and Key
- Create a Cloud Foundry space in your subaccount
- Navigate to Services > Instances and Subscriptions > Create
- Select:
- Service:
Cloud Transport Management - Plan:
standard(instance type) - Runtime:
Cloud Foundry
- Service:
- Create a service key - credentials structure:
Landscape Configuration
Transport Nodes
Transport nodes represent source or target endpoints of deployment processes.
Node Types:
- Physical Nodes: Actual deployment endpoints (e.g., Cloud Foundry spaces)
- Virtual Nodes: Placeholders for aggregation/distribution without physical deployment
Key Configuration Fields:
Transport Routes
Routes connect transport nodes. Constraint: A node can be a target for only one route but can be a source for multiple routes.
Transport Landscape Wizard
Use for simple 2-3 node landscapes:
- Select template (number of nodes)
- Configure each node
- Customize route names
- Review and finish
Destination Configuration
All destinations require HTTPS. Configure in: SAP BTP Cockpit > Connectivity > Destinations
Destination to TMS Service (Source Environment)
Required for applications exporting content directly to TMS.
MTA Deployment Destinations (Cloud Foundry)
Option 1: Basic Authentication (SAP ID users only)
Get space GUID:
cf space <space-name> --guidURL-encode special characters in org/space names
Option 2: OAuth2Password (Custom IdP support)
BTP ABAP Environment Destinations
Import Queue Operations
Import Methods
Importable Statuses: Initial, Fatal, Repeatable
File Upload
- Max file size: 1 GB (500 MB on free plan)
- Storage quota: 50 GB standard, 500 MB free
- Retention: 30 days (7 days free) after final status
- Formats:
.mtar(MTA),.tgz(XSC DU),.zip(Application Content)
Scheduling
- Patterns: Daily (hourly, 4x/day) or Weekly (specific days/times)
- Auto-deactivation: After 3 consecutive fatal failures over 3+ weeks
Automatic Import
Enable per node - immediately processes all importable requests and triggers on new arrivals.
Transport Request Statuses
Import Statuses
Lifecycle Statuses
- Modifiable: Request can be edited
- Released: In at least one queue with non-archived status
- Deleted: Deleted from all queues
- Archived: Cleaned up by retention policy
Troubleshooting
Quick Reference: Common Errors
MTA Deployment Errors
Error: Not Found during deployment
Causes:
- Wrong Cloud Foundry domain in URL
- Special characters in org/space names not URL-encoded
Solutions:
- Verify domain matches CF API endpoint:
cf api - Use space GUID instead of names
- URL-encode special characters (
+→%2B, space →%20)
Error: Forbidden during deployment
Causes:
- User lacks
SpaceDeveloperrole - User from wrong identity provider
Solutions:
- Verify user roles:
cf space-users <org> <space> - Use OAuth2Password auth for custom IdP users
SAP Support
Component: BC-CP-LCM-TMS (Transport Management for application content)
Required for incidents: Region, subaccount ID, reproduction steps, transport action logs, screenshots
For detailed troubleshooting steps, error catalogs by content type, and support procedures, see references/troubleshooting.md.
Security
Service Plans for API Access
Node-Specific Restrictions
Use attributes to restrict roles to specific nodes:
TmsNodesTransportOperatorTmsNodesImportTmsNodesExport
Malware Scanning
TMS does not perform malware scans - target applications are responsible. Exception: MTA deployment descriptors are verified.
Integrations
CI/CD Integration
Use SAP Continuous Integration and Delivery or Project Piper with the export service plan.
Alert Notifications
Configure ALERT_NOTIFICATION_SERVICE destination for:
TmsImportFinished/TmsImportStartedTmsTransportRequestAddedTmsNodeImportJobDeactivatedTmsStorageQuotaUsage(85% threshold)
API Operations
- File Upload: Upload content archive
- Node Export: Attach file to new request, forward to target nodes
- Node Upload: Upload to specific node (CI/CD scenarios)
- Import operations: Async - monitor with Get transport action
Reference Documentation
For detailed configuration procedures, see the reference files:
Bundled Resources
Reference Documentation
references/initial-setup.md- Complete setup proceduresreferences/landscape-configuration.md- Nodes, routes, visualization, and wizardreferences/destinations.md- All 8 destination types with configurationsreferences/import-operations.md- Import queue, MTA descriptors, modifiable requestsreferences/administration.md- Service plans, backup, storage, data exportreferences/troubleshooting.md- Error resolution guidereferences/integrations.md- Integration scenarios and API operationsreferences/security-roles.md- Role and permission details
Documentation Links
- GitHub Docs: https://github.com/SAP-docs/sap-btp-cloud-transport-management
- SAP Help Portal: https://help.sap.com/docs/cloud-transport-management
- API Reference: https://api.sap.com/package/TmsForCloudPub/rest
Last Updated: 2025-11-22 Source: SAP-docs/sap-btp-cloud-transport-management


