Analytics Legends logoAI & Analytics Legends Sign inSign up
Guide

SAP Datasphere architecture — the reference diagram and the four calls that set the cost

As of 2026-10-10

Datasphere is the unified data and semantic layer of SAP's modern analytics estate: federation, replication and modelling in one product, running on HANA Cloud with an integrated Delta Lake. The diagram below draws it — sources, spaces and layers, consumers. The architecture work is the four decisions underneath that drawing, and each one is expensive to reverse once objects exist.

SAP Datasphere architecture diagram: SAP S/4HANA, BW and non-SAP sources feed spaces with inbound, harmonisation and consumption layers, consumed by SAP Analytics Cloud, Business Data Cloud, Databricks and third-party tools
SAP Datasphere reference architecture, redrawn by Analytics Legends (October 2026). Sources: SAP Help Portal — SAP Datasphere · SAP Architecture Center — Transforming Enterprise Data Strategy with SAP Business Data Cloud · SAP Help Portal — Consuming Data in SAP Analytics Cloud

Reading the SAP Datasphere architecture diagram

Read it left to right. Sources sit on the left: SAP S/4HANA, an existing BW or BW/4HANA estate, non-SAP databases and applications, files in hyperscaler storage. Each one reaches the tenant either federated, as a remote table that queries the source live, or loaded, through a replication flow that copies it into a local table.

Inside the tenant, everything lives in a space. The three layers drawn across it — inbound, harmonisation, consumption — are a delivery convention rather than product objects, and that matters: SAP enforces the space boundary, while only the team enforces the layers. Inbound keeps data source-shaped; harmonisation conforms it in views, data flows and transformation flows; consumption publishes analytic models and data products, the semantic contract every report and agent reads.

Two bands run under all of it. The catalog, with data access controls and lineage, is how one space consumes another's work without copying it. Task chains, monitoring and transport are how the whole thing runs every night and moves between tenants.

On the right sit the consumers: SAP Analytics Cloud for stories and planning, Business Data Cloud for data products, Databricks through zero-copy Delta Sharing, and third-party tools over SQL or OData. The four decisions below are where those boxes stop being a drawing and start being a cost.

Decision one: which layer owns the semantics

Datasphere models and governs; SAP Analytics Cloud consumes. They are layers, not alternatives, and the real question is how much semantic modelling belongs in each.

The criterion is reuse, not preference. The moment a second story, a planning model, an AI agent or an external tool needs the same measure, the definition has to live where all of them can read it. A key figure defined inside one SAC story is invisible to everything else, and the second consumer re-implements it slightly differently — which is how two dashboards start disagreeing about revenue.

Decision two: federate or load, per object

Federation is first-class here, and that inverts the classical warehouse habit. Historically everything was loaded before it could be modelled; in Datasphere a live query passes through with nothing copied, so loading is a choice you justify rather than a default you inherit.

The justification is one of three things — latency, source-system load, or source availability. Write it down per object, or the team replicates by reflex and pays storage and pipeline maintenance for data nobody queries twice a month.

The reverse mistake is as common. Federating a high-volume fact table under constant query pays the source's live-query cost on every render. Our break-even sits around 100 gigabytes of facts, or fifty concurrent business-intelligence users.

Decision three: how spaces are cut

Every object lives inside a space: a governed partition with its own security, connections and lifecycle, where cross-space consumption goes through the catalog as a versioned data product rather than as ad-hoc table sharing.

Cut on ownership and release cadence — one data owner, one lifecycle. Cutting by project produces a graveyard of ownerless spaces; cutting by source system reproduces the staging layer inside the governance model and makes every useful business object cross a boundary.

Decision four: whether a lakehouse belongs in the picture

Three architectures, and the choice is not about capability. Datasphere alone, consumed by SAP Analytics Cloud — correct whenever nobody on the project would use Spark if you gave it to them, and not the lesser option. Datasphere plus a standalone Databricks, federated — correct when a mature Databricks practice already exists, because migrating it into SAP-native tooling costs more than federating it. Business Data Cloud — the pre-wired bundle, where you buy the integration instead of building it.

The bundle assumes an SAP-majority estate, roughly seventy to eighty percent of analytics-relevant data inside the SAP footprint. Invert that ratio and you are paying SAP packaging to keep a minority of your analytics native.

The first question on all three is not technical: does anyone here operate a lakehouse day to day? Business Data Cloud changes who bills for Databricks, not who has to understand Spark, Delta and Unity Catalog.

The hybrid window is an architecture, not an accident

In almost every multi-year S/4HANA transition, ECC and S/4HANA run side by side for three to five years because lines of business migrate on different cadences. Datasphere's job in that window is to unify analytics across both, so one model layer abstracts which source a number came from.

What keeps it bounded is calendared exit dates per region or line of business, reviewed quarterly. Organisations that design the endgame from the start converge in two to four years; those that treat each decision tactically are still running two platforms seven to ten years later.

Frequently asked

Is SAP Datasphere a replacement for BW?

It is not the new BW, and framing it that way licenses lift-and-shift. What it replaces is a pattern — point-to-point extracts, hand-built warehouses, brittle query layers — with federation, replication and modelling in one governed product.

Do we need SAP Analytics Cloud as well as Datasphere?

For consumption, yes: Datasphere models and governs, SAC delivers stories, applications and planning. Buying only the consumption half is how semantics end up scattered across stories nobody owns.

Federate or replicate by default?

Federate, and justify each replication with latency, source load or source availability. Reverse it past roughly 100 GB of facts or fifty concurrent users, where replication is the cheaper answer.

Where does HANA Cloud fit?

Underneath. Datasphere is the semantic and governance fabric on top of HANA Cloud with an integrated Delta Lake, not a replacement for it. Conflating the two double-counts capacity at sizing time.

Who takes these decisions — a SAP Datasphere architect or a consultant?

The SAP Datasphere architect (SAP DSP architect in postings that use SAP's short form) takes the four decisions above, once, on the first live tenant. SAP Datasphere consultants build inside them, and on a multi-team programme a team lead holds them in place when delivery pressure argues for a shortcut.

Is there an official SAP Datasphere architecture diagram?

SAP documents the components on the SAP Help Portal and publishes Business Data Cloud reference architectures on the SAP Architecture Center. The diagram on this page is our own redrawing of those components, organised around the decisions a delivery team actually has to take rather than around the product menu.

What belongs in a SAP Datasphere architecture review?

The four decisions that are expensive to reverse: which layer owns the semantics, federate or load per object, how spaces are cut (on ownership and release cadence), and whether a lakehouse belongs in the picture. Add the hybrid window if ECC and S/4HANA run side by side: calendared exit dates per region or business line, reviewed quarterly. The first question is not technical, it is whether anyone on the project operates a lakehouse day to day.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Alert me to new SAP Datasphere missions

No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy

Open missions

120 live roles and contracts in SAP Datasphere right now — see the SAP Datasphere missions · freelance SAP contracts.