secondsky/sap-skillsGPL-3.011 files

Sap Btp Cloud Transport Management

|

Specification
Skill ID
secondsky/sap-skills/sap-btp-cloud-transport-management
Publisher
secondsky
Repository
sap-skills
Installs
0
Files
11
License
GPL-3.0
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

secondsky/sap-skills/sap-btp-cloud-transport-managementInstalls these files
  • README.md
  • SKILL.md
  • agents/openai.yaml
  • references/administration.md
  • references/destinations.md
  • references/import-operations.md
  • references/initial-setup.md
  • references/integrations.md
  • references/landscape-configuration.md
  • references/security-roles.md
  • references/troubleshooting.md

What this skill tells the agent

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

  1. Overview
  2. Quick Start: Initial Setup
  • Prerequisites
  • Setup Workflow
  • Step 1: Configure Entitlements
  • Step 2: Subscribe to the Service
  • Step 3: Set Up Role Collections
  • Step 4: Create Service Instance and Key
  1. Landscape Configuration
  • Transport Nodes
  • Transport Routes
  • Transport Landscape Wizard
  1. Destination Configuration
  • Destination to TMS Service (Source Environment)
  • MTA Deployment Destinations (Cloud Foundry)
  • BTP ABAP Environment Destinations
  1. Import Queue Operations
  • Import Methods
  • File Upload
  • Scheduling
  • Automatic Import
  1. Transport Request Statuses
  • Import Statuses
  • Lifecycle Statuses
  1. Troubleshooting
  • Quick Reference: Common Errors
  • MTA Deployment Errors
  • SAP Support
  1. Security
  • Service Plans for API Access
  1. Bundled Resources
  • Node-Specific Restrictions
  • Malware Scanning
  1. Integrations
  • CI/CD Integration
  • Alert Notifications
  • API Operations
  1. Reference Documentation
  2. Documentation Links

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): .mtar files 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

1. Configure Entitlements → 2. Subscribe to Service → 3. Set Up Roles → 4. Create Service Instance

Step 1: Configure Entitlements

Navigate to: Global Account > Entitlements > Entity Assignments > Add Service Plans

Select "Cloud Transport Management" and choose plans:

Plan TypePlans AvailablePurpose
Applicationstandard, free, build-runtimeUI access
Instancestandard, export, transport_operatorAPI/programmatic access
Instance plans require an active application plan. The export plan is for CI/CD pipelines.

Step 2: Subscribe to the Service

  1. Navigate to Services > Service Marketplace
  2. Search for "Cloud Transport Management"
  3. Select Create from the Actions menu
  4. Choose a subscription plan (standard, free, or build-runtime)
  5. Verify status shows "Subscribed"

Step 3: Set Up Role Collections

Pre-delivered Role Collections:

  • TMS_LandscapeOperator_RC
  • TMS_Viewer_RC

Available Roles:

RoleCapabilities
AdministratorFull administration for all TMS tasks
LandscapeOperatorCreate/edit/delete nodes and routes
TransportOperatorManage import queues, forward, reset, schedule
ImportOperatorImport all transport requests
ImportSelectedOperatorImport selected transport requests
ExportOperatorAdd files, create modifiable requests
ViewerRead-only access

Assign roles: Security > Role Collections > [Collection] > Edit > Users

Step 4: Create Service Instance and Key

  1. Create a Cloud Foundry space in your subaccount
  2. Navigate to Services > Instances and Subscriptions > Create
  3. Select:
  • Service: Cloud Transport Management
  • Plan: standard (instance type)
  • Runtime: Cloud Foundry
  1. Create a service key - credentials structure:
{
  "uaa": {
    "clientid": "sb-xxxxxx",
    "clientsecret": "xxxxxx",
    "url": "https://<domain>.authentication.sap.hana.ondemand.com"
  },
  "uri": "https://transport-service-app-backend.ts.cfapps.sap.hana.ondemand.com"
}

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:

FieldDescription
NameCase-sensitive identifier (must match sourceSystemId for Content Agent)
Allow Upload to NodeEnable file uploads for local archives
Forward ModePre-Import (default), Post-Import, On Success, Manual
Content TypeMTA, BTP ABAP, Application Content, XSC DU
DestinationTarget deployment endpoint
Deployment Strategydefault or blue-green (MTA on CF only)

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:

  1. Select template (number of nodes)
  2. Configure each node
  3. Customize route names
  4. 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.

FieldValue
NameTransportManagementService (or app-specific name)
TypeHTTP
URLService key uri value
AuthenticationOAuth2ClientCredentials
Client IDService key uaa.clientid
Client SecretService key uaa.clientsecret
Token Service URLService key uaa.url + /oauth/token
Additional PropertysourceSystemId = source node name

MTA Deployment Destinations (Cloud Foundry)

Option 1: Basic Authentication (SAP ID users only)

FieldValue
URL (org/space)https://deploy-service.cf.<domain>/slprot/<org>/<space>/slp
URL (space GUID)https://deploy-service.cf.<domain>/slprot/<guid>/slp
AuthenticationBasicAuthentication

Use this skill in a project

Open any RiverX project, search the Skills panel for secondsky/sap-skills/sap-btp-cloud-transport-management, and install it in one click.

Use this skill