Capabilities Drill-downs

From one golden record to everything that refers to it, across systems.

All the sales orders for a customer, all the purchase orders for a supplier, all the stock for a material at every plant, all the tickets for an asset: one click from the record, live counts, and the rows in a grid.

Northbay Logisticsgolden C-00842 · 4 source keysSales ordersSAP VBAK · 184 openInvoicesOracle AR · 12 overdueService ticketsServiceNow · 3 openOpportunitiesSalesforce · 2 in stage 4Shipments3PL feed · 27 in transitWHY IT WORKSgolden id → KUNNR 0000048210→ Oracle party 300000012→ ServiceNow sys_id 7f3a…→ Salesforce 001Ab…one click, one query, live countsevery list is a real grid: sort, filter, open the source row, or pivot it by month
One golden customer, five kinds of related rows in four systems, one click each.
5
related objects on the customer page by default
catalogue
4
systems joined for one customer on the showcase estate
showcase
live
counts, from the same query as the rows
product
2
clicks from a pivot cell to the source row
product
Step by step

From the customer page to an order line in SAP

Open the recordGolden customer C-00842 shows its attribute groups and, on the right, the related objects with live counts: 184 open sales orders, 12 overdue invoices, 3 open tickets, 2 opportunities.
What refers to what

The related objects per domain, from the catalogue

DomainRelated objects with live counts
Customersales orders · deliveries · invoices and receivables · opportunities and quotes · tickets · contacts · addresses
Supplierpurchase orders · receipts · invoices and payables · contracts · quality incidents · sourcing links · bank accounts
Materialorder lines · purchase lines · stock by plant and bin · production orders · forecast rows · BOMs it appears in · sources
Sitestock · orders · production · headcount · lanes · storage structure
Cost centrepostings · budget lines · positions · hierarchy versions
Assetwork orders · tickets · depreciation · readings · technical structure

Every domain page lists its related objects and the systems they come from.

Relationships from the facts

Edges the data proves, beside the ones people curate

A relationship graph usually holds what stewards entered: parent companies, contacts, sites. Lima adds the edges the transactions prove: this customer buys these products from these plants; this supplier ships to these sites; these two suppliers share invoices. The edges are computed from the bed, so they are live and carry counts.

The graph is a view: click a node to open its record, an edge to open the rows that prove it.

Curated edgesparent, contact, site, agreement
Proven edgesbuys, ships to, shares invoices, appears in BOM
Countslive, from the same query
Opennode → record; edge → rows
Terms on this page

Drill-downFollowing a key from a record or a pivot cell to the rows behind it, down to the source row.
Related objectA table whose rows refer to a golden record through a foreign key.
Proven edgeA relationship computed from transactions; a curated edge is one a person entered.
Questions

Are the counts always live?

They come from the same query as the rows, under each column's freshness contract; a replica column says so.

Can I drill from a merged customer into orders placed under the old number?

Yes; the cross-reference keeps every source key, so orders under the absorbed number appear with the rest.

Does opening the source row need a licence for that system?

It opens the source's own screen as you, so the source's licence and permissions apply.

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.