Logistics and warehouse on Oracle Fusion

Dock scheduling and carrier appointment on Oracle Fusion Cloud

Lets carriers book dock slots against inbound orders and dock capacity, checks trucks in at the gate, re-slots late arrivals and posts the goods receipt from the dock.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Carrier bookingS02 Dock calendarS03 Booking detailS04 Gate check-inS05 ReceivingS06 Boarddh_purchase_order_linePurchase order lineProcurement REST: purchaseOrders · lines· schedulesdh_deliveryDeliveryShipping REST: shipmentLines · shipmentsdh_goods_receiptGoods receiptReceiving REST:receivingReceiptTransactionsdh_supplier_masterSupplier masterProcurement REST: suppliers ·supplierSitesWRITE BACK TO ORACLE FUSIONGoods receipt → POST receivingReceiptRequestsPurchase order line → PATCH purchaseOrders (change order) · POST purchaseOrdersrows 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.
4
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
6 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
Purchase order lineProcurement REST: purchaseOrders · lines · schedulesPromisedDeliveryDate (confirmed date) · Quantity (qty) · ReceivedQuantity (schedules) (received qty) · OrderNumber (number)live through the API
DeliveryShipping REST: shipmentLines · shipmentsShipment (number) · Customer (customer) · InitialShipDate (planned gi) · ActualShipDate (actual gi)live through the API
Goods receiptReceiving REST: receivingReceiptTransactionsReceiptNumber (document) · DocumentNumber (po) · ItemNumber (material) · Quantity (qty)live through the API
Supplier masterProcurement REST: suppliers · supplierSitesSupplierNumber (id) · Supplier (name) · Country (country) · Status (block)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: An open order line with a supplier-confirmed date within the next 5 days, or an outbound delivery with a planned goods issue within 2 days; the carrier books a slot against it on the portal screen.

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
PromisedDeliveryDate <= today + 5 and ReceivedQuantity (schedules) < Quantity

# the same criterion in canonical fields
{po.confirmed_date} <= today + 5 and {po.received_qty} < {po.qty}
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
Goods receiptgoods receipt posted against the order line from the receiving screen, with counted quantity and batch; material document number storedPOST receivingReceiptRequests
Purchase order lineshipping notification confirmation with the booked arrival date added to the order linePATCH purchaseOrders (change order) · POST purchaseOrders
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 handlers4 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
Purchase order lineProcurement REST: purchaseOrders · lines · schedulesPO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL (write: PO_CHANGE_API1_S)
DeliveryShipping REST: shipmentLines · shipmentsWSH_NEW_DELIVERIES · WSH_DELIVERY_DETAILS
Goods receiptReceiving REST: receivingReceiptTransactionsRCV_SHIPMENT_HEADERS · RCV_TRANSACTIONS (write: RCV_TRANSACTIONS_INTERFACE)
Supplier masterProcurement REST: suppliers · supplierSitesAP_SUPPLIERS · AP_SUPPLIER_SITES_ALL (write: AP_SUPPLIERS_INT)
Nearby

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

Dock scheduling and carrier appointment on

Other apps on Oracle Fusion

Terms on this page

Dock slotA booked time window at one dock, sized by the pallets the dock handles per hour.
Goods receiptThe posting in the ERP that records the arrival of goods against an order line and adds them to stock.
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.