Master data Your first domain

Your first golden records in one working day.

Bring two systems that hold the same suppliers, customers or materials. By the end of the day the sources are registered and read in place, the match has run on live rows, your steward has worked the first queue, the column and row rules are on, and the golden view is published with its lookup API.

09:00connecttwo sources registered09:40modelattributes and keys mapped10:30matchfirst run on live rows13:00reviewqueue worked with the steward15:00rulescolumn and row rules on16:30publishgolden view live, API answeringshowcase estate · supplier domain from SAP and a portal · 41,800 source records · 6 h 52 min to a published golden viewyour first domain runs the same steps on your data, with your steward in the room
The showcase run: supplier records from SAP S/4HANA and a supplier portal. Every time is from the recorded session. Showcase estate.
6 h 52 min
from the first connection to the published golden view
showcase
41,800
source records in the two systems
showcase
9,340
golden suppliers after the match
showcase
612
pairs sent to the steward queue, 41 minutes to clear
showcase
0
rows copied out of SAP to get there
product
The day, hour by hour

What happens in each step, and what you see on the screen

The same seven steps run for every domain; the supplier domain is the walkthrough because it touches parties, addresses, bank details and purchasing data at once.

09:00
Connect the sourcesSAP S/4HANA (LFA1, LFB1, LFM1, LFBK, ADRC) and the supplier portal are registered from the connector catalogue. Each object shows its rows at once, read in place, with the SAP user's own authorisations.
09:40
Model the domainThe supplier template from the catalogue maps the attribute groups: identity, sites, bank and payment, compliance, purchasing data, lifecycle. Keys are set: VAT ID, DUNS, verified IBAN, name and country, standardised address.
10:30
Run the matchThe rules run on the live rows: 41,800 records, 33,100 pairs above the review line, 32,488 above the merge line. The steward sees the first cluster on screen before the run has finished.
13:00
Work the queue612 pairs sit between the lines, sorted by confidence and open purchase-order value. Two records side by side, the transactions of each, one click to approve, reject or ask. 41 minutes.
15:00
Switch on the rulesIBAN checksum and country, VAT format and VIES, screening present before payment data, one active account per supplier. The rules show the rows they would flag before they are saved: 71 rows, 3 blocked.
16:30
Publish and serveThe golden view is published as version 1 with a note; the lookup API answers a POST from the portal with the golden id, the record and the cross-reference; the grid, the pivot by category and month, and the audit trail are live.
What you leave with

Six things that exist at the end of the day

A golden view

One record per supplier with every source key underneath, published as version 1.

A steward queue

Sorted by confidence and value, with the evidence per proposal and one-click actions.

Rules that run

Column and row rules on save and on demand, with the rows they flag.

A lookup API

POST the keys you know, receive the golden record, its cross-reference and open orders.

A pivot

Spend by category and month on golden suppliers, with drill-down to the purchase orders.

An audit trail

Every merge, every rule result and every read of the bank column, from minute one.

What you bring

Four things to have ready

Two systems that hold the same entitiesAn SAP or Oracle system and one other: a CRM, a portal, a lake or a second ERP. Read access for a technical user is enough.
After the day

From version 1 to production

WeekWhat happensWho
1Rules extended to business rules over totals; hierarchies loaded and versioned; security layers set per rolesteward · configurator
2Write-back tested per object, off until the test write succeeds; approval rules set; second environment promotedapplication team
3Consumers connected: planning system, BI, SmartApps, agents; the API published in the developer portalintegration
4Production: the domain runs with its queue, its rules and its audit; the fixed price for the second domain is writteneveryone

The engagement is fixed-price and written before the work starts: one domain on two sources to a production-grade version. The pricing page lists the entry offers.

Terms on this page

Merge line and review lineThe two scores per match rule: pairs above the merge line merge automatically; pairs between the lines go to the steward.
Golden viewThe published, versioned result of a domain: one row per entity, readable by grids, pivots, SQL and APIs.
Showcase estateLima's configured demonstration estate; every figure from it is labelled showcase.
Questions

Can the day run on our production systems?

Yes, with read access. Nothing is written back on the day; write-back is enabled per object later, after a test write succeeds.

What if our data is worse than the showcase data?

The match rules and thresholds are set on your rows, and the queue shows what needs a person. A messy domain produces a longer queue on day one and a shorter one every day after.

Is the day free?

The guided day is part of the fixed-price first domain. The demonstration on the showcase estate is free, on request.

Book the day

Two systems, one steward, one question. By 16:30 the golden view is live with its API.