OMP plans process industries. Its model needs recipes with co-products and by-products, density and unit conversions, batch characteristics flattened from the ERP's classification tables, changeover matrices, rates and tank capacities. Lima builds these from SAP or Oracle, keeps the changeover matrices as governed master data, loads through OMP's staging 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 interfaces | Loads OMP's staging tables and triggers the import. | First and net-change loads. |
| Plan reads | Reads the production and distribution 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 |
|---|---|
| Recipes | with co-products and by-products |
| Unit and density conversions | the arithmetic of process quantities |
| Batch characteristics | flattened from classification |
| Changeover matrices | governed master data kept in Lima |
| Rates and tanks | capacity |
| Pattern | Supported |
|---|---|
| Full load | first load |
| Incremental | net change |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Getting yields and conversions right so planned quantities in OMP match what the plant can actually make.
The prerequisites are what the team that runs OMP 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 →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.
