Source systems change: a release adds a column, a table is renamed, an extract stops carrying a field.
The scan finds the difference; your team decides what it means.
Registration recorded the description of every table: the names, the data types, the keys, the row counts and a sample of values. The sync scan reads the same description from the live source and compares the two, field by field.
Anything that differs becomes an item on a list. A new column, a renamed table, a data type that widened, a field the source stopped publishing, a value pattern that moved a long way from the sample.
Beside each item Juno names what depends on it: the confirmed mappings, the released agents and the saved questions that read that table or column. Your team sees the consequence before it decides.
Your team then adopts an item, holds it for a later decision, or replaces the field with another. Each adoption creates a new version of the data set and of its mapping, and the change joins the audit trail with the name of the person who made it.
Each row carries the source, the finding, the work that depends on it and one decision.
| Difference | Source | What the scan found | What depends on it | Decision |
|---|---|---|---|---|
| New column | SAP · EKPO | ZZ_CANCEL_REASON, four characters | a mapping proposal is ready | Adopt |
| New column | SAP · EKET | SUPPLIER_CONF_QTY, a quantity | a mapping proposal is ready | Adopt |
| New column | Oracle Fusion | cancellationWindowDays | a mapping proposal is ready | Adopt |
| Renamed table | SAP · release 2508 | ZCANCEL_WDW is ZCANCEL_WINDOW | 1 mapping · 2 agents · 3 questions | Carry across |
| Column gone | Planning suite | LEGACY_COVER_WKS left the extract | 1 mapping · 1 saved question | Replace |
Five differences from one overnight scan of five systems. Showcase estate.
The decision column is the only place a person is needed. Adopt takes the new field into the data set and sends it to mapping. Carry across moves a confirmed mapping to a renamed table. Replace points the mapping at another field. Hold leaves the item on the list with an owner and a date.
The dependency list turns a technical change into a business decision with a known consequence.
Three lines cover what a release, an upgrade or an extract change does to a registered data set.
| What changed | What the scan reports | What Juno proposes | What your team decides |
|---|---|---|---|
| Something new | A new column, a new table, or a new value pattern in an existing column | A mapping proposal with a confidence and a reason, ready for the review screen | Adopt it into the data set now, or hold it with an owner and a date |
| Something changed | A renamed table or column, a wider data type, a changed key, a value pattern that moved | Carrying the confirmed mapping across to the new name, with the evidence for it | Confirm the carry-across, or map the field again by hand |
| Something gone | A column or a table the source stopped publishing since the last scan | The list of mappings, agents and saved questions that read it | Point them at another field, retire them, or ask the source owner |
The scan compares the description, so a change in the meaning of values shows as a moved pattern. Product.
Showcase estate.
The showcase estate took an SAP release on Wednesday evening. It added a cancellation reason to the purchase order item table, added a confirmed quantity to the schedule line table, and renamed the custom cancellation window table. The Oracle division published a cancellation window of its own the same week.
The Thursday scan listed all five differences by 05:31. A. Novak confirmed the carry-across at 08:15 and adopted the three new columns, which went to the mapping review screen with proposals waiting. The planning suite extract had stopped carrying a legacy cover field, so the one question that used it was pointed at the mapped days-of-supply measure. The PO cancellation agent ran that morning on rule version 4, as released.
How Juno works out what each registered column means, with a confidence and a reason behind every proposal.
On the schedule your team sets for each source, and on demand when a release is planned. The showcase estate runs it at 05:30 each working day, so the list is ready before the first questions arrive.
It reads the description the source gives about itself: names, types, keys, counts and a sample of values. The rows stay in the source system, and the sample follows the access rights of the connection.
It keeps running on the rule version it was released with. A difference that touches a mapping the agent uses is shown on the agent, with the owner named, so the decision reaches the right person.
The named owner of the data set, usually the data lead, with the domain owner for a business field. Both names go on the new version, beside the date and the evidence.
Each one builds on the one before it.
Reads your rows in place.
Connect and move ↗One record per real thing.
Master and govern ↗Apps for every decision.
Operate and decide ↗Asks and acts, at your level.
Ask and act ↗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.
