Connectors Infor LN and M3 to Azure Synapse Analytics

Infor LN and M3 to Azure Synapse Analytics: full history landed and reconciled, then kept current.

Lima Backbone reads Infor LN and M3 through ION API gateway, types the data correctly on landing, writes it into Azure Synapse Analytics as dedicated sql pool schemas with hash distribution on the source keys, and keeps it current from the source’s changes. Every run ends with a row count and a control total per table.

OUT OF INFOR LN AND M3ItemsItem master · item warehouseBills of materialProduct structure BODsRoutingsRouting BODsStockInventory balance BODsLIMA BACKBONEExtractION API gateway · Business object docume…Checknine checks before anything loadsShapetypes, keys, deletes, partitionsLoadParquet to ADLS, COPY INTO staging, appl…INTO AZURE SYNAPSE ANALYTICSAzure Synapse AnalyticsDedicated SQL pool schemas with hash dis…
The path from Infor LN and M3 to Azure Synapse Analytics. Objects come out through the source's methods, are typed and checked, land in Azure Synapse Analytics and are kept current from the source's changes.
220M rows
615 tables · ~30 GB in ~30 min on 64 vCPU
performance estimate
80 GB/day
moved and transformed every day
production · semiconductor enterprise
8
checks on landing
product
1
count and control total per table per run
product
What Azure Synapse Analytics expects

The model the load has to fit.

ModelDedicated SQL pool schemas with hash distribution on the source keys; or Delta tables on ADLS.LoadParquet to ADLS, COPY INTO staging, apply by key; counts and control totals per table.BackResults can be written back to the ERP by Lima, confirmed per write.
The hardest part of this path

Choosing distribution keys so joins across SAP tables stay local.

The Azure Synapse Analytics connector page →

What comes out of Infor LN and M3

Objects and where they go.

The first load is assembled from these objects through ION API gateway. Change capture (BOD publications) keeps the daily volume small afterwards.

Planning objectSource objectsDestination in Azure Synapse Analytics
ItemsItem master · item warehouseraw schema → conformed schema (COPY INTO + apply)
Bills of materialProduct structure BODsraw schema → conformed schema (COPY INTO + apply)
RoutingsRouting BODsraw schema → conformed schema (COPY INTO + apply)
StockInventory balance BODsraw schema → conformed schema (COPY INTO + apply)
Open purchase ordersPurchase order BODsraw schema → conformed schema (COPY INTO + apply)
Open sales ordersSales order BODsraw schema → conformed schema (COPY INTO + apply)
Production ordersProduction order BODsraw schema → conformed schema (COPY INTO + apply)
ForecastsForecast BODsraw schema → conformed schema (COPY INTO + apply)
Customers and suppliersBusiness partner BODsraw schema → conformed schema (COPY INTO + apply)
CalendarsCalendar objectsraw schema → conformed schema (COPY INTO + apply)
The path, step by step

Six steps, one report at the end.

ConnectRegister Infor LN and M3 and Azure Synapse Analytics with credentials from the vault; test both connections.
ExtractFirst load through ION API gateway; then BOD publications.
CheckNine checks run before anything loads; a failed row becomes an exception with an owner and the load continues with the valid rows.
ShapeTypes are set from the source, keys kept complete, deletes and late changes applied in order.
LoadParquet to ADLS, COPY INTO staging, apply by key; counts and control totals per table.
Keep currentChanges from Infor LN and M3 are applied on the schedule you set; every run ends with the same report.
The checks that run before anything loads

8 checks, each with a plain example.

Every check either passes a row or turns it into an exception record with an owner. Nothing is dropped silently.

CheckKindWhat it catches, with an example
Types set from the sourcetypingSAP dates and times stored as text become dates and times; currency decimals shifted by the currency's rule
Keys complete and uniquekeysclient or organisation columns kept in the key; zero-padded keys preserved
Deletes appliedconsistencyrows deleted in the source are marked or removed in the copy
Late changes land in orderconsistencya change that arrives after a later one is applied by its source timestamp
Wide and cluster tables completecompletenessevery column of a wide table lands; cluster tables read through the released module
Partitions cover the rangecompletenessevery date partition present; gaps reported
Counts and control totals matchreconciliationrows and amounts per table compared between source and target
Schema changes noticeddrifta new or changed column is flagged before it breaks a downstream query
Cadence and offer

How the copy stays current, and how the work is priced.

After the first landing, Azure Synapse Analytics receives the source's changes: BOD publications. A migration month costs the same as a quiet month on the same tier.

Terms on this page

Plain meanings.

LandingWriting rows into the target's raw layer as they arrived, typed, before any business transformation.
Referential orderLoading parents before children so every row finds what it refers to.
Control totalThe sum of a key amount column compared between source and target, along with the row count.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Change captureReading only the rows that changed, from a log, change pointers or timestamps.
Questions

Asked about this path.

How long until the first load is live?

Days for the first tables; a full-history migration is sized by table count and volume, and read in partitions inside the run windows your administrators allow.

What does the data team see?

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.

Who runs it after go-live?

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.

Land your first tables in Azure Synapse Analytics.

One call scopes the dataset, the run window and the tier. The reconciliation report at the end is the acceptance test.