Blue Yonder's planning engines share SKU (item at a location) and DFU (demand forecasting unit) keys. Lima builds the DFU from a governed rule, produces one zero-filled demand history stream at the engine's bucket, aligns the buckets across engines, loads through Blue Yonder's ingestion interfaces and returns the plan to the ERP.
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 |
|---|---|---|
| Staging-table and platform ingestion | Loads the model tables through Blue Yonder's data ingestion interfaces. | First and net-change loads. |
| Plan reads | Reads recommendations and orders from the plan. | 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 |
|---|---|
| SKU | item at a location |
| DFU | demand forecasting unit: the key the forecast is built on |
| Demand history | one zero-filled stream per DFU |
| Supply and inventory | open supply and stock by SKU |
| Calendars and buckets | the time grain of each engine |
| Pattern | Supported |
|---|---|
| Full load | first load |
| Incremental | net change |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Building one DFU rule that holds across ERPs and keeping the history stream complete for every bucket.
The prerequisites are what the team that runs Blue Yonder Planning 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.
