o9 plans on a graph of dimensions with strict hierarchies, measures stored at a grain, attributes and versions. Lima validates the hierarchies for orphans and duplicates, loads dimension members before measures, checks that daily measures sum to the weekly grain, and returns the agreed forecast to the ERP as planned independent requirements.
Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.
| Method | What it does | When it is used |
|---|---|---|
| File-based ingestion | Lands dimension and measure files in o9's ingestion location. | Bulk and scheduled loads. |
| REST APIs | Loads and reads measures and members. | Intraday updates; reading the plan back. |
The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.
| Object | Plain meaning |
|---|---|
| Dimensions and hierarchies | item, location, customer, time and their roll-ups |
| Measures at a grain | history, forecast, stock, open orders |
| Attributes | properties used in rules |
| Versions | the plan cycle being loaded |
| Pattern | Supported |
|---|---|
| Full load | foundation load |
| Incremental | member-first deltas per version |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Validating hierarchies built from several ERPs, where the same code means different things in each.
The prerequisites are what the team that runs o9 Solutions grants. The four steps are the same for every connector.
Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →
Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.
Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.
Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.
A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.
Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.
A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.