SAP BW (Business Warehouse)

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.

The installed base, stated carefully. The registry floor is ~18,000 customers. Treat it as a floor and not a census: SAP does not publish a BW customer count on a regular cadence, the figure circulating in the market ranges from ~15,000 "active" to ~18,000 installed, and commercial customer databases disagree with each other by a factor of six (879 to 5,693 named companies across four vendors, all paywalled, all marketing-sourced). No free, primary, enumerable list of BW customers exists publicly. Anyone quoting a precise BW customer count without naming the source and the date is quoting marketing.

The ECC confusion. The number ~17,000 belongs to ECC, SAP's previous-generation ERP. It has migrated into BW sentences often enough that it now appears on both sides of the same argument. BW and ECC are different products with different install bases and different deadlines; a migration case that mixes them is measuring two populations as one.

What this concept does not settle. Maintenance dates depend on product, release and contract, and this page states none. See SAP BW End of Support for the four cohorts and the four paths.

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 floor: ~18,000 customers. 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.

Common pitfalls

• Treating "BW" as one product — Signal: A deadline or an effort estimate quoted without naming the generation Fix: Ask which of the four; the answer changes the paths and the horizon.
• Quoting the ECC installed base as BW — Signal: ~17,000 appears next to BW Fix: 17,000 is ECC. The BW floor is ~18,000 — check which population the sentence is about.
• Buying a customer list as evidence — Signal: A vendor database quotes a precise BW customer count Fix: Four vendors disagree by 6×, all paywalled and marketing-sourced. Treat as directional at best.

Decision framework

Sources

1. SAP Help — SAP BW/4HANA documentation (maintenance and release info)
2. SAP Help — SAP Business Data Cloud documentation
3. SAP Help — SAP Datasphere documentation
4. SAP Help — SAP S/4HANA documentation
5. DSAG — German-speaking SAP user group (maintenance-horizon advocacy)
6. ASUG — Americas' SAP Users' Group
7. BARC — independent analyst research on data platforms