Connectors SAP Integrated Business Planning

SAP Integrated Business Planning, loaded from your ERP on your planning calendar.

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.

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 SAP's model, on the calendarPLANNING APPLICATIONSAP Integrated Business PlanningPlanning area → master data types → com…THE APPROVED PLAN RETURNS TO THE ERP · EACH WRITE CONFIRMED
How SAP Integrated Business Planning 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 SAP Integrated Business Planning

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
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 APIsReads and writes key figures.Reading the plan back; small updates.
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
Master data typesproduct, location, customer
Compound master dataproduct–location, product–customer combinations
Key figuresquantities and values at a planning level
Time profile and versionthe grain and the plan cycle
PatternSupported
Full loadinitial load per planning area
Incrementaldeltas per cycle
Change capture—
Streaming—
Write-back—
What SAP Integrated Business Planning expects

The landing model, and the hardest part.

ModelPlanning area → master data types → compound master data → key figures at a planning level, in a time profile and version.LoadCombinations derived, planning-level completeness checked, weekly values checked against daily sums, then loaded through the area's channel.BackThe agreed plan returns to the ERP, each write confirmed.
The hardest part, in one sentence

Keeping every key figure complete at the planning level for combinations that exist in one ERP and not another.

Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs SAP Integrated Business Planning grants. The four steps are the same for every connector.

  • The planning area's channel (CI-DS, RTI or OData) and its user
  • Planning-level definitions from the IBP configuration
  • Cycle calendar
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

SAP Integrated Business Planning 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-sap-ibp

SAP ECC to SAP Integrated Business Planning

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-sap-ibp

SAP S/4HANA to SAP Integrated Business Planning

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-sap-ibp

Oracle E-Business Suite to SAP Integrated Business Planning

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-sap-ibp

Oracle Fusion Cloud ERP to SAP Integrated Business Planning

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-sap-ibp

Oracle JD Edwards EnterpriseOne to SAP Integrated Business Planning

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

Open the pair page →
/connectors/peoplesoft-to-sap-ibp

Oracle PeopleSoft to SAP Integrated Business Planning

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-sap-ibp

Microsoft Dynamics 365 Finance and Supply Chain to SAP Integrated Business Planning

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-sap-ibp

Infor LN and M3 to SAP Integrated Business Planning

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

Open the pair page →
/connectors/netsuite-to-sap-ibp

Oracle NetSuite to SAP Integrated Business Planning

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

Open the pair page →
/connectors/sap-ewm-to-sap-ibp

SAP Extended Warehouse Management to SAP Integrated Business Planning

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

Open the pair page →
Status and evidence

Stated plainly, with dates.

When SAP's own integration is enough: stated on the SAP IBP solution 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 SAP Integrated Business Planning?

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 SAP Integrated Business Planning 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 SAP Integrated Business Planning 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.