Connectors SAP S/4HANA to o9 Solutions

SAP S/4HANA to o9 Solutions: a first load in weeks, then net change on your planning calendar.

Lima Backbone reads planning data from SAP S/4HANA through released CDS views, shapes it into o9 Solutions’s model, checks it, loads it inside the run window your planning calendar sets, and returns the approved plan to SAP S/4HANA with each write confirmed. The first planning dataset is live in four weeks at a fixed price.

OUT OF SAP S/4HANAItemsI_Product · MARA · MARCBills of materialSTKO · STPO · MASTRoutings and production versionsPLKO · PLPO · MKALStock by statusMATDOC · MARDLIMA BACKBONEExtractReleased CDS views · Table reads throug…Checknine checks before anything loadsShapeinto o9's modelLoadMembers first, then measuresINTO O9 SOLUTIONSo9 SolutionsA graph of dimensions with strict hiera…THE APPROVED PLAN RETURNS TO SAP S/4HANA · EACH WRITE CONFIRMED
The path from SAP S/4HANA to o9 Solutions 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 S/4HANA.
8–10 wks
to a first full planning load
customer engagements · anonymised
4 wks
first planning dataset, fixed price
offer
32 GB/day
changed rows across 4,218 tables; change feed 1m 48s behind
showcase estate
9
checks before anything loads
product
Every write
confirmed by the ERP
product
What o9 Solutions expects

The model the load has to fit.

ModelA graph of dimensions with strict hierarchies, measures stored at a grain, attributes and versions. Every member must exist before a measure references it.LoadMembers first, then measures; each hierarchy is checked for orphans and duplicates across ERPs, and each measure for grain sums, before the load.BackThe agreed forecast returns to the ERP as planned independent requirements, confirmed per write.
The hardest part of this path

Validating hierarchies built from several ERPs, where the same code means different things in each.

The o9 Solutions connector page →

What comes out of SAP S/4HANA

Objects and where they go.

The first load is assembled from these objects through released CDS views. Change capture (delta-enabled CDS views, change pointers, table-level change capture) keeps the daily volume small afterwards.

Planning objectSource objectsDestination in o9 Solutions
ItemsI_Product · MARA · MARCItem dimension and attributes
Bills of materialSTKO · STPO · MASTBOM measure at item–component grain
Routings and production versionsPLKO · PLPO · MKALResource and routing dimensions
Stock by statusMATDOC · MARDInventory measure at item–location grain
Open purchase ordersEKKO · EKPO · EKETOpen supply measure
Open sales ordersVBAK · VBAP · VBEPOpen orders measure
Production ordersAFKO · AFPOItem dimension and attributes
Planned independent requirementsPBIM · PBEDHistory and forecast measures
Customers and suppliersKNA1 · LFA1 · BUT000Customer and supplier dimensions with hierarchies
CalendarsTFACD · T001WTime dimension and calendars
How SAP S/4HANA is read

Released CDS views, table reads through a named function module, BAPIs, change pointers and extractor delta queues. No ODP RFC (SAP Note 3255746), no RFC_READ_TABLE in production (SAP Note 382318), no reading of 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 S/4HANA and o9 Solutions with credentials from the vault; test both connections.
ExtractFirst load through released CDS views; then delta-enabled CDS views, change pointers, table-level change capture.
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 o9 Solutions's model: a graph of dimensions with strict hierarchies, measures stored at a grain, attributes and versions
LoadMembers first, then measures; each hierarchy is checked for orphans and duplicates across ERPs, and each measure for grain sums, before the load.
ReturnThe agreed forecast returns to the ERP as planned independent requirements, confirmed per write.
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, o9 Solutions receives net change on your planning calendar: delta-enabled CDS views, change pointers, table-level change capture. The plan returns to SAP S/4HANA through BAPIs, IDocs and released OData APIs, 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 o9 load.

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