Connectors SAP ECC to SAP Integrated Business Planning

SAP ECC to SAP Integrated Business Planning: a first load in weeks, then net change on your planning calendar.

Lima Backbone reads planning data from SAP ECC through table reads through a released function module, shapes it into SAP Integrated Business Planning’s model, checks it, loads it inside the run window your planning calendar sets, and returns the approved plan to SAP ECC with each write confirmed. The first planning dataset is live in four weeks at a fixed price.

OUT OF SAP ECCItemsMARA · MARC · MARD · MBEWBills of materialSTKO · STPO · MAST · STASRoutings and production versionsPLKO · PLPO · MKALStock by status and dateMARD · MSKA · MSLB · MCHBLIMA BACKBONEExtractTable reads through a released function…Checknine checks before anything loadsShapeinto SAP's modelLoadCombinations derived, planning-level co…INTO SAP INTEGRATED BUSINESS PLANNINGSAP Integrated Business PlanningPlanning area → master data types → com…THE APPROVED PLAN RETURNS TO SAP ECC · EACH WRITE CONFIRMED
The path from SAP ECC to SAP Integrated Business Planning and back. Objects come out through the source's methods, pass nine checks, are shaped into the planning model and loaded on the calendar; the approved plan returns to SAP ECC.
8–10 wks
to a first full planning load
customer engagements · anonymised
4 wks
first planning dataset, fixed price
offer
2021
SAP to Kinaxis and back, in production since
production
9
checks before anything loads
product
Every write
confirmed by the ERP
product
What SAP Integrated Business Planning expects

The model the load has to fit.

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 of this path

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

The SAP Integrated Business Planning connector page →

What comes out of SAP ECC

Objects and where they go.

The first load is assembled from these objects through table reads through a released function module. Change capture (change pointers, table-level change capture, extractor deltas) keeps the daily volume small afterwards.

Planning objectSource objectsDestination in SAP Integrated Business Planning
ItemsMARA · MARC · MARD · MBEWProduct master data type
Bills of materialSTKO · STPO · MAST · STASProduction source and component ratio
Routings and production versionsPLKO · PLPO · MKALResource and production source
Stock by status and dateMARD · MSKA · MSLB · MCHBStock on hand key figure
Open purchase ordersEKKO · EKPO · EKET · EKBEOpen supply key figures
Open sales ordersVBAK · VBAP · VBEP · VBUPSales order key figures
Production ordersAFKO · AFPO · AFRUProduct master data type
Forecast and planned independent requirementsPBIM · PBEDStatistical forecast and consensus demand key figures
Customers and suppliersKNA1 · KNVV · LFA1 · LFM1Customer and supplier master data types
CalendarsTFACD · TFACS · T001WTime profile and planning calendars
How SAP ECC is read

Lima reads SAP through released interfaces: table reads through a named function module, BAPIs, CDS views where available, change pointers and extractor delta queues. It does not use the ODP RFC interface that SAP Note 3255746 restricts, it does not use RFC_READ_TABLE in production (SAP Note 382318), and it does not read the HANA database log (SAP Note 2971304). No add-on is installed in SAP.

The path, step by step

Six steps, one report at the end.

ConnectRegister SAP ECC and SAP Integrated Business Planning with credentials from the vault; test both connections.
ExtractFirst load through table reads through a released function module; then change pointers, table-level change capture, extractor deltas.
CheckNine checks run before anything loads; a failed row becomes an exception with an owner and the load continues with the valid rows.
ShapeObjects are mapped into SAP Integrated Business Planning's model: planning 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.
ReturnThe agreed plan returns to the ERP, each write confirmed.
The checks that run before anything loads

9 checks, each with a plain example.

Every check either passes a row or turns it into an exception record with an owner. Nothing is dropped silently.

CheckKindWhat it catches, with an example
Every item has a plant and a unit of measurecompletenessan item without a plant cannot be planned; the row is held with its owner
Every child finds its parentreferential ordera bill-of-material line whose item has not arrived is held until the item loads
Each way of supply has its own structureconsistencya production version without a routing or a bill is flagged
Open quantities are openconsistencyorder lines with delivered quantity equal to ordered quantity are excluded
Dates are inside the horizon and the calendarrangea due date on a non-working day is moved by the calendar rule and flagged
Units and currencies convertconsistencya component in a unit with no conversion to the base unit is held
Hierarchies are strictcompletenessno orphan members, no duplicate codes across ERPs
Weekly equals the sum of dailyconsistencygrain sums are checked for every measure
Counts and control totals matchreconciliationrows and quantities per table compared between source and target
Cadence and offer

How the copy stays current, and how the work is priced.

After the first load, SAP Integrated Business Planning receives net change on your planning calendar: change pointers, table-level change capture, extractor deltas. The plan returns to SAP ECC through BAPIs and IDocs, each write confirmed.

Terms on this page

Plain meanings.

Net changeA load that sends only what changed since the last load, in the order the target needs.
Referential orderLoading parents before children so every row finds what it refers to.
Control totalThe sum of a key amount column compared between source and target, along with the row count.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Write-backWriting a result into the system that owns it through its released interface; the response is the confirmation.
Questions

Asked about this path.

How long until the first load is live?

Four weeks for one planning dataset at a fixed price; recent programs reached a first full planning load in eight to ten weeks (customer engagements, anonymised).

What does the planning team see?

Counts per step, the check that stopped a row, the owner and the replay point, and the lineage of any number back to its source column.

Who runs it after go-live?

Your team, on the schedule you set, with the same report after every run; or your systems integrator; or Lima's team under the subscription.

Run your first SAP load.

One call scopes the dataset, the run window and the tier. The reconciliation report at the end is the acceptance test.