If you run SAP BW, TechEd made one thing clearer: your warehouse is now expected to feed data products, not just reports.
SAP's direction is to extend BW data warehouse capabilities into SAP Business Data Cloud (BDC), rather than replace them overnight. The route already exists. With SAP BW, private cloud edition inside BDC, and the Data Product Generator for SAP BW, customers can generate data products from existing InfoProviders. They can share these with analytics and AI platforms while continuing to run existing BW use cases. That means years of modelling, business logic and historical data can support new use cases without rebuilding everything first.
Timing matters too. Mainstream maintenance for BW 7.5 ends in 2027, with options to extend support beyond that date. Many customers are already deciding what comes next. TechEd gave them more to consider.
For BW customers, the most relevant announcements were about business context.
SAP announced that its Knowledge Graph can incorporate additional SAP and non-SAP data, including information specific to individual customers. It also introduced Business Data Cloud Ontology Manager, currently in beta, to help teams create ontologies and domain-specific views across SAP and third-party data.
This points towards a future where the definitions and relationships that give BW data its meaning could be reused in AI applications, rather than being lost when data is extracted. How much of that context carries through automatically from existing BW models remains something customers need to validate.
The SAP Business AI Platform brings these capabilities into AI development. Teams can use Joule Studio to build and extend agents, while BDC and Knowledge Graph provide the data and business context those agents need.
Alongside this, BDC Connect supports zero-copy sharing with partner platforms. SAP's acquisition of Dremio adds federation capabilities, allowing distributed data to be queried without moving or copying it. SAP Reltio adds master data management capabilities, bringing together customer, supplier and product records from SAP and non-SAP systems into governed data products.
Together, these announcements strengthen SAP's direction towards connecting data, business semantics and AI across a broader enterprise data landscape.
For BW customers, modernisation no longer has to be framed solely as a warehouse migration.
It can also mean making existing BW data and business logic available to new analytics and AI use cases, while deciding which warehouse capabilities should move over time.
BDC provides a potential route to do that in stages. Customers can retain established BW processes, expose selected data as reusable products and gradually extend their data warehouse capabilities into a broader platform.
The opportunity is to build on existing investments rather than start again. But that doesn't mean every BW workload needs to move immediately, or that BDC is automatically the right destination for every requirement.
The right approach depends on the current BW landscape, the business value of existing models and the capabilities customers need in the future.
For a broader look at the modernisation paths available today, take a look at James' other post on BW modernisation, where he explores the options for customers currently running SAP BW.
It would be wrong to present all of this as finished.
Ontology Manager is in beta, and the newer capabilities from Dremio and Reltio are still being integrated into SAP's broader BDC offering. Customers also face a fair question about which component does what.
Datasphere, SAP Databricks, Dremio and HANA Cloud Knowledge Graph have different roles, but their responsibilities and integration points are not always obvious. SAP still needs to make the practical reference architecture clearer.
There is also a difference between exposing BW data as a product and preserving all the business meaning behind it. Customers need to establish which definitions, relationships and governance rules carry through, and where additional modelling or configuration is required.
That isn't a reason to wait. It's a reason to test the direction against real data before committing to a large modernisation programme.
Pick one important BW data set and follow it into an analytics or AI scenario. Then ask three questions:
The answers will help show where BDC fits your data strategy, where extending or moving warehouse capabilities could create value, and where it's still too early to commit.
The message from TechEd isn't that BW customers need to move everything into BDC now. It's that existing BW investments can play a role in a broader data and AI architecture, and customers have an opportunity to start testing that path today.
If you'd like help assessing what this means for your BW landscape and identifying a practical route forward, get in touch.
Understanding your existing BW landscape is the first step towards making an informed modernisation decision.
Invenio's free half-day BW Modernisation Assessment helps you evaluate your current environment, explore your options and identify a practical way forward.