Anaplan is a connected-planning platform used for S&OP, financial planning and supply planning. Its model is lists (hierarchies), modules with line items, and time. Lima loads lists before modules through the bulk integration API, checks that list members exist before line items reference them, and reads exports back for write-back to the ERP.
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 |
|---|---|---|
| Integration API bulk imports | Runs Anaplan import actions on files Lima uploads. | Scheduled loads. |
| Export actions | Runs exports and reads the result files. | Reading the plan back. |
| CloudWorks / Anaplan Connect | Schedules actions where the customer already uses them. | Coexistence with existing integrations. |
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 |
|---|---|
| Lists | hierarchies of products, locations, customers |
| Modules and line items | the planning data at a grain |
| Time and versions | periods and scenarios |
| Pattern | Supported |
|---|---|
| Full load | list and module loads |
| Incremental | delta files per import action |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Keeping list members in step with ERP master data across many modules.
The prerequisites are what the team that runs Anaplan 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 →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 →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.