Concept card

BW Data Product Generator

As of 2026-09-27

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

What is BW Data Product Generator?

The BW Data Product Generator is SAP's add-on for BW 7.5 and BW/4HANA that turns existing InfoProviders into governed Business Data Cloud data products — moving data and structure into BDC while BW stays the source, and leaving BEx and transformation logic to be redesigned.

The BW Data Product Generator is the SAP add-on for SAP BW 7.5 and SAP BW/4HANA that reads existing InfoProviders — advanced DataStore Objects, CompositeProviders and the InfoObjects they use — and generates governed Business Data Cloud data products from them. The generated products are published into BDC, where SAP Datasphere, SAP Analytics Cloud and, through the object store, Databricks consume them; the BW system remains the system of record during the coexistence period. It exists because the alternative — rebuilding every InfoProvider by hand in Datasphere before any BDC consumer can see the data — does not scale across a large BW estate, and because SAP needs a path that keeps BW 7.5 customers moving before the maintenance horizon (mainstream 2027, extended 2030) without forcing a big-bang rewrite.

What it generates, and what it does not

The Generator moves data and structure: key fields, key figures, characteristics and the provider's shape become a data product whose content is provisioned from BW into Business Data Cloud on a schedule. It does not convert BEx queries into SAP Analytics Cloud stories, it does not translate BW transformation or routine logic, and it does not wire Data Access Controls on the consuming side — those remain design work in Datasphere and SAC. The semantic layer on the Datasphere side comes from a separate, documented path, the BW/4HANA model transfer, which imports BW queries and CompositeProviders as Datasphere views and Analytic Models. A consultant who conflates the two paths promises the client a finished semantic model where the tooling only delivers provisioned data.

Why it matters

It is the documented path that brings BW 7.5 and BW/4HANA data into Business Data Cloud without a big-bang rewrite, before the BW 7.5 maintenance horizon (mainstream 2027, extended 2030).
Reconciliation testing must run from the first generated product onward — a product whose data is correct but whose meaning is incomplete drifts silently until an auditor reads it.
The Generator provisions data; BEx queries and transformation logic are rebuilt by hand — budgeting it as a full migration tool understates effort.

Key points

An SAP add-on for BW 7.5 and BW/4HANA: it generates governed BDC data products from advanced DataStore Objects and CompositeProviders, and publishes them into Business Data Cloud.
It moves data and structure; it converts neither BEx queries nor transformation logic — those are redesign work in Datasphere and SAC.
The Datasphere semantic layer comes from the separate BW/4HANA model transfer; do not sell the two paths as one tool.
BW stays the system of record during coexistence — the Generator is a provisioning path, not a decommissioning tool.
SAP publishes no productivity multiplier; any figure in a proposal is the consultant's own estimate and must be labelled as such.
Reconciliation failures on a structurally clean object usually trace to a BEx-query-level calculation (currency conversion, hierarchy-based exception) that lives outside the InfoProvider the Generator actually reads.
A separate, newer path — the SAP Business Data Cloud Modernization Option for SAP BW NetWeaver (subscription open September 2026) — lets a BW NetWeaver system itself run inside BDC without re-architecture; do not conflate it with the Generator, which provisions data out of BW 7.5/BW4HANA, not the whole system.

Terms used on this page

BW Data Product Generator: SAP add-on for BW 7.5 and BW/4HANA that generates governed BDC data products from InfoProviders.
Data product (BDC): A governed, published dataset in Business Data Cloud, consumable by Datasphere, SAC and Databricks.
BW/4HANA model transfer: The separate path that imports BW queries and CompositeProviders into Datasphere as views and Analytic Models.
Coexistence: The period during which BW remains the system of record while BDC consumers read the generated products.
Reconciliation testing: Reproducing legacy BW report figures from the generated product, from the first product onward.

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.