SAP Business Data Cloud: what it means if you run BW today

In February 2025 SAP launched SAP Business Data Cloud (BDC). At Sapphire 2026 it became one of the three pillars of the new SAP Business AI Platform, next to BTP and SAP's AI services. If your reporting runs on SAP BW, BDC changes where SAP is investing, and sooner or later it changes your roadmap.

What is in the box

BDC combines several products that existed separately:

• Data products: SAP-managed packages of business data from SAP applications, delivered with their business meaning intact and hosted in BDC's foundation services.
• SAP Datasphere: the data fabric and semantic layer, used both for SAP's packaged content and for your own models combining SAP and non-SAP data.
• SAP Analytics Cloud: dashboards, stories and planning.
• Insight apps: SAP-built analytical applications on top of the data products.
• SAP Databricks: a Databricks environment inside BDC for data science and machine learning, with zero-copy sharing to Databricks outside SAP.
• SAP BW, private cloud edition: a way to bring existing BW systems into the same environment.

The shift underneath

The traditional pattern was to extract SAP tables into a warehouse and rebuild the business logic there. Every warehouse ended up with its own definition of an open order or a margin. The data product approach is meant to reverse that: SAP publishes the data with its semantics, and you combine it with other data without copying more than necessary.

What BW customers should do

BW is not being switched off. BW/4HANA remains supported, and BDC gives BW a place inside the new architecture. But innovation is clearly going to Datasphere and BDC, and licensing is moving towards BDC at renewal. A sensible path:

1. Inventory your BW content by usage. As with custom code, much of it is rarely used.
2. Identify where SAP data products already cover a need. Those are candidates to stop maintaining yourself.
3. Federate before migrating. Datasphere can consume BW content, so new use cases can start there while BW keeps running.
4. Move models when there is a reason, such as an S/4HANA migration changing the source or a new AI use case needing the data.
5. Plan around your licence renewal, which is when the commercial conversation will happen anyway.

Why it matters for AI

SAP's agents and Joule depend on business context. Data products and the Knowledge Graph are how that context is supplied. Companies whose analytical data is well modelled and governed will get more out of SAP's AI roadmap than companies with a tangle of extracts.