Domain catalogue Parties

Customer

One record per real customer, assembled from the ERPs, the CRM and the portals, with every source key kept.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSalesforceCRMSnowflakelakehouseDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN CUSTOMERCustomerone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the customer record comes from, how it is assembled, and who reads it. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
6
attribute groups in the golden record
catalogue
6
match keys
catalogue
4
hierarchies the record sits in
catalogue
5
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today the same customer is a sold-to in SAP, a party in Oracle, an account in Salesforce and a row in three spreadsheets, each with its own number, spelling and address.

With Lima the customers are read where they live, matched on VAT ID or tax number and DUNS, assembled field by field and published as one golden record per real customer, with every source key underneath. All sales orders, deliveries, invoices, open receivables, opportunities and tickets for the customer, across the systems, with live counts are one click away, because the transactions sit in the same bed.

The golden record

6 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Identitylegal name, trading names, registration number, VAT IDs, DUNS, website
wins: registry and ERP first
Addressesregistered, billing, ship-to, with validity dates
wins: ERP, verified by an address service
Contacts and rolesbuyer, accounts payable, executive sponsor
wins: CRM first, portal second
Commercial termspayment terms, currency, credit limit, price list, Incoterms
wins: ERP contract data
Classificationindustry, segment, account tier, region, sales organisation
wins: CRM and the hierarchies
Lifecycle and statusprospect, active, dormant, blocked, with reasons and dates
wins: derived from transactions and stewards
How records match

The keys, in order

VAT ID or tax numberDUNSregistration numberlegal name and country (fuzzy)street, postcode and city (standardised)domain of the e-mail addresses

Two records match when a strong key agrees, or when name and address agree closely and no strong key disagrees.

Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.

Where it sits

4 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Legalparent company, subsidiaries, branches, from registries and D&B
Salessales organisation, region, key-account team
Billingpayer, sold-to, ship-to relationships from the ERP
Industrysector and sub-sector codes

A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
ColumnVAT ID has the format of its country and passes the VIES check
postcode matches the country's pattern
currency is in the code list
Rowa ship-to address carries the same country as its region code
a customer with a credit limit has a verified legal name and registration number
a blocked customer carries a reason and a date
Businessopen orders plus open receivables stay under the credit limit
every child of a legal parent uses the parent's payment terms or an approved exception
revenue by sales region equals the sum of its customers
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Sales ordersSAP VBAK · VBAP; Oracle order headers and lines
Deliveries and shipmentsSAP LIKP · LIPS; 3PL feeds
Invoices and receivablesSAP BSID · ACDOCA; Oracle AR
Opportunities and quotesSalesforce Opportunity, Quote
Service ticketsServiceNow incidents and cases
revenue by monthopen order valueon-time deliverydays sales outstandingbookings vs invoicedcomplaints per 1,000 orders

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens all sales orders, deliveries, invoices, open receivables, opportunities and tickets for the customer, across the systems, with live counts.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Bank details and credit limits masked for most roles; contacts visible to the account team; personal data of contacts under the privacy policy. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/customer/lookup
{
  "legal_name": "Northbay Logistics Inc",
  "country": "US",
  "vat_id": "",
  "postcode": "94306"
}
response
200 OK
{
  "golden_id": "C-00842",
  "confidence": 0.94,
  "legal_name": "Northbay Logistics, Inc.",
  "xref": {
    "sap": "0000048210",
    "oracle": "300000012",
    "salesforce": "001Ab00000QxL2m"
  },
  "open_orders": 184
}

The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.

A distributor with 21,000 customer records in SAP and 34,000 accounts in Salesforce found 6,100 pairs describing the same company. After the first match run the sales team saw open orders, overdue invoices and open tickets on one account page, and the credit team stopped approving limits twice for the same buyer.

illustrative scenario · Customer
Terms on this page

Sold-to, ship-to, payerThe partner roles an ERP keeps for one customer: who orders, who receives, who pays.
Cross-referenceThe list of source keys that belong to one golden record.
Credit limitThe open exposure a customer is allowed; a business rule compares it with orders and receivables.
Golden recordThe one record for a real customer, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.

How long to the first golden view?

One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

High-tech and semiconductor, Consumer goods, Industrial manufacturing, Telecom, Financial services. The industry pages show the domains each starts with.

See your first domain built on your data

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.