Concept card

Transport Landscape

As of 2026-09-27

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Transport Landscape?

ABAP transports and Datasphere's Content Network/CLI are two parallel pipelines, not one landscape — when a change spans both, the ABAP transport must land before the Datasphere object promotes.

What it is

Transport Landscape is how changes move from Dev → Test → Prod through SAP's transport infrastructure — the classical ABAP transport organizer (transport requests, CTS/CTS+) on the ERP side, and the Content Network plus CLI-based CI/CD on the Datasphere side. A senior consultant treats the two as parallel but distinct pipelines that must be sequenced together, not as one landscape.

The ABAP side. Every configuration or custom-code change is captured in a transport request, released through a defined landscape (DEV → QAS → PRD, sometimes with an extra consolidation system), and sequenced to avoid object collisions. CTS+ (Change and Transport System, enhanced) extends this to non-ABAP objects — BW objects, Java, and some Datasphere-adjacent artifacts — so a single transport request can carry cross-stack changes.

The Datasphere side. Objects (spaces, models, views, task chains) move between tenants via the Content Network — export/import packages with dependency resolution — or via the Datasphere CLI, which enables git-based CI/CD: object definitions committed to a repository, promoted through a pipeline (dev tenant → test tenant → prod tenant) with automated validation gates instead of manual export/import.

Senior craft signal — sequencing dependency. When a change spans both worlds (e.g. a new CDS view feeding a new Datasphere model), the ABAP transport must land in the target ERP system BEFORE the corresponding Datasphere object is promoted, or the Datasphere object activates against a source that doesn't exist yet. Wave planning (companion C036) and transport sequencing must be designed together, not independently by two different teams.

Why it matters

A new CDS view feeding a new Datasphere model is the textbook sequencing trap — get the order wrong and the Datasphere object fails to activate.
Manual export/import between Datasphere tenants without CLI-based CI/CD works for a pilot but produces silent drift at Tier-1 scale: prod diverges from what dev/test say it should contain.
Wave planning and transport sequencing must be designed together by the same team — splitting them across two teams is how the sequencing dependency gets missed.

Key points

Transport Landscape = two parallel pipelines: ABAP CTS/CTS+ on the ERP side, Content Network + CLI-based CI/CD on the Datasphere side.
CTS+ extends the classic ABAP transport organizer to non-ABAP and cross-stack objects.
Cross-stack changes must sequence: the source-side transport lands before the dependent Datasphere object is promoted.
Manual export/import without CI/CD produces prod-vs-repo drift at Tier-1 scale.
SAP's Prompt Registry is itself a Git-based transport landscape in miniature for AI configuration — prompt and orchestration-config templates managed as YAML files, auto-synced on commit — a third pipeline alongside CTS/CTS+ and the Datasphere Content Network/CLI.
A Joule Studio agent's orchestration config, workflow logic and multi-agent definitions are build-time artefacts that need their own dev/test/prod promotion path before the agent reads live SAP data — a fourth layer this card's classical ABAP-and-Datasphere framing did not originally need to cover.
The same sequencing dependency this card warns about for CDS views and Datasphere objects applies one layer higher: an agent's Prompt Registry template or orchestration config must not promote to production ahead of the Datasphere model or source it references.

Terms used on this page

Transport request: ABAP-side change container promoted DEV → QAS → PRD in a defined, sequenced release.
CTS+: Change and Transport System, enhanced — extends the classic ABAP transport organizer to non-ABAP and cross-stack objects.
Content Network: Datasphere's export/import mechanism for promoting spaces, models, and views between tenants with dependency resolution.
Datasphere CLI: Command-line tool enabling scripted, git-based CI/CD for Datasphere objects, replacing manual export/import.
Object collision: Conflict when two transport requests modify the same object concurrently; resolved by sequencing or ownership rules.
CI/CD pipeline: Automated promotion path (dev → test → prod) with validation gates, replacing manual promotion.
Landscape sequencing: Coordinating ABAP transport landing with Datasphere object promotion so dependent objects activate in the right order.
Drift: Divergence between a tenant's actual state and what the source-of-truth repository/transport history says it should contain.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

SAP Datasphere best practices 2026 that survive an audit