Finds stock with cover above a threshold or a long idle time, gives each position to its planner with the options, and posts the decision in the ERP.
Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | OnhandQuantity (on hand) · OnhandValue (costing extract) (value) · LastUpdateDate (last movement) · ItemNumber (material) | live through the API |
| Material master | Product Hub REST: itemsV2 | ItemNumber (id) · ItemDescription (desc) · ItemType (type) · OrganizationCode (plant) | live through the API |
| Forecast | Demand Management: forecast measures (REST / planning data extract) | ForecastQuantity (qty) · Item (material) · Organization (plant) · TimeBucket (period) | live through the API |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OrderedQuantity (qty) · OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) | live through the API |
| Batch | Inventory REST: inventoryItemLots | LotNumber (batch) · ItemNumber (material) · ExpirationDate (expiry) · OriginationDate (produced) | live through the API |
| Journal line | General Ledger REST: journals · BICC GL journal lines extract | JournalBatchName / JournalName (document) · AccountCombination (account) · EnteredDr − EnteredCr (amount) · Segment (cost center) (cost center) | live through the API |
In plain words: A stock position worth more than 5,000 whose on-hand quantity covers more than 12 months of forecast and open orders, or whose last movement is older than 180 days.
The criterion runs in Oracle Fusion through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.
# start criterion in Oracle Fusion fields OnhandValue (costing extract) > 5000 and (OnhandQuantity > 12 months of ForecastQuantity + OrderedQuantity or LastUpdateDate < today - 180) # the same criterion in canonical fields {stock.value} > 5000 and ({stock.on_hand} > 12 months of {forecast.qty} + {so.qty} or {stock.last_movement} < today - 180)
Writes use the same released REST resources (POST and PATCH) with the integration user's data-security profile. Each call returns the document identifier or an error message, and the app records both beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Stock position | transfer to another plant or scrap posted as a goods movement; quantity moved to blocked stock while a decision is open | POST inventoryTransactions (transfer, scrap, status) |
| Material master | plant status set to phase-out so planning stops creating new orders | POST/PATCH itemsV2 |
| Journal line | the agreed reserve change posted as a journal at month end | POST journals (ERP Integration Service, FBDI) |
Each write stores the identifier Oracle Fusion returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
Oracle roles and data-security policies are mapped to Lima access policies once. A buyer scoped to a business unit in Oracle sees the same rows in the app.
On Oracle E-Business Suite the same objects live in the tables named beside each row and are read in place through JDBC with a read-only user; writes go through the open interface tables and public APIs, run by a concurrent program.
| Object | On Oracle Fusion | On Oracle E-Business Suite |
|---|---|---|
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Material master | Product Hub REST: itemsV2 | MTL_SYSTEM_ITEMS_B (write: MTL_SYSTEM_ITEMS_INTERFACE) |
| Forecast | Demand Management: forecast measures (REST / planning data extract) | MRP_FORECAST_DATES · MRP_FORECAST_ITEMS (write: MRP_FORECAST_INTERFACE) |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL) |
| Batch | Inventory REST: inventoryItemLots | MTL_LOT_NUMBERS |
| Journal line | General Ledger REST: journals · BICC GL journal lines extract | GL_JE_HEADERS · GL_JE_LINES (write: GL_INTERFACE) |
The screens read through handlers that leave the rows in Oracle Fusion. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.
Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.