Send Pickup and Delivery Dates Back to Oracle Fusion Cloud Order Management for Fulfillment Lines

In this use case, orders are planned into shipments through an automation agent or a scheduled process.

Description Integration Type Integration Options Notes

Orders can be planned into shipments through an automation agent or a scheduled process to run the BuildBuySideShipments process based on a saved query that selects the orders to be planned. The saved query might select orders with a new and unscheduled status. When an order is initially planned into a shipment, and as stop times are updated throughout its lifecycle, the estimated pickup and delivery dates can be updated on the order, if desired, to send back to Oracle Order Management.

Outbound

SOAP Services

Description	Integration Type	Integration Options	Notes
Orders can be planned into shipments through an automation agent or a scheduled process to run the BuildBuySideShipments process based on a saved query that selects the orders to be planned. The saved query might select orders with a new and unscheduled status. When an order is initially planned into a shipment, and as stop times are updated throughout its lifecycle, the estimated pickup and delivery dates can be updated on the order, if desired, to send back to Oracle Order Management.	Outbound	SOAP Services	The sample flow assumes the following has been configured in Oracle Transportation and Global Trade Management: Parameters RECALC ORDER EARLIEST EST PICKUP DATES and RECALC ORDER LATEST EST DELIVERY DATES are set to True to enable the calculation of these fields on the order release. The Oracle Fusion Cloud Applications domain includes a FA_DEFAULT parameter set with these settings: Properties: `glog.workflow.topic.OrderLatestEstDeliveryDateSync.suppresslifetime=false` and `glog.workflow.topic.OrderEarliestEstPickupDateSync.suppresslifetime=false`. These properties should be added to the CUSTOM property that's included with Oracle Transportation and Global Trade Management. An agent listening to ORDER - EARLIEST EST PICKUP DATE CHANGE and ORDER - LATEST EST DELIVERY DATE CHANGE (restrictions: INTERNAL) sends the integration to OIC. The Oracle Fusion Cloud Applications domain includes a SEND ORDER DATES TO FA, which is one example of how this might be configured. Similar to Receive, Acknowledge, and Process Order Fulfillment Line, this sends the Release interface, which includes the estimated pickup and delivery dates. The OTM_OM integration is one example of how the date estimates might be sent from Oracle Transportation and Global Trade Management back to Oracle Order Management.

The sample flow assumes the following has been configured in Oracle Transportation and Global Trade Management:

Parameters RECALC ORDER EARLIEST EST PICKUP DATES and RECALC ORDER LATEST EST DELIVERY DATES are set to True to enable the calculation of these fields on the order release. The Oracle Fusion Cloud Applications domain includes a FA_DEFAULT parameter set with these settings:
Properties: glog.workflow.topic.OrderLatestEstDeliveryDateSync.suppresslifetime=false and glog.workflow.topic.OrderEarliestEstPickupDateSync.suppresslifetime=false. These properties should be added to the CUSTOM property that's included with Oracle Transportation and Global Trade Management.
An agent listening to ORDER - EARLIEST EST PICKUP DATE CHANGE and ORDER - LATEST EST DELIVERY DATE CHANGE (restrictions: INTERNAL) sends the integration to OIC. The Oracle Fusion Cloud Applications domain includes a SEND ORDER DATES TO FA, which is one example of how this might be configured. Similar to Receive, Acknowledge, and Process Order Fulfillment Line, this sends the Release interface, which includes the estimated pickup and delivery dates.

The OTM_OM integration is one example of how the date estimates might be sent from Oracle Transportation and Global Trade Management back to Oracle Order Management.