Finds deliveries that will miss the customer's requested date, shows the cause, offers expedite, split or a new date, and records the customer's confirmation on the order.
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 |
|---|---|---|---|
| Delivery | Shipping REST: shipmentLines · shipments | ShippingMethod (route) · InitialShipDate (planned gi) · ActualShipDate (actual gi) · Shipment (number) | live through the API |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | RequestedShipDate (requested date) · OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) | live through the API |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | ItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand) | live through the API |
| Production order | Manufacturing REST: workOrders | WorkOrderNumber (number) · ItemNumber (material) · PlannedStartQuantity (qty) · PlannedStartDate (start) | live through the API |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | AccountNumber (id) · PartyName (name) · Country (country) · BusinessUnit (sales org) | live through the API |
In plain words: An open delivery whose planned goods issue date has passed with actual goods issue empty, or whose planned goods issue plus the transit days of the route falls after the requested date on the order line.
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 ActualShipDate = '' and (InitialShipDate < today or InitialShipDate + route_days(ShippingMethod) > RequestedShipDate) # the same criterion in canonical fields {delivery.actual_gi} = '' and ({delivery.planned_gi} < today or {delivery.planned_gi} + route_days({delivery.route}) > {so.requested_date})
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 |
|---|---|---|
| Delivery | planned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interface | PATCH shipmentLines · POST shipments |
| Sales order line | confirmed date and the customer's confirmation written as a note on the order line | 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 |
|---|---|---|
| Delivery | Shipping REST: shipmentLines · shipments | WSH_NEW_DELIVERIES · WSH_DELIVERY_DETAILS |
| 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) |
| Stock position | Inventory REST: inventoryOnhandBalances · inventoryItemLots | MTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE) |
| Production order | Manufacturing REST: workOrders | WIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_INTERFACE) |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | HZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL) |
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.