BTP & Integrationadvanced

BTP Transport Management Part 3: Designing and Operating Transport Landscapes

Key takeaway

Operate transports at scale: landscape patterns (per product, shared integration, multiple regions), import schedules and approvals, integration with CI/CD pipelines, monitoring failed imports, rollbacks via redeploy, and audit reporting.

Explanation

📌 KEY POINTS
✅ Choose landscape patterns: per product line, shared integration landscape, regional prod nodes.
✅ Schedule imports (e.g. weekly release windows) and use approval steps for production.
✅ Connect CI/CD so every build produces a traceable transport request.
✅ Failed imports show logs; fix and re-import, or redeploy a previous version as rollback.
⚠️ Parallel manual deployments alongside cTMS make the import history unreliable.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured nodes. Now operations.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PATTERNS

Product-based, shared, regional.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SCHEDULES & APPROVALS

Release windows; approver roles.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CI/CD

Build → test → upload to cTMS.

━━━━━━━━━━━━━━━━━━━━
▶ 4. FAILURES & ROLLBACK

Import logs; redeploy prior MTA.

━━━━━━━━━━━━━━━━━━━━
▶ 5. AUDIT

Import history; compliance reports.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define release windows.
Add approval for PROD imports.
Practice a rollback.

✅ CHECKPOINT: rollback completed within the release window.

Code example

ABAP Code

===== OPERATIONS =====CI/CD pipeline: build → unit tests → upload to cTMS (TEST) → automatic import TEST → manual approval → scheduled PROD importFailed import → log → fix → new request (or re-import previous version) ===== GOVERNANCE =====Only cTMS deploys to PROD | import order enforced | monthly audit of import history

Real project scenario

An integration team running many iFlows imported requests out of order and overwrote a hotfix. Enforcing queue order and scheduled imports with approval eliminated regressions.

Common mistakes

Out-of-order imports.
Manual deployments in parallel.
No rollback plan.
No approvals.
Ignoring logs.

Best practices

Queue order.
cTMS only.
Keep previous versions.
Approvals for prod.
Review logs.

Interview angle

Questions: "How do you integrate cTMS with CI/CD?", "How do you roll back?", "Which landscape pattern?"
Strong answer: patterns, schedules/approvals, CI/CD, failures/rollback, audit.

Practice this lesson

Quick check

1. How can you roll back a faulty production deployment with cTMS?

2. Why should parallel manual deployments be avoided when using cTMS?

3. A hotfix was overwritten after requests were imported out of order. What prevents this?

Interview questions

1. A production issue is reported in Transport Management. What would you check first, and how would you troubleshoot it systematically?

Answer it in your own words first, then compare.

2. Suppose you inherit an existing Transport Management solution. How would you review it before making a change?