Agentic AI Capability

The same supplier in three systems is recognised as one.

Your ERP calls a supplier 0000104471, the acquired division calls it 104471, and the portal calls it DF-1042.

THREE SYSTEMS, THREE RECORDSWHAT JUNO COMPARESONE SUPPLIER IN THE ONTOLOGYDelta Fasteners LtdSAP · LFA1 · 0000104471Delta Fasteners LimitedOracle · suppliers · 104471Delta FastenersSupplier portal · DF-1042The values themselvesnine digits on both sidesClose spellings“Ltd” beside “Limited”How much overlaps94% of 9,340 numbersSupplier · Delta Fasteners LtdSAP key 0000104471Oracle key 104471Portal key DF-1042one late rate: 7.4%showcase estate · the records stay in their systems; the link is held in the ontology
Three records, one supplier. The link holds all three keys, so one question reaches all three systems. Showcase estate.
94%
of supplier numbers matched between SAP and Oracle in the showcase estate
showcase estate
9,340
supplier records compared in one run
showcase estate
3
kinds of evidence: the values, close spellings, a cross-reference
product
One
supplier object, holding the key of each system that knows it
product
Where this sits

Stage 2 of six: map

Step by step

How two columns become one confirmed link

The values carry the evidence; your team carries the decision.

FROM TWO COLUMNS TO ONE CONFIRMED LINK01Pick the pairscolumns that could carrythe same thing02Compare the valuesthe values in each column,from the sample03Measure theoverlaphow many values appear onboth sides04Score and explaina share matched and thereason for it05Your team confirmsconfirm the link, or add across-referenceeach confirmed link becomes evidence for the next pair
The first three steps read the values Juno already holds in the knowledge index. The last belongs to your team, and its decision teaches the next pair.

Mapping told Juno what each column means. Linking answers a second question: when two systems both hold suppliers, are they the same suppliers. The evidence is in the values, and the knowledge index already holds a profile of every column.

Juno picks the pairs worth comparing: two columns mapped to the same ontology attribute, or two columns whose values follow the same shape. A ten-digit number column and a date column stay out of the comparison.

For each pair it compares the values themselves and counts how many appear on both sides. That count becomes the share matched: 94% of the 9,340 supplier numbers in the showcase estate appear in both systems.

The pair arrives on the review screen with the share matched, a sample of the values that agree and a sample of those that stay apart. Your team confirms the link, adjusts it or adds a cross-reference table for the codes that follow their own shape.

The evidence

Three ways two systems agree about one thing

Each pair carries its evidence onto the review screen, so a reviewer can judge it in seconds.

The same value on both sides

Nine digits in SAP and the same nine digits in Oracle, once the leading zeros are set aside. This is the strongest evidence, and it needs a few seconds to measure.

A close spelling

“Delta Fasteners Ltd” beside “Delta Fasteners Limited”. Juno measures how close two names are, and shows the pairs so a person can agree or disagree.

A cross-reference you hold

A portal code follows its own shape, so the link runs through a table your team maintains, or through a tax number both systems carry.

The comparison reads the sample of values kept in the knowledge index. The rows stay in the source systems. Product.

How much agrees

A share matched for every pair of columns

One number per pair tells your data owners where the estate agrees and where it needs work.

Columns comparedWhat Juno foundValues that agreeWhat your team did
SAP LFA1.LIFNR · Oracle suppliers.SupplierNumberThe same nine digits on both sides, with leading zeros in SAP94% of 9,340Confirmed as one supplier key
SAP LFA1.NAME1 · Portal VENDOR_NAMEThe same names with small spelling differences88% of 1,204Confirmed; 142 names reviewed by hand
SAP MARA.MATNR · Oracle item numberThe same material numbers on both sides99% of 412,880Confirmed as one material key
SAP plant code · Warehouse system siteA short code table joins the two100% of 14Confirmed against the site list
Portal VENDOR_ID · SAP LFA1.LIFNRA portal code with a shape of its own71% of 860A cross-reference table added by hand

Five pairs from the showcase estate. The share matched is the count of values that appear on both sides. Showcase estate.

The share matched is the number your data owners ask for first. A pair at 99% is a key both systems keep well. A pair at 71% says that most records link and that the rest need a route of their own, usually a cross-reference table or a correction in the source.

Records that stay apart are listed, with the system each one came from. Your team works through them, and each decision joins the evidence for the next run.

Linking makes a question whole: the late rate of Delta Fasteners counts the deliveries recorded in both ERPs and the confirmations on the portal, as one supplier.

Where a client wants one governed record for the supplier itself, with a stewarded golden record and a survivorship rule per field, Lima Axiom holds it and Juno reads it as another registered source.

The running example

Tuesday 14:05: one supplier, three keys, one late rate

Showcase estate.

The running example

The cancellation case needed the late rate of each supplier, and Delta Fasteners sat in three systems. SAP held 0000104471, the acquired division held 104471 in Oracle, and the portal held DF-1042 with the confirmed ship dates.

Juno compared the supplier columns at 14:05 and reported 94% of 9,340 numbers on both sides, with the portal code at 71%. P. Sharma confirmed the SAP and Oracle link, and uploaded a cross-reference table for the portal codes that afternoon. Delta Fasteners then carried one late rate, 7.4%, and the buyer rule that keeps allocation-bound lines could name the supplier once.

Next stage · Ask

ChatLima: ask your supply chain

With the estate registered, mapped and linked, a person can ask a question in plain language and see the working behind the answer.

Terms on this page
LinkingRecognising that two columns in two systems carry the same thing, such as one supplier.
Share matchedThe count of values that appear on both sides of a compared pair, as a percentage.
Close spellingTwo names that differ by a few characters, such as “Ltd” and “Limited”.
Cross-reference tableA list your team maintains that pairs a code in one system with a code in another.
Key columnThe column a system uses to identify a thing, such as a supplier number.
Golden recordOne governed record for a business thing, held and stewarded in Lima Axiom.
Questions
Does linking change our data?

The link is held in the ontology, beside the mapping. Each record stays in the system that holds it, with the key that system uses, and questions reach all of them through the link.

What about a supplier that appears in one system alone?

It stays as it is and is listed among the records that stay apart, with the system it came from. Your team decides whether it is a separate supplier or a record to correct.

How does this sit beside master data management?

Linking recognises that two records describe one thing, so a question can join them. Lima Axiom holds one governed record for the thing itself, with stewards and survivorship rules. Estates often run both.

How long does a comparison take?

It runs as a background task on the sample values in the knowledge index. Supplier and material columns in the showcase estate were compared in minutes, and the review took the rest of the afternoon.

In the platform

Where Juno sits among the four capabilities

Each one builds on the one before it.

One shared foundationCatalogLineageAccess policyWrite path

See Juno answer and act on your own data

Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.