Analytics Legends The knowledge platform for SAP Analytics
Guide

SAP BW4HANA 2023 — what a release designation settles, and what it does not

As of 2026-08-14

A BW/4HANA release designation settles two things and no more: which functional scope your system carries, and which maintenance terms attach to it. It does not settle the size of a migration, the conversion route, or whether BW/4HANA is the right destination — those are decided by the object model and the state of the estate. If you arrived here sizing a programme, the release number is the least informative input you have.

What the release number does control

It controls scope and support. Which capabilities are shipped in your system, and which maintenance commitment applies to it, are both keyed to the release — and the maintenance half is the one worth checking, because it moved recently: SAP BW/4HANA maintenance has been aligned with the SAP Business Suite roadmap to 2040, in a decision independent of the extension of SAP BW 7.5 extended maintenance to 31 December 2030.

What that alignment means for a specific release is a question for SAP's maintenance schedule for that release, read alongside the customer's contract. We do not restate a per-release support matrix here, and a page that does should be treated as a secondary source that will age badly.

The practical rule is unchanged by any release: your date depends on product, release and contract, and the only authority is the schedule for your exact version.

What it does not control — the object model

BW/4HANA is a separate product with its own code line, HANA-only, generally available since 2016, and the property that shapes every migration is not the release number but the deliberately reduced object model that has defined the product since the start.

The Advanced DSO absorbed what standard DSOs, write-optimised DSOs and InfoCubes did separately. CompositeProviders absorbed MultiProviders and InfoSets. Classic InfoCubes, 3.x dataflows and transfer rules are gone.

Because the target carries fewer object types than the source, no faithful one-to-one translation exists for a mature BW estate — every InfoCube becomes an aDSO with a chosen configuration, every MultiProvider becomes a CompositeProvider with an explicit join-or-union decision. That is why effort estimates keyed to a release number are wrong in both directions, and why the same release can host a six-month programme at one customer and a two-year one at another.

Reading a firm's release claim

Partner marketing quotes release numbers because they are easy to verify and easy to standardise. Treat a stated release as a statement about a delivery bench's currency, not about its judgement.

The questions that separate benches are different in kind: what share of your last estate landed in the auto-eligible complexity band, what did you rule out and why, who owned report retirement, and what debt travelled across on the lift-and-shift you delivered last year.

The honest scale reading also belongs in this conversation. Our registry carries a floor of roughly 2,500 BW/4HANA customers against roughly 18,000 for BW overall — both floors from public disclosure rather than a register. The modernised cohort is a clear minority of the BW estate, so a firm's BW/4HANA reference list is being drawn from a much smaller pool than its BW reference list, whatever release either mentions.

What we cannot assert

We do not publish a feature list or a support matrix for any individual BW/4HANA release. Release-level scope and maintenance terms are settled in SAP's own release and maintenance documentation for that version; anything we restated here would be a second copy that drifts. What we do carry is the product-level maintenance alignment recorded above.

Frequently asked

Which BW/4HANA release should we target?

Target the maintenance commitment and the functional scope you need, then confirm both against SAP's schedule for that release. The release choice does not change the shape of the migration work, which is set by the object-model gap between source and target.

How long is BW/4HANA maintained?

BW/4HANA maintenance was aligned with the SAP Business Suite roadmap to 2040, in a decision independent of the SAP BW 7.5 extended-maintenance move to 31 December 2030. What applies to a specific release and contract is settled in SAP's own schedule.

Is BW/4HANA a release of SAP BW?

No — it is a separate product with its own code line, HANA-only, generally available since 2016. Reading the name as a release number is what produces the phrase "we'll just upgrade to BW/4", and that framing under-sizes the work every time.

Does a newer release reduce the migration effort?

Not materially. The effort concentrates in the residue that tooling cannot decide — custom logic, unusual hierarchies, bespoke authorisations — and that residue is a property of the source estate, not of the target release.

What this page is built on

Read next