Lima Backbone reads planning data from Oracle JD Edwards EnterpriseOne through partitioned JDBC reads, shapes it into OMP’s model, checks it, loads it inside the run window your planning calendar sets, and returns the approved plan to Oracle JD Edwards EnterpriseOne with each write confirmed. The first planning dataset is live in four weeks at a fixed price.
Getting yields and conversions right so planned quantities in OMP match what the plant can actually make.
The first load is assembled from these objects through partitioned JDBC reads. Change capture (by audit columns; database log capture where the DBA allows) keeps the daily volume small afterwards.
| Planning object | Source objects | Destination in OMP |
|---|---|---|
| Items | F4101 · F4102 | Products and packaging |
| Bills of material | F3002 | Recipes with co- and by-products |
| Routings | F3003 | Lines, rates and changeover matrices |
| Stock | F41021 | Stock by location and batch |
| Open purchase orders | F4311 · F4301 | Purchase supply |
| Open sales orders | F4211 · F4201 | Customer demand |
| Work orders | F4801 · F3111 | Process orders |
| Forecasts | F3460 | Forecast input |
| Customers and suppliers | F0101 · F03012 · F0401 | Customers and suppliers |
| Calendars | F0007 | Shift and line calendars |
Every check either passes a row or turns it into an exception record with an owner. Nothing is dropped silently.
| Check | Kind | What it catches, with an example |
|---|---|---|
| Every item has a plant and a unit of measure | completeness | an item without a plant cannot be planned; the row is held with its owner |
| Every child finds its parent | referential order | a bill-of-material line whose item has not arrived is held until the item loads |
| Each way of supply has its own structure | consistency | a production version without a routing or a bill is flagged |
| Open quantities are open | consistency | order lines with delivered quantity equal to ordered quantity are excluded |
| Dates are inside the horizon and the calendar | range | a due date on a non-working day is moved by the calendar rule and flagged |
| Units and currencies convert | consistency | a component in a unit with no conversion to the base unit is held |
| Hierarchies are strict | completeness | no orphan members, no duplicate codes across ERPs |
| Weekly equals the sum of daily | consistency | grain sums are checked for every measure |
| Counts and control totals match | reconciliation | rows and quantities per table compared between source and target |
After the first load, OMP receives net change on your planning calendar: by audit columns; database log capture where the DBA allows. The plan returns to Oracle JD Edwards EnterpriseOne through Orchestrator services and Z-file tables; confirmation read back.
Four weeks, fixed price. One planning dataset from Oracle JD Edwards EnterpriseOne into OMP, the nine checks, the run window on your calendar and a reconciliation report at the end. Your systems integrator can deliver it; so can Lima's team.
Offers and principles →Sized by the tier your estate needs. The whole platform is included; the price does not change with rows moved or questions asked.
How pricing works →Four weeks for one planning dataset at a fixed price; recent programs reached a first full planning load in eight to ten weeks (customer engagements, anonymised).
Counts per step, the check that stopped a row, the owner and the replay point, and the lineage of any number back to its source column.
Your team, on the schedule you set, with the same report after every run; or your systems integrator; or Lima's team under the subscription.
One call scopes the dataset, the run window and the tier. The reconciliation report at the end is the acceptance test.
