Connectors Infor LN and M3

Infor LN and M3 data integration with Lima, in both directions.

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.

SOURCEInfor LN and M3ION API gateway · Business object docum…LIMA BACKBONEExtractfull · incremental · change captureCheckevery row valid, or an exception with a…Transform and load150+ operators · Python · loads on the…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · filesRESULTS RETURN TO INFOR LN AND M3 · EACH WRITE CONFIRMED
How Infor LN and M3 fits the six Backbone steps. It is a source and a target: data comes out through the methods below, and results go back in with confirmation.
3
ways to read or write it
this connector
4
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads and writes Infor LN and M3

Method by method.

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.

MethodWhat it doesWhen it is used
ION API gatewayCalls 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.
What it covers

Objects and patterns.

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.

ObjectPlain meaning
Items and item-warehouse recordsproducts and stocking points
Bills of material and routingsmanufacturing structures
Purchase and sales ordersdocuments
Inventory balancesstock
Business partnerscustomers and suppliers
PatternSupported
Full loadYes
IncrementalYes
Change captureBOD publications
Streaming—
Write-backION APIs; response is the confirmation
What a planning application needs from Infor LN and M3

The objects a first load is built from.

A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.

Planning objectSource objects in Infor LN and M3
ItemsItem master · item warehouse
Bills of materialProduct structure BODs
RoutingsRouting BODs
StockInventory balance BODs
Open purchase ordersPurchase order BODs
Open sales ordersSales order BODs
Production ordersProduction order BODs
ForecastsForecast BODs
Customers and suppliersBusiness partner BODs
CalendarsCalendar objects
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs Infor LN and M3 grants. The four steps are the same for every connector.

  • ION API credentials and the products' API suites enabled
  • BOD publishing configured for the change feeds
  • For on-premise: a read-only database user
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

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 →

Pair pages

Infor LN and M3 in a source-to-target path.

Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.

/connectors/infor-ln-m3-to-kinaxis-maestro

Infor LN and M3 to Kinaxis Maestro

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-o9

Infor LN and M3 to o9 Solutions

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-blue-yonder

Infor LN and M3 to Blue Yonder Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-sap-ibp

Infor LN and M3 to SAP Integrated Business Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-omp

Infor LN and M3 to OMP

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-anaplan

Infor LN and M3 to Anaplan

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/infor-ln-m3-to-snowflake

Infor LN and M3 to Snowflake

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-databricks

Infor LN and M3 to Databricks

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-microsoft-fabric

Infor LN and M3 to Microsoft Fabric

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-bigquery

Infor LN and M3 to Google BigQuery

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-amazon-redshift

Infor LN and M3 to Amazon Redshift

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/infor-ln-m3-to-azure-synapse

Infor LN and M3 to Azure Synapse Analytics

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.

Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Questions

Asked about this connector.

Does Lima install anything in Infor LN and M3?

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.

How is load on Infor LN and M3 kept in check?

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.

What do we see when a run finishes?

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.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try Infor LN and M3 on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.