Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Why SAP rebuilt its data stack: from BW to Business Data Cloud

11 min

Listen to this lesson

0:00 / 7:24

Contoso Motor Co. is live on SAP S/4HANA Cloud Private Edition after its conversion from SAP ECC 6.0. The CFO now asks a question that sounds simple: "Why do we have three places that show revenue, and which one is right?" Margin by customer appears in a Fiori analytical app in CMP, in an SAP BW 7.5 query that finance has used for ten years, and in a spreadsheet that Dan, the finance process owner, rebuilds every month. Noor, Contoso's data and analytics lead, has been asked to explain where SAP's data and analytics products are going and what Contoso should do about it. This course follows her.

To answer, you need the history. For two decades SAP's answer to "analytics on ERP data" was SAP Business Warehouse (BW): extract data from the ERP with DataSources, stage it, transform it, store it again in InfoProviders and report on it with BEx or Analysis for Office queries. BW was reliable and well governed, but every new question meant a new flow, and the data was a copy of a copy, often a day old.

The classic BW path for billing data: every arrow is a load the customer built, scheduled and monitored, and every box is another copy.
The Sign-Off Table · thesignofftable.com/academy/sap-dap-101

Every one of those boxes had to be designed, transported and tested by the customer, and every new business question usually meant another arrow. When SAP S/4HANA arrived with its own real-time analytics on CDS views, many companies ended up with two parallel worlds: operational reports inside the ERP and strategic reports in BW, each with its own definitions. The CFO’s three revenue numbers are a symptom of exactly that history.

Four generations in one diagram

Each generation tried to shorten the distance between business data and the people and systems that use it.
The Sign-Off Table · thesignofftable.com/academy/sap-dap-101

SAP then built SAP BW/4HANA (2016), a HANA-only and simplified BW, and in 2019 a cloud data warehouse, SAP Data Warehouse Cloud, renamed SAP Datasphere in 2023. Customers still had to move and model ERP data themselves. In February 2025 SAP announced SAP Business Data Cloud (BDC): one fully managed SaaS offering that brings SAP Datasphere, SAP Analytics Cloud, SAP BW (including its private cloud edition) and SAP Databricks together, and adds SAP-managed data products that SAP itself extracts and maintains from SAP applications. At SAP Sapphire in May 2026, SAP called BDC the data foundation of the new SAP Business AI Platform and named SAP HANA Cloud and SAP Master Data Governance as core BDC components.

What changed in the idea, not just the product names

QuestionBW era answerBDC answer
Who builds the extraction from SAP applications?The customer, flow by flowSAP, for SAP-managed data products; the customer for its own data
What is the unit of reuse?An InfoProvider inside one BW systemA data product: a described, governed dataset others can discover and consume
Where does non-SAP analytics happen?Data is exported, usually as filesZero-copy sharing through BDC Connect, where supported
Who consumes the data?Reports and planningReports, planning, machine learning and AI agents
Who runs the platform?Customer IT and BasisSAP, as a managed cloud service

The shift is from building pipelines to consuming and publishing data products.

ConsumptionSAP Analytics Cloud stories and planning, intelligent applications, Joule agents, partner platforms
Semantic and model layerSAP Datasphere spaces, views and analytic models; SAP Knowledge Graph
Data productsSAP-managed data products and customer data products, listed in the catalog
StorageSAP HANA Cloud and the object store (SAP HANA Cloud, data lake files)
SourcesSAP S/4HANA, other SAP applications, SAP BW private cloud edition, non-SAP systems
A simplified layer view of BDC. Real deployments add security, catalog and administration services.
The Sign-Off Table · thesignofftable.com/academy/sap-dap-101

Why it matters to people who sign things off

For a tester or process owner, the important change is that numbers will increasingly be produced outside the transaction system. A margin figure in an SAP Analytics Cloud story may come from a data product that SAP refreshed, a model a data team built, and an AI agent that summarized it. If nobody can prove where the number came from, nobody should sign it off. That is the thread through this course and the reason for the testing course that follows it (sap-dap-301).

What would you do?

In her first steering meeting, Grace, the PMO lead, asks Noor: "Is BDC just Datasphere with a new name, so we can ignore it?" What is the best answer?

  1. AskThe CFO asks which revenue number is right
  2. TraceNoor lists every place margin is calculated: Fiori app, BW query, spreadsheet
  3. CompareShe reconciles the three for one month and explains each difference
  4. DecideSteering agrees which layer owns which kind of question
The practical first step for any company is to trace and reconcile the numbers it already has.
The Sign-Off Table · thesignofftable.com/academy/sap-dap-101
Key points
  • SAP moved from BW (build every pipeline) to BDC (consume and publish governed data products).
  • BDC, announced in February 2025, bundles SAP Datasphere, SAP Analytics Cloud, SAP BW private cloud edition and SAP Databricks as a managed SaaS.
  • At Sapphire 2026 SAP called BDC the data foundation of the SAP Business AI Platform.
  • Statuses change fast: date every claim and re-check after SAP events.

Check your understanding · not graded

Lesson check

  1. 1. Which statement best describes SAP Business Data Cloud?

  2. 2. What was SAP Datasphere called before 2023?

  3. 3. Which is the biggest change in operating idea from BW to BDC?

  4. 4. Why should a process owner ask for the lineage of one key figure before signing off a new analytics source?