SAP BW/4HANA

What it is

SAP BW/4HANA is SAP's HANA-only data warehouse product, generally available since 2016. The naming invites a mistake worth naming early: it is not "BW, release 4". It is a separate product with its own code line, and a customer does not upgrade into it so much as move into it.

What was deliberately removed. BW accumulated object types over eighteen years, and BW/4HANA cut them back. The Advanced DSO (aDSO) absorbed the roles that standard DSOs, write-optimised DSOs and InfoCubes played separately — one object with configuration flags instead of three objects with distinct semantics. CompositeProviders absorbed MultiProviders and InfoSets. Classic InfoCubes, 3.x dataflows, transfer rules and the old extractor-side modelling are gone. What survives is the part that carried the analytical meaning: InfoObjects, transformations, DTPs, process chains, and the query layer.

Why that makes it a modelling exercise. Because the target has fewer object types than the source, there is no faithful one-to-one translation for a mature BW estate. Every InfoCube must become an aDSO with a chosen configuration; every MultiProvider must become a CompositeProvider with an explicit join or union decision. Tooling can carry a large share of it and SAP ships conversion paths — in-place, remote, and shell — but the residue is judgement, and the residue is where the effort concentrates. This is the mechanism behind the observation that BW/4HANA projects rarely resemble upgrades.

Scale, stated as a floor. The registry carries ~2,500 BW/4HANA customers against a ~18,000 floor for BW overall. Both are floors from public disclosure rather than counts from a register, and the ratio is the more robust reading: the modernised cohort is a clear minority of the BW estate. That asymmetry, not either number on its own, is what drives the migration-demand argument.

Where it sits against Datasphere and BDC. BW/4HANA is the successor within the BW lineage. SAP Datasphere is a cloud data-warehousing service with a different modelling model, and SAP Business Data Cloud is the packaged data-product layer above it. They are not rival answers to one question. A customer can run BW/4HANA and Datasphere together, and BW Bridge exists precisely to let BW content land inside Datasphere. Treating the choice as either/or is the most common framing error in this part of the stack.

Why it matters

• BW/4HANA is the one path that keeps the BW modelling paradigm intact. Whether that is an asset or a delay depends on where the customer intends to be once BDC and Datasphere are the strategic targets.

Key points

• A separate product, not a BW release: its own code line, HANA-only, generally available since 2016.
• Installed-base floor ~2,500 customers against a ~18,000 BW floor — the modern cohort is a minority of the BW estate.
• The aDSO replaces the DSO/InfoCube split; CompositeProviders replace MultiProviders and InfoSets. Fewer object types, more decisions pushed into modelling.
• 🔴 It is a successor to BW, not an alternative to Datasphere or BDC — they sit at different layers, and choosing one does not settle the other.
• Conversion paths exist (in-place, remote, shell) but the residue is judgement, and that residue is where the effort concentrates.

Common pitfalls

• Reading the name as a release number — Signal: "We'll just upgrade to BW/4" Fix: Separate product, separate code line. Plan a move, not an upgrade.
• Framing BW/4HANA against Datasphere as either/or — Signal: A slide with one arrow and two boxes Fix: Different layers. BW Bridge exists precisely so both can hold at once.
• Quoting the BW installed base for BW/4HANA — Signal: ~18,000 attached to BW/4HANA Fix: ~18,000 is BW overall; the BW/4HANA floor is ~2,500. The ratio is the point.

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