Dynamics 365 Finance and Supply Chain Management is Microsoft's cloud ERP. Lima reads its data entities through the Data Management Framework and OData, or through Synapse Link and the Dataverse where the estate uses them, and writes back through OData entities so that Dynamics applies its validation.
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 |
|---|---|---|
| Data Management Framework packages | Exports data entities as files on a schedule. | Bulk reads. |
| OData entities | Reads and writes entities with change tracking. | Deltas and write-back. |
| Synapse Link / Fabric link tables | Reads the exported tables where the estate has enabled them. | Near-real-time reads without load on the application. |
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 |
|---|---|
| Released products | items by legal entity |
| BOM versions and lines | bills of material |
| Routes and operations | routings |
| On-hand inventory | stock by warehouse and location |
| Purchase and sales orders | documents and lines |
| Vendors and customers | trading partners |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | entity change tracking; Synapse Link tables |
| Streaming | — |
| Write-back | OData entities; 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 Microsoft Dynamics 365 Finance and Supply Chain |
|---|---|
| Items | Released products V2 |
| Bills of material | BOM versions · BOM lines |
| Routings | Routes · Route operations |
| Stock | On-hand inventory entity |
| Open purchase orders | Purchase order headers and lines |
| Open sales orders | Sales order headers and lines |
| Production orders | Production orders and BOM lines |
| Forecasts | Demand forecast entries |
| Customers and suppliers | Customers V3 · Vendors V2 |
| Calendars | Working time calendars |
The prerequisites are what the team that runs Microsoft Dynamics 365 Finance and Supply Chain 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 Microsoft Dynamics 365 Finance and Supply Chain 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.