Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sap-btp-cloud-transport-management
Comprehensive skill for SAP Cloud Transport Management service on SAP BTP. Use when setting up transport landscapes, configuring transport nodes and routes, managing import queues, deploying MTAs across Cloud Foundry environments, integrating with CI/CD pipelines, configuring ABAP environment transports, troubleshooting deployment errors, or implementing change management workflows. Covers entitlements, subscriptions, role collections, service instances, destinations, and API integrations.
npx claudepluginhub andreafusar/https-github.com-secondsky-sap-skills --plugin sap-btp-cloud-transport-managementHow this skill is triggered — by the user, by Claude, or both
Slash command
/sap-btp-cloud-transport-management:sap-btp-cloud-transport-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. [Overview](#overview)
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
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:
.mtar files for Cloud Foundry deployments.zip, .rar)1. Configure Entitlements → 2. Subscribe to Service → 3. Set Up Roles → 4. Create Service Instance
Navigate to: Global Account > Entitlements > Entity Assignments > Add Service Plans
Select "Cloud Transport Management" and choose plans:
| Plan Type | Plans Available | Purpose |
|---|---|---|
| Application | standard, free, build-runtime | UI access |
| Instance | standard, export, transport_operator | API/programmatic access |
Instance plans require an active application plan. The
exportplan is for CI/CD pipelines.
standard, free, or build-runtime)Pre-delivered Role Collections:
TMS_LandscapeOperator_RCTMS_Viewer_RCAvailable Roles:
| Role | Capabilities |
|---|---|
| Administrator | Full administration for all TMS tasks |
| LandscapeOperator | Create/edit/delete nodes and routes |
| TransportOperator | Manage import queues, forward, reset, schedule |
| ImportOperator | Import all transport requests |
| ImportSelectedOperator | Import selected transport requests |
| ExportOperator | Add files, create modifiable requests |
| Viewer | Read-only access |
Assign roles: Security > Role Collections > [Collection] > Edit > Users
Cloud Transport Managementstandard (instance type)Cloud Foundry{
"uaa": {
"clientid": "sb-xxxxxx",
"clientsecret": "xxxxxx",
"url": "[https://<domain>.authentication.sap.hana.ondemand.com"](https://<domain>.authentication.sap.hana.ondemand.com")
},
"uri": "[https://transport-service-app-backend.ts.cfapps.sap.hana.ondemand.com"](https://transport-service-app-backend.ts.cfapps.sap.hana.ondemand.com")
}
Transport nodes represent source or target endpoints of deployment processes.
Node Types:
Key Configuration Fields:
| Field | Description |
|---|---|
| Name | Case-sensitive identifier (must match sourceSystemId for Content Agent) |
| Allow Upload to Node | Enable file uploads for local archives |
| Forward Mode | Pre-Import (default), Post-Import, On Success, Manual |
| Content Type | MTA, BTP ABAP, Application Content, XSC DU |
| Destination | Target deployment endpoint |
| Deployment Strategy | default or blue-green (MTA on CF only) |
Routes connect transport nodes. Constraint: A node can be a target for only one route but can be a source for multiple routes.
Use for simple 2-3 node landscapes:
All destinations require HTTPS. Configure in: SAP BTP Cockpit > Connectivity > Destinations
Required for applications exporting content directly to TMS.
| Field | Value |
|---|---|
| Name | TransportManagementService (or app-specific name) |
| Type | HTTP |
| URL | Service key uri value |
| Authentication | OAuth2ClientCredentials |
| Client ID | Service key uaa.clientid |
| Client Secret | Service key uaa.clientsecret |
| Token Service URL | Service key uaa.url + /oauth/token |
| Additional Property | sourceSystemId = source node name |
Option 1: Basic Authentication (SAP ID users only)
| Field | Value |
|---|---|
| URL (org/space) | [https://deploy-service.cf.<domain>/slprot/<org>/<space>/slp](https://deploy-service.cf./slprot///slp`) |
| URL (space GUID) | [https://deploy-service.cf.<domain>/slprot/<guid>/slp](https://deploy-service.cf./slprot//slp`) |
| Authentication | BasicAuthentication |
| User | Platform user email with SpaceDeveloper role |
Get space GUID:
cf space <space-name> --guidURL-encode special characters in org/space names
Option 2: OAuth2Password (Custom IdP support)
| Field | Value |
|---|---|
| URL | Same as Basic Auth |
| Authentication | OAuth2Password |
| Client ID | cf |
| Client Secret | (leave empty) |
| Token Service URL | [https://login.cf.<domain>](https://login.cf.`) |
| Field | Value |
|---|---|
| URL | [https://<instance>.abap.<region>.hana.ondemand.com/sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/manage_software_components/0001/](https://.abap..hana.ondemand.com/sap/opu/odata4/sap/a4c_mswc_api/srvd_a2x/sap/manage_software_components/0001/`) |
| Authentication | BasicAuthentication |
| User | Communication user from SAP_COM_0948 |
| Method | Description | Availability |
|---|---|---|
| Import All | Sequential import of all requests in queue | All content types |
| Import Selected | Import specific requests (may cause inconsistencies) | Not BTP ABAP |
| Import Upto | Import all requests up to selected one | BTP ABAP only |
Importable Statuses: Initial, Fatal, Repeatable
.mtar (MTA), .tgz (XSC DU), .zip (Application Content)Enable per node - immediately processes all importable requests and triggers on new arrivals.
| Status | Description |
|---|---|
| Initial | Added but not imported |
| Running | Import in progress |
| Succeeded | Import successful |
| Warning | Completed with warnings |
| Error | Import failed (retryable) |
| Fatal | Import failed (fatal error) |
| Skipped | Intentionally skipped (virtual nodes) |
| Repeatable | Reset for re-import |
| Deleted | Removed from queue |
| Transient | Tested and released (modifiable requests) |
| Error | Likely Cause | Quick Fix |
|---|---|---|
Not Found | Wrong CF domain | Match domain to cf api output |
Not Found | Unencoded special chars | Use space GUID: cf space <name> --guid |
Forbidden | Missing SpaceDeveloper | Add role in BTP Cockpit or CF CLI |
Forbidden | Wrong IdP | Use OAuth2Password with origin property |
| Connection refused (ABAP) | Wrong URL pattern | Verify SAP_COM_0948 communication arrangement URL |
| Import stuck | Non-final status | Check Transport Action Logs for root cause |
Error: Not Found during deployment
Causes:
Solutions:
cf api+ → %2B, space → %20)Error: Forbidden during deployment
Causes:
SpaceDeveloper roleSolutions:
cf space-users <org> <space>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.
| Plan | Access Level |
|---|---|
standard | Full API access |
export | Export actions only (CI/CD) |
transport_operator | Import, reset, forward, delete only |
Use attributes to restrict roles to specific nodes:
TmsNodesTransportOperatorTmsNodesImportTmsNodesExportTMS does not perform malware scans - target applications are responsible. Exception: MTA deployment descriptors are verified.
Use SAP Continuous Integration and Delivery or Project Piper with the export service plan.
Configure ALERT_NOTIFICATION_SERVICE destination for:
TmsImportFinished / TmsImportStartedTmsTransportRequestAddedTmsNodeImportJobDeactivatedTmsStorageQuotaUsage (85% threshold)For detailed configuration procedures, see the reference files:
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 detailsLast Updated: 2025-11-22 Source: SAP-docs/sap-btp-cloud-transport-management