Lima Backbone reads Infor LN and M3 through ION API gateway, types the data correctly on landing, writes it into Snowflake as three schemas: raw (as arrived), conformed (current state by key) and history (every version), and keeps it current from the source’s changes. Every run ends with a row count and a control total per table.
Getting SAP and Oracle types right on landing: text dates and times, currency decimals, zero-padded keys and client or organisation columns.
The first load is assembled from these objects through ION API gateway. Change capture (BOD publications) keeps the daily volume small afterwards.
| Planning object | Source objects | Destination in Snowflake |
|---|---|---|
| Items | Item master · item warehouse | RAW table → CONFORMED table (MERGE) → HISTORY |
| Bills of material | Product structure BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Routings | Routing BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Stock | Inventory balance BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Open purchase orders | Purchase order BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Open sales orders | Sales order BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Production orders | Production order BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Forecasts | Forecast BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Customers and suppliers | Business partner BODs | RAW table → CONFORMED table (MERGE) → HISTORY |
| Calendars | Calendar objects | RAW table → CONFORMED table (MERGE) → HISTORY |
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 |
|---|---|---|
| Types set from the source | typing | SAP dates and times stored as text become dates and times; currency decimals shifted by the currency's rule |
| Keys complete and unique | keys | client or organisation columns kept in the key; zero-padded keys preserved |
| Deletes applied | consistency | rows deleted in the source are marked or removed in the copy |
| Late changes land in order | consistency | a change that arrives after a later one is applied by its source timestamp |
| Wide and cluster tables complete | completeness | every column of a wide table lands; cluster tables read through the released module |
| Partitions cover the range | completeness | every date partition present; gaps reported |
| Counts and control totals match | reconciliation | rows and amounts per table compared between source and target |
| Schema changes noticed | drift | a new or changed column is flagged before it breaks a downstream query |
After the first landing, Snowflake receives the source's changes: BOD publications. A migration month costs the same as a quiet month on the same tier.
The tables you name, landed in Snowflake with types set, keys complete and a count and control total per table, then kept current. Scoped in one call.
Offers and principles →Two weeks on your largest tables: terabytes moved, rows per minute, reconciliation variance and cost per terabyte against your current tool.
The offer →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.
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.
