Finds purchase order lines that will arrive late, gives each to its buyer with the supplier's reply, and updates the order once a decision is made.
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 |
|---|---|---|---|
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | Quantity (qty) · ReceivedQuantity (schedules) (received qty) · RequestedDeliveryDate (delivery date) · OrderNumber (number) | live through the API |
| Supplier master | Procurement REST: suppliers · supplierSites | SupplierNumber (id) · Supplier (name) · Country (country) · Status (block) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand) | live through the API |
| Planned order | Supply Chain Planning REST: planningSupplies (planned orders) | OrderNumber (number) · Item (material) · Quantity (qty) · StartDate (start) | live through the API |
In plain words: An open order line whose delivery date is within 5 days, or has passed, and whose received quantity is below the ordered quantity.
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 RequestedDeliveryDate <= today + 5 and ReceivedQuantity (schedules) < Quantity # the same criterion in canonical fields {po.delivery_date} <= today + 5 and {po.received_qty} < {po.qty}
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 |
|---|---|---|
| Purchase order line | confirmed delivery date and quantity updated on the schedule line; note added | PATCH purchaseOrders (change order) · POST purchaseOrders |
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 |
|---|---|---|
| Purchase order line | Procurement REST: purchaseOrders · lines · schedules | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S) |
| Supplier master | Procurement REST: suppliers · supplierSites | AP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT) |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Planned order | Supply Chain Planning REST: planningSupplies (planned orders) | MRP_RECOMMENDATIONS · MRP_PLANNED_ORDERS |
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.
