Infor LN and M3 are Infor's manufacturing and distribution ERPs. Lima reads them through the ION API gateway and the business object documents (BODs) that Infor publishes, and reads the database directly where the estate is on-premise and allows it. Write-back goes through ION APIs so Infor applies its rules.
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 |
|---|---|---|
| ION API gateway | Calls the REST APIs Infor exposes for each product. | Reads and write-back. |
| Business object documents (BODs) | Receives published XML documents for items, orders and inventory. | Change feeds. |
| Direct database reads (on-premise) | Reads tables over JDBC where allowed. | History and first loads. |
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 |
|---|---|
| Items and item-warehouse records | products and stocking points |
| Bills of material and routings | manufacturing structures |
| Purchase and sales orders | documents |
| Inventory balances | stock |
| Business partners | customers and suppliers |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | BOD publications |
| Streaming | — |
| Write-back | ION APIs; response is the confirmation |
A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.
| Planning object | Source objects in Infor LN and M3 |
|---|---|
| Items | Item master · item warehouse |
| Bills of material | Product structure BODs |
| Routings | Routing BODs |
| Stock | Inventory balance BODs |
| Open purchase orders | Purchase order BODs |
| Open sales orders | Sales order BODs |
| Production orders | Production order BODs |
| Forecasts | Forecast BODs |
| Customers and suppliers | Business partner BODs |
| Calendars | Calendar objects |
The prerequisites are what the team that runs Infor LN and M3 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 →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →3 more pair pages for Infor LN and M3 are listed in the directory.
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.