SAP IBP plans on a planning area: master data types, compound master data and key figures stored at a planning level in a time profile and a version. Lima derives the product–customer and product–location combinations, checks planning-level completeness, loads through the channel the planning area uses and returns the agreed plan 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 |
|---|---|---|
| Cloud Integration for Data Services (CI-DS) | Batch loads of master data and key figures. | Scheduled loads. |
| Real-time integration (RTI / SDI) | Order-based data with lower lag. | Order-based planning areas. |
| OData APIs | Reads and writes key figures. | Reading the plan back; small updates. |
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 |
|---|---|
| Master data types | product, location, customer |
| Compound master data | product–location, product–customer combinations |
| Key figures | quantities and values at a planning level |
| Time profile and version | the grain and the plan cycle |
| Pattern | Supported |
|---|---|
| Full load | initial load per planning area |
| Incremental | deltas per cycle |
| Change capture | — |
| Streaming | — |
| Write-back | — |
Keeping every key figure complete at the planning level for combinations that exist in one ERP and not another.
The prerequisites are what the team that runs SAP Integrated Business Planning 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 →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.