Runs the daily shortage meeting on live projected stock: planning, sourcing, sales and the plant allocate scarce components to orders and write the decisions to 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 |
|---|---|---|---|
| Material master | Product Hub REST: itemsV2 | ItemNumber (id) · ItemDescription (desc) · ItemType (type) · OrganizationCode (plant) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | OnhandQuantity (on hand) · ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) | live through the API |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | Quantity (qty) · ReceivedQuantity (schedules) (received qty) · OrderNumber (number) · LineNumber (line) | live through the API |
| Production order | Manufacturing REST: workOrders | PlannedStartQuantity (qty) · WorkOrderNumber (number) · ItemNumber (material) · PlannedStartDate (start) | live through the API |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OrderedQuantity (qty) · OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) | live through the API |
| Bill of materials | Product Hub REST: itemStructures · components | ItemNumber (parent) · ComponentItemNumber (component) · Quantity (qty) · StartDate (valid from) | live through the API |
In plain words: Each working day at 07:00 the app projects stock for every component on the critical list; a component whose projected stock falls below 0 within 4 weeks is on that day's agenda.
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 OnhandQuantity + (Quantity - ReceivedQuantity (schedules) due within 28 days) < demand from PlannedStartQuantity and OrderedQuantity within 28 days # the same criterion in canonical fields {stock.on_hand} + ({po.qty} - {po.received_qty} due within 28 days) < demand from {prod_order.qty} and {so.qty} within 28 days
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 |
|---|---|---|
| Production order | start and finish dates changed to the allocation | PATCH workOrders · POST operationTransactions |
| Purchase order line | pull-in date and quantity changed on the schedule line; premium buy added as a new line | PATCH purchaseOrders (change order) · POST purchaseOrders |
| Sales order line | confirmed quantity and date updated on the customer order | POST/PATCH salesOrdersForOrderHub |
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 |
|---|---|---|
| Material master | Product Hub REST: itemsV2 | MTL_SYSTEM_ITEMS_B (write: MTL_SYSTEM_ITEMS_INTERFACE) |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S) |
| Production order | Manufacturing REST: workOrders | WIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_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) |
| Bill of materials | Product Hub REST: itemStructures · components | BOM_STRUCTURES_B · BOM_COMPONENTS_B (write: BOM_BILL_OF_MTLS_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.
