Concept card

SAP BW Data Product Generator — The BW Modernization Path

As of 2026-07-23

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 Data Product Generator — The BW Modernization Path?

The BW Data Product Generator converts roughly 80% of a customer's BW estate into BDC Data Products automatically — the third modernization path for the ~17,000 ECC and ~4,000 MEE BW customers who need one.

What it is

The BW Data Product Generator is the Available-today tool SAP shipped at Sapphire 2026 as the canonical path off SAP BW into BDC. It reads existing BW InfoProviders (Composite Providers, ADSOs, queries) and emits BDC Data Products that preserve the BW semantic layer.

Why this matters for the BW cliff. Approximately 17,000 ECC and 4,000 MEE BW customers globally need a modernization path. The two historical options were (a) rebuild from scratch in Datasphere — expensive, slow, risky — or (b) lift-and-shift to BW/4HANA — buys 3-5 years but doesn't solve the lakehouse plus AI problem. The Generator is option (c): preserve BW investment, convert to Data Products, get on the BDC roadmap.

What the Generator emits. For each BW InfoProvider, it produces (1) a BDC Data Product with the same fields, types, and business KPIs, (2) lineage back to the BW source, (3) governance metadata. The companion Query template generator handles the query layer. Net result: a BW-savvy consultant can convert approximately 80% of a customer's existing BW estate into BDC Data Products without rewriting calculation logic.

The 20% that doesn't convert cleanly. Custom ABAP transformations, complex Composite Provider unions, and process chains needing orchestration outside the Generator's scope — these require manual remodelling in Datasphere or BDC native modelling. The Generator surfaces these as conversion warnings.

Why it matters

The customer base is quantified: approximately 17,000 ECC and 4,000 MEE BW customers globally need a modernization path — this isn't a niche tool.
The 80/20 split is explicit and actionable: the Generator automates ~80% of InfoProviders into Data Products with preserved lineage, while the remaining 20% (custom ABAP transforms, complex Composite Provider unions) needs manual remodelling.
The decision rule names both sides: use the Generator when BW logic is trusted and reporting can't freeze; use native Datasphere remodelling when the BW logic itself is the problem (undocumented exits, 10+ years of layered workarounds).

Key points

Available today — canonical SAP path off BW into BDC.
Converts InfoProviders (Composite Providers, ADSOs) into BDC Data Products preserving semantic layer.
Companion Query template generator handles BW query layer.
Converts ~80% of typical BW estate without rewriting calculation logic.
Targets the ~17,000 ECC + ~4,000 MEE BW customers needing a modernization path (the Analytics Legends research ledger).
Conversion warnings flag custom ABAP transformations + complex Composite Provider unions for manual remodelling.
SAP BW Data Product Generator — The BW Modernization Path is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.

Terms used on this page

InfoProvider: SAP BW abstraction for any object queryable by BW queries — Composite Providers, ADSOs (Advanced DataStore Objects), InfoCubes, MultiProviders.
Composite Provider: BW object that unions or joins multiple InfoProviders into a single queryable surface; the most common BW modelling pattern post-2015.
ADSO: Advanced DataStore Object — BW/4HANA's primary persistent data store, replacing classic DSO/InfoCube; supports both transactional inserts and aggregated reporting.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.

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.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

SAP Datasphere migration cost: what drives the bill