Kinaxis Maestro (formerly RapidResponse) plans supply, demand and inventory on a model of linked tables: Part, PartSource, BillOfMaterial, OnHand, ScheduledReceipt, IndependentDemand, Constraint and Calendar. Lima builds those tables from the ERP, loads them in referential order through Maestro's integration interfaces, and reads planned orders back for write-back to SAP or Oracle. Lima has run this loop in production since 2021.
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 |
|---|---|---|
| Bulk data load | Loads full tables at the start and for reference data. | First load; calendars and constraints. |
| Net-change load | Loads only what changed since the last run, in referential order. | Nightly and intraday loads. |
| Plan extract | Reads planned orders, allocations and recommendations. | Write-back to the ERP. |
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 |
|---|---|
| Part · PartSource | planning items and every way to supply them |
| BillOfMaterial | components per PartSource |
| OnHand · ScheduledReceipt | stock and open supply |
| IndependentDemand · HistoricalDemandActual | orders, forecast and history |
| Constraint · Calendar | capacity and working time |
| Pattern | Supported |
|---|---|
| Full load | first load |
| Incremental | net change in referential order |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Turning ERP production versions, info records and source lists into one PartSource per way of supply, each with its own bill of material.
The prerequisites are what the team that runs Kinaxis Maestro 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 →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.
