Concept card

BW Data Product Generator

As of 2026-07-24T14:00:00Z

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 BW Data Product Generator?

The BW Data Product Generator turns 6-12 months of manual InfoCube conversion into 6-12 weeks of guided generation — the single biggest reason customers pick 2026-2028 as the migration window over waiting until 2030.

The BW Data Product Generator is the Business Data Cloud migration accelerator that reads existing SAP BW objects — InfoCubes, DataStore Objects, MultiProviders, BEx queries — and emits Business Data Cloud-native Data Products, preserving semantic types, hierarchies, restricted key figures, and authorisation patterns wherever a mapping exists. It exists because manual InfoCube-by-InfoCube conversion does not scale: unaided, a Tier-1 BW estate takes six to twelve months of hand modelling to migrate, and the Generator compresses the mechanical portion of that work into six to twelve weeks of guided generation plus targeted remediation on the objects that need a human. It is, in practical terms, the single biggest reason customers are choosing to migrate in the 2026-2028 window rather than deferring to the end of the decade: the tooling finally makes the business case for moving now instead of later.

The Four Conversion Paths

An InfoCube converts to a Data Product fact table, with dimensions becoming foreign-key relationships, key figures becoming measures, and fiscal-period assignments preserved. A DataStore Object converts to a Data Product detail table, keeping line-item granularity and its audit-trail semantics intact. A MultiProvider or CompositeProvider converts to a Data Product union view, surfacing the underlying federation pattern in Datasphere-native form. A BEx query converts to a SAP Analytics Cloud Story scaffold — a starting layout, not a finished report, and manual finishing is the norm rather than the exception here.

The Complexity-Score Gate

Why it matters

The complexity-score gate (1-5) auto-generates 70-80% of a typical Tier-1 customer's objects, leaving only 20-30% for mandatory manual redesign.
Reporting-parity testing requires every BW report to reproduce in BDC with auditor-grade reconciliation before cutover — skipping it risks silent report drift.
BEx query conversion only scaffolds a SAC Story skeleton — manual finishing is typical, so budgeting the Generator as fully automated for reports understates effort.

Key points

Four conversion paths: InfoCube · DSO · MultiProvider · BEx query.
Complexity-score 1-5 gates automation: 1-2 auto · 3 guided · 4-5 manual redesign.
Tier-1 distribution: 70-80% objects auto-eligible · 20-30% manual mandatory.
Reporting-parity testing auditor-grade (4-8h per InfoCube) — non-negotiable.
ABAP stubs require rewrite as Data Flow / SQL view (companion C006).
BW AUMs convert to DAC rules at lowest exposed layer (companion C008).
Tier-1 timeline: 12-18 mo manual → 6-9 mo with Generator.
Tier-1 fees: €1-1.8M manual → €500-900k with Generator.
BW Data Product Generator is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

BW Data Product Generator: BDC migration accelerator converting BW objects to BDC Data Products. Native; included in BDC licensing.
Complexity score: 1-5 rating per BW object. 1-2 auto · 3 guided · 4-5 manual redesign mandatory.
InfoCube → fact Data Product: Path 1: dimensions → FK, key figures → measures, fiscal-period preserved.
DSO → detail Data Product: Path 2: line-item granularity preserved with audit-trail semantics.
MultiProvider → union view: Path 3: federation pattern as Datasphere union view.
BEx query → SAC scaffold: Path 4: query layout to SAC Story skeleton; manual finishing typical.
Reporting-parity testing: Auditor-grade reconciliation: every BW report reproduces in BDC with documented variance.
ABAP stub: Generator output for custom ABAP transformation routines. Requires rewrite as Data Flow or Datasphere SQL view.

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.