Concept card

SAP BW (Business Warehouse)

As of 2026-08-05T12:00:00Z

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

What is SAP BW (Business Warehouse)?

SAP's ABAP-based enterprise data warehouse, shipped since 1998 and still the analytical backbone of a large part of the SAP installed base. Understanding what "BW" names across four product generations is the precondition for reading any migration argument about it.

What it is

SAP BW is SAP's ABAP-based enterprise data warehouse. It shipped in 1998 as Business Information Warehouse, became SAP NetWeaver BW, and has been through four product generations that the market persistently collapses into one word.

The four things called BW. BW 7.x on any database is the classic stack, running on Oracle, DB2, SQL Server or HANA. BW on HANA is the same ABAP application with HANA underneath — a database swap, not a new product. BW/4HANA is a separate product with its own code line, HANA-only, with a deliberately reduced object model. BW Bridge is a BW runtime hosted inside SAP Datasphere, intended as a landing zone for existing BW content rather than a place to build new models. A statement about "BW" that does not say which of these is meant is not yet a statement about anything actionable.

Why the object model matters. BW's value was never the storage. It was an opinionated modelling layer: InfoObjects carrying master data, texts and hierarchies; DSOs for consolidated staging; InfoCubes for star-schema query; transformations and DTPs for movement; process chains for orchestration; and a query layer that made time-dependency and currency conversion someone else's solved problem. BW/4HANA collapsed this to a smaller set — the aDSO absorbed most of what DSOs and InfoCubes did separately, and CompositeProviders absorbed MultiProviders and InfoSets. That reduction is the real migration work, and it is why a lift-and-shift is rarely what actually happens.

Why it matters

Nearly every SAP analytics migration conversation starts from a BW estate. Which BW is on the table decides the paths available, the effort, and whether a deadline applies at all.

Key points

🔴 "BW" names four different things: BW 7.x on any database, BW on HANA, BW/4HANA, and BW Bridge inside SAP Datasphere. They do not share a maintenance horizon — always ask which one before answering anything.
Installed base: 20,000-30,000 BW 7.5 customers worldwide (SAP — Dominik Kurz, Sapphire 2025). A floor from public disclosure, not a census.
Do not confuse it with ~17,000, which is the ECC (ERP) installed base and belongs to a different product entirely.
The modelling vocabulary — InfoProvider, DSO, InfoCube, transformation, process chain — is what actually transfers to a successor, more than any single artefact does.
No free, primary, enumerable list of BW customers exists publicly; commercial databases disagree by a factor of six.

Terms used on this page

InfoObject: The atomic BW modelling unit — a characteristic or key figure, carrying its own master data, texts and hierarchies.
DSO (DataStore Object): The consolidated staging layer; holds detailed records with change-log semantics.
InfoCube: The classic star-schema object optimised for query; removed in BW/4HANA in favour of the aDSO.
Process chain: BW's orchestration object — the scheduled dependency graph that runs loads and activations.
BW Bridge: A BW runtime hosted inside SAP Datasphere, a landing zone for existing BW content rather than a place to build new models.

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.