Logistics and warehouse on Oracle Fusion

Shipment exception and on-time recovery on Oracle Fusion Cloud

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.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Deliveries at riskS02 Delivery detailS03 Recovery optionsS04 Customer messageS05 Carrier portalS06 Boarddh_deliveryDeliveryShipping REST: shipmentLines · shipmentsdh_sales_order_lineSales order lineOrder Management REST:salesOrdersForOrderHub · linesdh_stock_positionStock positionInventory REST: inventoryOnhandBalances· inventoryItemLotsdh_production_orderProduction orderManufacturing REST: workOrdersdh_customer_masterCustomer masterReceivables REST:receivablesCustomerAccounts · TCApartiesWRITE BACK TO ORACLE FUSIONDelivery → PATCH shipmentLines · POST shipmentsSales order line → POST/PATCH salesOrdersForOrderHubrows stay in Oracle Fusion · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Oracle Fusion object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Oracle Fusion objects behind each handler

Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.

ObjectRead fromFields the app usesFreshness
DeliveryShipping REST: shipmentLines · shipmentsShippingMethod (route) · InitialShipDate (planned gi) · ActualShipDate (actual gi) · Shipment (number)live through the API
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesRequestedShipDate (requested date) · OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer)live through the API
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsItemNumber (material) · OrganizationCode (plant) · Subinventory (sloc) · OnhandQuantity (on hand)live through the API
Production orderManufacturing REST: workOrdersWorkOrderNumber (number) · ItemNumber (material) · PlannedStartQuantity (qty) · PlannedStartDate (start)live through the API
Customer masterReceivables REST: receivablesCustomerAccounts · TCA partiesAccountNumber (id) · PartyName (name) · Country (country) · BusinessUnit (sales org)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

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})
What the app writes back

Through released interfaces

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.

ObjectWhat changesInterface
Deliveryplanned goods issue, route or carrier changed; delivery split into a partial delivery through the delivery change interfacePATCH shipmentLines · POST shipments
Sales order lineconfirmed date and the customer's confirmation written as a note on the order linePOST/PATCH salesOrdersForOrderHub
Acknowledged and logged

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.

Access and prerequisites

What is in place before the first build

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.

  • An integration user with the REST resource roles for the objects the app reads and writes
  • BI Cloud Connector offerings enabled for the objects that need history at scale
  • Allowed IP or private connectivity to the pod
  • Business-unit and inventory-organisation scopes agreed with the process owner
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on Oracle E-Business Suite

The same app on Oracle E-Business Suite

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.

ObjectOn Oracle FusionOn Oracle E-Business Suite
DeliveryShipping REST: shipmentLines · shipmentsWSH_NEW_DELIVERIES · WSH_DELIVERY_DETAILS
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL)
Stock positionInventory REST: inventoryOnhandBalances · inventoryItemLotsMTL_ONHAND_QUANTITIES_DETAIL (write: MTL_TRANSACTIONS_INTERFACE)
Production orderManufacturing REST: workOrdersWIP_DISCRETE_JOBS (write: WIP_JOB_SCHEDULE_INTERFACE)
Customer masterReceivables REST: receivablesCustomerAccounts · TCA partiesHZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL)
Nearby

This app on other systems, and other apps on Oracle Fusion

Shipment exception and on-time recovery on

Other apps on Oracle Fusion

Terms on this page

On time in fullA delivery that arrives on the customer's requested date with the full quantity; the board counts the share of deliveries that meet both.
Goods issueThe posting that records goods leaving the warehouse; the planned goods issue date is when it should happen.
Read in placeThe rows stay in Oracle Fusion; the handler sends the filter and the columns and Oracle Fusion returns the matching rows.
Questions

Does this app copy data out of Oracle Fusion?

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.

What does Oracle Fusion need to allow?

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.

Can I run it on Oracle E-Business Suite as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

See this app on your data

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.