Concept card

SAP Data Products — The 300+ Catalogue (target 500+ by Q2 2026)

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 Data Products — The 300+ Catalogue (target 500+ by Q2 2026)?

SAP Data Products are typed, governed, versioned assets that let a Joule agent or SAC dashboard query a domain object directly — no raw table joins — with 300+ live today and a committed 500+ by Q2 2026.

What it is

SAP Data Products are curated, versioned, governed data assets shaped for downstream consumption — the building blocks of BDC. Sapphire 2026 confirmed 300+ live today and committed to 500+ by Q2 2026.

Domain coverage visible in the keynote slide. Finance: Billing & Payments · Cash Flow · Compensation. Supply Chain: Deliveries · Inventory · Manufacturing Material · Purchase Orders. Human Resources: Headcount. Service & Sales: Cases & Tickets. Plus extensions across Spend Management and Industry-specific products.

What a Data Product actually contains. Each Data Product is a typed schema + business-meaningful KPIs + lineage to the source SAP system + governance metadata (owner, refresh cadence, classification) + the data itself. A consumer (Joule agent, SAC dashboard, Datasphere model) queries a Data Product as a first-class object — no need to write joins against raw S/4HANA tables.

Why 300 → 500 matters. Every net-new Data Product is a feature SAP delivers for free to existing BDC customers. The pace (200 products added in 2 quarters) is the proof-point SAP is investing in BDC content depth, not just platform. A consultant should track the quarterly Data Product release notes the way an SAP BW consultant used to track Business Content shipments.

Why it matters

The consumption pattern is concrete: a consumer queries a Data Product as a first-class object, skipping hand-written joins against raw S/4HANA tables.
The 300-to-500 pace (200 net-new in two quarters) is the stated proof-point that SAP is investing in content depth, not just platform — worth tracking the way BW consultants tracked Business Content releases.
The build-vs-buy rule is explicit: use a packaged Data Product when the standard domain and KPI set match the requirement — build custom Datasphere only when business logic genuinely diverges.

Key points

300+ Data Products live today; commitment to 500+ by Q2 2026 (+200 net-new in 2 quarters).
Domains: Finance (Billing, Cash Flow, Comp) · SCM (Deliveries, Inventory, Mfg Mat, POs) · HR (Headcount) · Service (Cases & Tickets) · Spend · Industry.
Each product: typed schema + KPIs + lineage + governance metadata + data.
Consumers (Joule, SAC, Datasphere) query Data Products as first-class objects — no raw S/4HANA joins needed.
SAP BW Data Product Generator converts BW InfoProviders into Data Products — canonical BW modernization path.
SAP Data Products — The 300+ Catalogue (target 500+ by Q2 2026) 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.
Define owner, metric, threshold, support path, and rollback before scaling.

Terms used on this page

Data Product: A curated, versioned, governed data asset with typed schema, business KPIs, lineage, and governance metadata — the canonical consumable in BDC.
BW Data Product Generator: Available BDC tool that converts existing SAP BW InfoProviders into BDC Data Products, the canonical BW modernization path (no rebuild from scratch).
Query template generator: Companion BW tool that converts BW queries into BDC-compatible query templates.
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.