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.
| Domain | Related objects with live counts |
|---|---|
| Customer | sales orders · deliveries · invoices and receivables · opportunities and quotes · tickets · contacts · addresses |
| Supplier | purchase orders · receipts · invoices and payables · contracts · quality incidents · sourcing links · bank accounts |
| Material | order lines · purchase lines · stock by plant and bin · production orders · forecast rows · BOMs it appears in · sources |
| Site | stock · orders · production · headcount · lanes · storage structure |
| Cost centre | postings · budget lines · positions · hierarchy versions |
| Asset | work orders · tickets · depreciation · readings · technical structure |
Every domain page lists its related objects and the systems they come from.
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.
They come from the same query as the rows, under each column's freshness contract; a replica column says so.
Yes; the cross-reference keeps every source key, so orders under the absorbed number appear with the rest.
It opens the source's own screen as you, so the source's licence and permissions apply.
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.