Connectors Anaplan

Anaplan, loaded from your ERP on your planning calendar.

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.

ERPS AND EXECUTION SYSTEMSSAP ECC · S/4HANAreleased interfacesOracle EBS · Fusion · JDEdatabase reads · APIsOther ERPs and WMSAPIs · database readsLIMA BACKBONEExtractfull, then changes onlyCheckcompleteness · consistency · orderShape and loadinto Anaplan's model, on the calendarPLANNING APPLICATIONAnaplanLists (hierarchies), modules with line…THE APPROVED PLAN RETURNS TO THE ERP · EACH WRITE CONFIRMED
How Anaplan fits the six Backbone steps. It is a planning target: the ERP's data is shaped into its model and loaded on the calendar; the plan is read back for the ERP.
3
ways to load it
this connector
2
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima loads and reads back Anaplan

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
Integration API bulk importsRuns Anaplan import actions on files Lima uploads.Scheduled loads.
Export actionsRuns exports and reads the result files.Reading the plan back.
CloudWorks / Anaplan ConnectSchedules actions where the customer already uses them.Coexistence with existing integrations.
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
Listshierarchies of products, locations, customers
Modules and line itemsthe planning data at a grain
Time and versionsperiods and scenarios
PatternSupported
Full loadlist and module loads
Incrementaldelta files per import action
Change capture—
Streaming—
Write-back—
What Anaplan expects

The landing model, and the hardest part.

ModelLists (hierarchies), modules with line items at a grain, time and versions. A line item can only reference list members that exist.LoadLists first, then modules; member existence and grain checks before the load; counts per import action.BackExports are read back and written to the ERP, each write confirmed.
The hardest part, in one sentence

Keeping list members in step with ERP master data across many modules.

Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs Anaplan grants. The four steps are the same for every connector.

  • An Anaplan integration user with model access
  • Import and export actions defined in the model
  • Run window per cycle
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

Anaplan 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/sap-ecc-to-anaplan

SAP ECC to Anaplan

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

Open the pair page →
/connectors/sap-s4hana-to-anaplan

SAP S/4HANA to Anaplan

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

Open the pair page →
/connectors/oracle-ebs-to-anaplan

Oracle E-Business Suite to Anaplan

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

Open the pair page →
/connectors/oracle-fusion-cloud-erp-to-anaplan

Oracle Fusion Cloud ERP to Anaplan

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

Open the pair page →
/connectors/oracle-jd-edwards-to-anaplan

Oracle JD Edwards EnterpriseOne to Anaplan

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

Open the pair page →
/connectors/peoplesoft-to-anaplan

Oracle PeopleSoft to Anaplan

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

Open the pair page →
/connectors/microsoft-dynamics-365-to-anaplan

Microsoft Dynamics 365 Finance and Supply Chain 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-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/netsuite-to-anaplan

Oracle NetSuite to Anaplan

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

Open the pair page →
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.
Net changeA load that sends only what changed since the last load, in the order the target needs.
Questions

Asked about this connector.

Does Lima install anything in Anaplan?

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 Anaplan 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 Anaplan 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.