Domain & Data Product Design
Domain principles
A domain should have:
- accountable ownership
- clear business scope
- defined source systems
- reusable semantic assets
- access policy
- quality expectations
- lifecycle ownership
Data product test
A candidate data product should be:
- understandable
- discoverable
- governed
- reusable
- versionable
- operationally supported
SAP's current catalog documentation treats data products as coherent datasets exposed for consumption and assigns lifecycle responsibilities to providers.
Example
A Procurement Spend product might contain:
- supplier
- purchasing organization
- material
- purchase order
- invoice
- spend measure
- currency
- fiscal period
The architecture must define ownership, freshness, quality, security, and consumer expectations—not just the table list.
Anti-pattern
Do not call every table a data product. A product is a governed consumption contract, not a storage object.