btp-cloud-transport-management
Skill1 starsChanged 4 months agoMITView on GitHub
SAP Cloud Transport Management (CTM) — transport landscape nodes, content export/import between BTP subaccounts, import queue management, gCTS for ABAP Cloud, Content Agent automation. Use when configuring cloud transports or troubleshooting CTM import failures.
In this repository413 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .cursor/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- sap-router-skillCopilot instructions
- .cursor/rules/sap-router.mdcCursor rule
- abap-cloud-migrationSkill
- abap-cloudSkill
- abap-code-patternsSkill
- abap-code-reviewSkill
- abap-docs-referenceSkill
- abapgitSkill
- abapSkill
- abap-snippetSkill
- abap-sql-amdpSkill
- abap-system-infoSkill
- abap-unit-testingSkill
- arc-1-skillsSkill
- atc-cloudificationSkill
- authorization-iamSkill
- automation-pilot-catalog-explorerSkill
- automation-pilot-command-generationSkill
- automation-pilot-command-reviewSkill
- automation-pilot-content-management-via-apiSkill
- automation-pilot-debuggerSkill
- automation-pilot-executions-apiSkill
- automation-pilot-executor-executescriptSkill
- automation-pilot-executor-httprequestSkill
- automation-pilot-mcp-server-generationSkill
- automation-pilot-scheduled-executions-apiSkill
- badi-enhancementSkill
- btp-abap-environmentSkill
- btp-best-practicesSkill
- btp-build-work-zoneSkill
- btp-business-application-studioSkill
- btp-ciasSkill
- btp-cloud-foundrySkill
- btp-cloud-identitySkill
- btp-cloud-loggingSkill
- btp-cloud-platformSkill
- btp-connectivitySkill
- btp-developer-guideSkill
- btp-diagram-generatorSkill
- btp-integration-suiteSkill
- btp-job-schedulingSkill
- btp-master-data-integrationSkill
- btp-service-managerSkill
- cap-add-remote-serviceSkill
- cap-developerSkill
- cap-triviaSkill
- capture-answerSkill
- cap-upgradeSkill
- cds-view-entitiesSkill
- claude-abap-skillsSkill
- claude-memSkill
- clean-abapSkill
- context-modeSkill
- cpi-iflow-developmentSkill
- engine-cap-developmentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Add DEV node (type: Content Source)
- Distinctive: line 49
Add TST node (type: Content Target, parent: DEV)
- Distinctive: line 50
Add PRD node (type: Content Target, parent: TST)
- Distinctive: line 90
Create schedule for DEV → TST (e.g., nightly at 02:00)
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SAP BTP Cloud Transport Management (CTM)
Prerequisites
- BTP Global Account with entitlement for Transport Management Service (plan:
standard) - At least two subaccounts configured (e.g., DEV → TST → PRD)
- For on-premise CTS+: SAP Solution Manager 7.2 FP03+ or CTS+ with WebDisp
- For gCTS: ABAP Cloud environment (Steampunk / Embedded Steampunk) with Git access
cfCLI logged in to target subaccounts
1. Enable CTM Service
# Create service instance in source subaccount (DEV)
cf create-service cts standard ctm-dev
# Create in target subaccount (TST)
cf create-service cts standard ctm-tst2. Configure Transport Landscape
DEV Subaccount ──export──▶ CTM Node (DEV)
│
import queue
│
▼
TST Subaccount ◀──import── CTM Node (TST)
│
import queue
│
▼
PRD Subaccount ◀──import── CTM Node (PRD)Via BTP Cockpit → Transport Management → Landscape:
- Add DEV node (type: Content Source)
- Add TST node (type: Content Target, parent: DEV)
- Add PRD node (type: Content Target, parent: TST)
3. Export Content from Source
# Via cockpit: Transport Management → Source Subaccount → Export
# Select content (apps, destinations, subscriptions, etc.)
# Or via Content Agent (automated):Enable Content Agent to auto-export on subscription changes:
- BTP Cockpit → Content Agent → Configuration
- Set source = DEV subaccount, target = CTM import queue
4. Import to Target Node
# Via cockpit: Transport Management → Target Node → Import Queue
# Queue auto-processes every 5 minutes by defaultManual import: Import Queue → select transport → Import
5. gCTS for ABAP Cloud
ABAP Cloud DEV ──▶ gCTS ──▶ Git Repository ──▶ gCTS ──▶ TST ──▶ PRD# Configure gCTS in ABAP Cloud (transaction SCTS_TRANSPORT)
# 1. Create Git repository for ABAP transport objects
# 2. Register repository in gCTS configuration
# 3. Export transport → commit to Git → push
# 4. On target: pull from Git → import to ABAP system6. Schedule Automated Transports
Via BTP Cockpit → Transport Management → Schedules:
- Create schedule for DEV → TST (e.g., nightly at 02:00)
- PRD import requires manual approval gate
Pitfalls
Failed import blocks entire queue
- Cause: Import queue is sequential — one failure stops all subsequent transports for that node
- Solution: Either fix the failing transport or select it → Skip. Resolved items process next cycle (5 min).
Content not appearing in target subaccount
- Cause: Content was not explicitly exported from source before transport
- Solution: Manually trigger export from DEV node, or verify Content Agent is enabled and subscribed
gCTS sync fails with Git authentication error
- Cause: Git credentials expired or repository URL changed
- Solution: Update credentials in SCTS_TRANSPORT → Repository Settings, verify SSH key or PAT has write access
Import takes longer than expected
- Cause: Queue processes every 5 minutes; large transports are sequential, not parallel
- Solution: Wait for next cycle or trigger manual import. For urgency, use Import Now button
Cloud Connector destinations not transported
- Cause: Cloud Connector configs are environment-specific, not included in CTM transport
- Solution: Manually configure Cloud Connector on target subaccount. Only destination definitions inside BTP are transported.
Verification
# Check CTM service is bound
cf services | grep cts
# Get CTM instance GUID
CTM_GUID=$(cf service ctm-dev --guid)
# Verify landscape configuration via API
cf curl "/v3/service_instances/$CTM_GUID/parameters"Confirm in BTP Cockpit:
- Landscape shows DEV → TST → PRD chain
- Import queue has no items in "Failed" state
- Last transport timestamp matches expected schedule
- Content Agent shows green status for source subaccount
- gCTS:
git logon ABAP repo shows recent transport commits
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

