Sample Integration

(1) Item Master Synchronization

An item is sent into Transportation and Global Trade Management Cloud from Product Hub Cloud via OIC. GTM creates/updates the item. Sample integrations PIM_CREATE_GTM and PIM_UPDATE_GTM illustrate one example of how this could be done.

(2) Receive, Acknowledge and Process Compliance Screening for Sales Order Pre-Booking

An order is sent into Transportation and Global Trade Management Cloud from Order Management Cloud via OIC. GTM acknowledges the receipt of the request. GTM creates the transaction in GTM and performs the screening based on the services configured by the user. Once the compliance screening processing is complete, the system will build the compliance status response structure and send it to OIC. The FA domain has a sample agent, DOO-GTM - PRE-BOOKING listening to the transaction creation in pre-booking stage of sales order and sends the response to OIC. This sample agent is where the desired configuration can be added. Sample integration OM_GTM illustrates one way that the screening could be performed, and GTM_OM illustrates an example of the corresponding response.

(3) Receive, Acknowledge and Process Compliance Screening for Order Fulfillment Line

An order fulfillment line is sent into Transportation and Global Trade Management Cloud from Order Management Cloud via OIC. GTM acknowledges the receipt of the request. GTM creates/updates the trade transaction and performs the configured screening. Suggested screening services are Restricted Party List, Sanctioned Countries and Control Screening. The FA domain includes a sample agent, DOO-GTM - POST-BOOKING, which listens to the transaction creation/modification in post-booking stage of sales order and sends the response to OIC. Similar to (2) above, the OM_GTM and GTM_OM illustrate one way the screening and response might be accomplished.

(4) Receive, Acknowledge, and Process Order Fulfillment Line

Orders are sent to Transportation and Global Trade Management Cloud from Order Management Cloud (via OIC) and must be processed into an order that can be planned. This can be done using the PUBLIC ORDER RELEASE – INSERT agent or another agent. See the Order Management Guide for more information.

When an order is created in Transportation and Global Trade Management Cloud, an acknowledgment can be sent back to Order Management Cloud. The FA domain includes a SEND ORDER RECEIVED TO FA agent as an example. The Release interface is sent into OIC and its payload used to create the proper response to forward to Order Management Cloud. The OM_OTM integration illustrates one example of how the order release might be created, and OTM_OM illustrates one way the acknowledgment could be sent.

(5) Send Pickup and Delivery Dates Back to Order Management Cloud for Fulfillment Lines

Orders can be planned into shipments via an Automation Agent or a scheduled process to run the BuildBuySideShipments process based on a saved query selecting 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 Order Management Cloud. The sample flow assumes the following has been configured in Transportation and Global Trade Management Cloud:

Parameters RECALC ORDER EARLIEST EST PICKUP DATES and RECALC ORDER LATEST EST DELIVERY DATES are set to True in order to enable calculating these fields on the Order Release. The FA domain includes a Parameter Set FA_DEFAULT with these set.
Properties: glog.workflow.topic.OrderLatestEstDeliveryDateSync.suppresslifetime=false and glog.workflow.topic.OrderEarliestEstPickupDateSync.suppresslifetime=false. These properties should be added to the CUSTOM property included with Transportation and Global Trade Management Cloud.
Agent listening to ORDER - EARLIEST EST PICKUP DATE CHANGE and ORDER - LATEST EST DELIVERY DATE CHANGE (restrictions: INTERNAL) and send integration to OIC. The FA domain includes a SEND ORDER DATES TO FA to show one example on how this might be configured. Similar to the above, this sends the Release interface, which includes the estimated pickup and delivery dates.

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

(6) Sending Shipment Information to Inventory Management Cloud (Shipping)

When shipments are created in Transportation and Global Trade Management Cloud, the shipment information must be sent to Inventory Management Cloud (Shipping). The FA domain includes a SEND PLANNED SHIPMENT TO FA INV agent as an example of how this could be configured. The OTM_WSH integration illustrates one way the planned shipment might be mapped from Transportation and Global Trade Management Cloud to Inventory Management Cloud.

Note: At the time of this publishing, the mapping of Order Release Destination to Initial Destination (Release/ShipToLocationRef/LocationRef/LocationGid/Gid/Xid to ShipmentRequestOrderLine/InitialDestinationLocationId) may cause the transmission to fail as the locations received from Order Management are actually Party Site IDs, and Inventory Management expects a Location ID here. This is slated to be fixed in a future version. In the meantime, this mapping can be removed (may affect pick release in Inventory Management), or could be configured with a lookup table to translate Party Site ID to a Location ID.

(7) Receive, Acknowledge and Compliance Screening for Pick Confirm Shipment Line

A pick confirm shipment line is sent into Transportation and Global Trade Management Cloud from Inventory Management Cloud (Shipping) via OIC. GTM acknowledges the receipt of the request. GTM creates/updates the trade transaction and performs the screening configured by the user. Suggested screening services are Restricted Party List, Sanctioned Countries and Control Screening. The FA domain has a sample agent, WSH-GTM - READY-TO-SHIP listening to the transaction creation in ready-to-ship stage of shipment and sends the response to OIC. The WSH_SCREENING_GTM integration illustrates one example of how this screening might be performed, and the GTM_SCREENING_WSH integration illustrates an example of the corresponding response.

(8) Receive, Acknowledge and Compliance Screening for Ship Confirm Customer Shipment

A Ship Confirm Customer Shipment is sent into Transportation and Global Trade Management Cloud from Inventory Management Cloud (Shipping) via OIC. GTM acknowledges the receipt of the request. GTM creates the trade transaction and performs the screening configured by the user. Suggested screening service is Documents Determination. GTM does not send back any screening results to Inventory Management Cloud. The FA domain has a sample agent, WSH-GTM - SHIPMENT-ADVICE listening to the transaction creation related to shipment advice where appropriate actions to generate documents can be added. The WSH_SA_GTM integration illustrates one example of how this might be accomplished.

(9) Receive Shipment Actual

The shipment as it was actually shipped in Inventory Management Cloud is sent into Oracle Transportation and Global Trade Management Cloud. These are sent as individual ship units updating the shipment. The WSH_OTM integration illustrates one example of how actual updates might be mapped from Inventory Management Cloud into Oracle Transportation and Global Trade Management Cloud.

The ship units sent from Inventory Management Cloud may differ significantly from those that were originally planned by Transportation and Global Trade Management Cloud. Ship units sent from Inventory Management Cloud will have a Received Ship Unit Count = 1. When all actual updates have been sent, Inventory Management Cloud will send an update setting “Attribute 20” to ‘Y’ to indicate all actuals have been sent. The FA domain includes a sample agent SHIPMENT COMPLETE which listens for shipment modification events, and if the shipment is “complete” (Attribute 20=’Y’), the WSH_SHIP_COMPLETE_OTM integration will be called. This integration immediately calls back into Transportation and Global Trade Management Cloud with a transmission that deletes all of the original planned ship units, leaving only the actual ones sent from Inventory management Cloud.

(10) Send POD to Order Management Cloud for Fulfillment Lines

When all shipments for an order have been delivered, notification of delivery can be sent back to Order Management Cloud. Agent action SET ORDER DELIVERED STATUS can be used to evaluate the ENROUTE status of the related shipment(s) and set the order release DELIVERED status. The FA domain includes a SHIPMENT DELIVERED agent to illustrate how this might be configured. This agent listens for shipment status ENROUTE to move to COMPLETED, and uses Data Type Association SHIPMENT TO ORDER RELEASE to call SET ORDER DELIEVERED STATUS and set the order’s DELIVERED status. Another sample agent, SEND ORDER DELIVERY STATUS TO FA has been included in the FA domain which shows an example of how an agent might be configured to send the order to Order Management Cloud when the order’s status moves to DELIVERED. The OTM_OM integration illustrates one example of how the proof of delivery might be communicated from Transportation and Global Trade Management Cloud to Order Management Cloud.