Every entry names what the golden record holds, how records match, where the record sits in the hierarchies, sample rules at three levels, the transactions that refer to it, the measures and drill-downs, the security pattern, the lookup API, and what the domain reads and writes on SAP S/4HANA, Oracle Fusion, Salesforce, Workday, ServiceNow, Snowflake and Databricks.
Each card opens the domain page; the system pages are one click further.
One record per real customer, assembled from the ERPs, the CRM and the portals, with every source key kept.
One record per vendor, with the legal entity, the sites that ship, the bank details that are verified and the terms that apply.
One record per person at a customer, supplier or partner, linked to the organisation they work for and the roles they hold.
One record per worker, from the HR system of record, matched to the ERP, the directory and the ticketing system.
One record per item: the global identity, the descriptions, the classification, and the plant-level data that planning and purchasing need.
One governed structure per product per plant: components, quantities, effectivity, alternates and phantoms, consistent with the golden materials.
The trees that group products for sales, planning, sourcing and reporting, kept as versioned hierarchies with one leaf per golden item.
One record per physical asset: identity, location, ownership, technical structure and the maintenance and IT records that refer to it.
Prices, discounts and surcharges as governed master data with validity, scale and precedence, tied to golden products and customers.
One record per physical site: plant, distribution centre, office, store or lab, with its codes in every system and its calendar, address and roles.
The storage structure inside a site: warehouses, storage locations, zones and bins, as one hierarchy that stock movements refer to.
Verified, standardised addresses with geocodes and delivery instructions, shared by customers, suppliers, sites and contacts.
The chart of accounts as governed master data: one account list, its groupings, its company-code views and the mappings to every local chart.
Responsibility units as governed master data: cost centres, profit centres, their managers, their hierarchies and their validity, consistent across finance, HR and planning.
Every legal entity of the group with its registrations, addresses, officers, ownership and the company codes and ledgers that represent it in each system.
Bank accounts of customers, suppliers and the company's own entities, verified before use, masked by default and audited on every read.
Tax codes, rates, jurisdictions and their validity as reference data shared by every system that prices, invoices or reports.
Units and their conversions as one governed list, with the item-specific conversions that purchasing, sales and planning rely on.
Currency codes, decimals and the exchange-rate series every system converts with, kept once with a version for each rate date.
The code lists every system needs, kept once: countries and regions, Incoterms, payment terms, languages, and the crosswalk to each system's local codes.
Factory, fiscal and planning calendars as governed reference data: working days, periods, weeks and buckets that every plan and report agrees on.
Lead times, lot sizes, safety stocks, planning strategies and horizons per item and site, governed with rules and history so the plan runs on numbers somebody owns.
Work centres, capacities and routings as governed master data consistent with the BOMs and the site calendars.
Which supplier supplies which item to which site, at what price and lead time, with quotas and validity, as one governed set of relationships.
Purchase and sales agreements as master data: parties, items, prices, validity and limits, linked to the orders released against them.
Carriers, service levels and lanes between sites and regions, with transit times and rates, kept as master data the planning and transport systems agree on.
Harmonised system, tariff and commodity codes assigned to golden items, with validity and evidence, so customs, sourcing and reporting classify the same way.
Country of origin, substance declarations, certifications and restrictions per golden item, with evidence and validity, ready for customs, customers and regulators.
The organisation as governed master data: units, positions, their managers and cost centres, versioned so every system shows the same structure on the same day.
Resellers, distributors and agents as one party record with their territories, tiers, agreements and the sell-through data that measures them.
Customer · Supplier · Business contact · Employee · Organisation units and positions · Distributors and channel partners
Material and product · Bill of materials · Product classification · Equipment and assets · Price lists and conditions
Plant and site · Warehouse and storage location · Ship-to and delivery addresses
General ledger account · Cost centre and profit centre · Legal entity and company code · Bank and payment details · Tax codes and jurisdictions
Units of measure · Currencies and exchange rates · Countries, regions and code lists · Calendars and time profiles
Planning parameters · Routings and work centres · Sourcing rules and supplier-item links · Contracts and agreements · Carriers and transport lanes · Commodity and tariff codes · Product compliance attributes
| Section | What it answers |
|---|---|
| The golden record | which attribute groups it holds and which source usually wins each |
| How records match | the strong keys, the standardised attributes and the deciding evidence |
| Where it sits | the hierarchies the domain uses, several per entity |
| Rules at three levels | sample column, row and business rules |
| What refers to it | the transactions in the bed, the measures and the drill-downs |
| Security pattern | what is masked, who edits, who reads |
| The lookup API | a request and its answer |
| On your systems | one page per system: objects, fields, keys, write path, prerequisites, ECC and EBS notes |
| A day with it | an illustrative story, labelled |
Yes. A domain is a model with keys, rules and hierarchies; the catalogue templates cover the thirty most common, and a new one follows the same structure.
SAP S/4HANA and Oracle Fusion carry the most objects; Salesforce, Workday and ServiceNow where the domain lives there; Snowflake and Databricks for history and analytics.
From the showcase runs and engagements: the count of attribute groups, keys, hierarchies and systems per domain. They are estimates, labelled as such.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
