Connectors Oracle Fusion Cloud ERP to Kinaxis Maestro

Oracle Fusion Cloud ERP to Kinaxis Maestro: a first load in weeks, then net change on your planning calendar.

Lima Backbone reads planning data from Oracle Fusion Cloud ERP through BI Cloud Connector (BICC) extracts, shapes it into Kinaxis Maestro’s model, checks it, loads it inside the run window your planning calendar sets, and returns the approved plan to Oracle Fusion Cloud ERP with each write confirmed. The first planning dataset is live in four weeks at a fixed price.

OUT OF ORACLE FUSION CLOUD ERPItemsItem public view objectsItem structuresStructure and component view objectsWork definitionsManufacturing work definition objectsOn-hand quantitiesInventory balance view objectsLIMA BACKBONEExtractBI Cloud Connector · REST APIsChecknine checks before anything loadsShapeinto Kinaxis's modelLoadA full load first, then net change on t…INTO KINAXIS MAESTROKinaxis MaestroLinked tables: Part → PartSource → Bill…THE APPROVED PLAN RETURNS TO ORACLE FUSION CLOUD ERP · EACH WRITE CONFIRMED
The path from Oracle Fusion Cloud ERP to Kinaxis Maestro 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 Oracle Fusion Cloud ERP.
8–10 wks
to a first full planning load
customer engagements · anonymised
4 wks
first planning dataset, fixed price
offer
9
checks before anything loads
product
Every write
confirmed by the ERP
product
What Kinaxis Maestro expects

The model the load has to fit.

ModelLinked tables: Part → PartSource → BillOfMaterial, plus OnHand, ScheduledReceipt, IndependentDemand, Constraint, Calendar. Every child row must find its parent, so the load order is fixed.LoadA full load first, then net change on the planning calendar. Each table gets a count check and the referential check runs before anything loads.BackPlanned orders, allocations and reschedule recommendations are read from the plan and written to the ERP, each write confirmed.
The hardest part of this path

Turning ERP production versions, info records and source lists into one PartSource per way of supply, each with its own bill of material.

The Kinaxis Maestro connector page →

What comes out of Oracle Fusion Cloud ERP

Objects and where they go.

The first load is assembled from these objects through BI Cloud Connector (BICC) extracts. Change capture (no (SaaS; extracts and APIs)) keeps the daily volume small afterwards.

Planning objectSource objectsDestination in Kinaxis Maestro
ItemsItem public view objectsPart
Item structuresStructure and component view objectsBillOfMaterial (one per PartSource)
Work definitionsManufacturing work definition objectsPartSource (one per way of supply)
On-hand quantitiesInventory balance view objectsOnHand
Open purchase ordersPurchasing document view objectsScheduledReceipt
Open sales ordersOrder management fulfillment linesIndependentDemand
Work ordersManufacturing work order objectsScheduledReceipt (in-process supply)
Demand plansSupply chain planning extractsIndependentDemand (forecast) · HistoricalDemandActual
Suppliers and customersTrading partner objectsCustomer · Supplier
CalendarsSchedule and calendar objectsCalendar
The path, step by step

Six steps, one report at the end.

ConnectRegister Oracle Fusion Cloud ERP and Kinaxis Maestro with credentials from the vault; test both connections.
ExtractFirst load through BI Cloud Connector (BICC) extracts; then no (SaaS; extracts and APIs).
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 Kinaxis Maestro's model: linked tables: part → partsource → billofmaterial, plus onhand, scheduledreceipt, independentdemand, constraint, calendar
LoadA full load first, then net change on the planning calendar. Each table gets a count check and the referential check runs before anything loads.
ReturnPlanned orders, allocations and reschedule recommendations are read from the plan and written 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, Kinaxis Maestro receives net change on your planning calendar: no (SaaS; extracts and APIs). The plan returns to Oracle Fusion Cloud ERP through REST and FBDI; job status is the confirmation.

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 Kinaxis load.

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