Concept card

Data Products

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 Data Products?

A Data Product replaces 'tables consumers can query' with a versioned schema contract plus a measured SLA — the shift that stops schema changes from silently breaking half of downstream consumers.

What is a data product in SAP business data cloud?

Short answer above

A Data Product in SAP Business Data Cloud is a published, contractually defined dataset — not just a table someone happens to have access to, but a dataset with a versioned schema, a documented service-level agreement covering freshness, completeness, and accuracy, an explicit roster of authorised consumers, and a named governance owner accountable for all of it. The distinction between a table you can query and a product you formally subscribe to is, more than any single feature, what separates a 2020-era data warehouse from a 2026-era data platform, and it is the argument SAP makes directly against Snowflake or Databricks deployments that have not adopted an equivalent contract discipline through Unity Catalog or a comparable governance layer.

The five things that make something a Data Product

Why it matters

Breaking schema changes go through announce → grace period → release instead of shattering consumers overnight, letting producers refactor freely underneath.
SLA terms (freshness, completeness, accuracy) are measured and reported, not aspirational — auditors get lineage answers in 30 seconds instead of a scramble.
A mandatory consumer roster and subscription model kills the ad-hoc pattern where every team builds its own competing version of 'Customer' or 'Sales'.

Key points

Five-layer anatomy: schema contract · SLA · consumer roster · owner · lineage.
Contract-based: producer commits to schema + SLA; consumers subscribe; ad-hoc reads denied.
Subscription required (no direct table access).
Schema versioning: semver + 90-day deprecation cycle on major bumps.
Quarterly governance review with consumer reps.
Five canonical SAP Data Products: GL Balances · Customer Gold · Sales Orders · Product Hierarchy · HR Headcount.
GDPR-classification metadata mandatory on personal-data Data Products.
DSAG 2026 ranks Data Products #1 most-asked-about BDC feature.
Data Products 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

Data Product: Contractually-defined dataset published in BDC Catalog with versioned schema + SLA + consumer roster + governance owner.
Schema contract: Versioned column-and-type definition consumers subscribe to. Breaking changes require major version bump.
SLA (Data Product): Three-component commitment: freshness (max latency), completeness (% rows reflected), accuracy (% within bounds).
Consumer roster: Explicit list of authorised teams/services. Subscription-required; ad-hoc reads denied via DAC.
Governance owner: Single accountable person/team for the contract. Holds quarterly review with consumers.
Deprecation cycle: 90-day announce → grace → sunset flow for major version bumps. Consumers migrate or lose access.
Lineage + provenance: Source systems + transformation pipeline tracked in Catalog. Auditor-checkable in 30 seconds.
Catalog manifest: YAML/JSON document declaring the Data Product (~50-100 lines). Source of truth in BDC Catalog.

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.