Connectors Oracle E-Business Suite to OMP

Oracle E-Business Suite to OMP: a first load in weeks, then net change on your planning calendar.

Lima Backbone reads planning data from Oracle E-Business Suite through partitioned JDBC reads, shapes it into OMP’s model, checks it, loads it inside the run window your planning calendar sets, and returns the approved plan to Oracle E-Business Suite with each write confirmed. The first planning dataset is live in four weeks at a fixed price.

OUT OF ORACLE E-BUSINESS SUITEItemsMTL_SYSTEM_ITEMS_B · MTL_ITEM_CATEGORIESBills of materialBOM_BILL_OF_MATERIALS · BOM_INVENTORY_C…RoutingsBOM_OPERATIONAL_ROUTINGS · BOM_OPERATIO…Stock by status and locatorMTL_ONHAND_QUANTITIES_DETAIL · MTL_MATE…LIMA BACKBONEExtractPartitioned JDBC reads · Incremental re…Checknine checks before anything loadsShapeinto OMP's modelLoadConversions checked for consistency, ch…INTO OMPOMPRecipes with co- and by-products, unit…THE APPROVED PLAN RETURNS TO ORACLE E-BUSINESS SUITE · EACH WRITE CONFIRMED
The path from Oracle E-Business Suite to OMP 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 E-Business Suite.
8–10 wks
to a first full planning load
customer engagements · anonymised
4 wks
first planning dataset, fixed price
offer
18 GB/day
changed rows from Oracle ERP across 2,891 tables
showcase estate
9
checks before anything loads
product
Every write
confirmed by the ERP
product
What OMP expects

The model the load has to fit.

ModelRecipes with co- and by-products, unit and density conversions, batch characteristics, changeover matrices, rates and tanks.LoadConversions checked for consistency, characteristics flattened and validated, matrices versioned in Lima, then loaded through the staging interfaces.BackThe plan returns to the ERP as process orders and transfers, each write confirmed.
The hardest part of this path

Getting yields and conversions right so planned quantities in OMP match what the plant can actually make.

The OMP connector page →

What comes out of Oracle E-Business Suite

Objects and where they go.

The first load is assembled from these objects through partitioned JDBC reads. Change capture (LogMiner where the DBA allows; otherwise last-update columns) keeps the daily volume small afterwards.

Planning objectSource objectsDestination in OMP
ItemsMTL_SYSTEM_ITEMS_B · MTL_ITEM_CATEGORIESProducts and packaging
Bills of materialBOM_BILL_OF_MATERIALS · BOM_INVENTORY_COMPONENTSRecipes with co- and by-products
RoutingsBOM_OPERATIONAL_ROUTINGS · BOM_OPERATION_SEQUENCESLines, rates and changeover matrices
Stock by status and locatorMTL_ONHAND_QUANTITIES_DETAIL · MTL_MATERIAL_STATUSESStock by location and batch
Open purchase ordersPO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALLPurchase supply
Open sales ordersOE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALLCustomer demand
Work ordersWIP_DISCRETE_JOBS · WIP_REQUIREMENT_OPERATIONSProcess orders
ForecastsMRP_FORECAST_DATES · MRP_FORECAST_DESIGNATORSForecast input
Customers and suppliersHZ_PARTIES · HZ_CUST_ACCOUNTS · AP_SUPPLIERSCustomers and suppliers
CalendarsBOM_CALENDARS · BOM_CALENDAR_DATESShift and line calendars
The path, step by step

Six steps, one report at the end.

ConnectRegister Oracle E-Business Suite and OMP with credentials from the vault; test both connections.
ExtractFirst load through partitioned JDBC reads; then LogMiner where the DBA allows; otherwise last-update columns.
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 OMP's model: recipes with co- and by-products, unit and density conversions, batch characteristics, changeover matrices, rates and tanks
LoadConversions checked for consistency, characteristics flattened and validated, matrices versioned in Lima, then loaded through the staging interfaces.
ReturnThe plan returns to the ERP as process orders and transfers, 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, OMP receives net change on your planning calendar: LogMiner where the DBA allows; otherwise last-update columns. The plan returns to Oracle E-Business Suite through open interface tables, public APIs; the import result 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 OMP load.

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