Shipment Execution

Shipment execution is where you tender shipments and move shipments to their final destinations.

Tendering

When a shipment is tendered, notice is sent to a service provider with an offer to carry the shipment. For some shipments, Oracle Transportation Management automatically tenders the shipment for you; however, sometimes you must manually tender a shipment.

To be able to tender a shipment:

Your service provider must have a primary contact
Your shipment must have a LOGISTICS involved party.
The two contacts must have at least one shared communication method such as email.

Online Booking and Tendering

After you tender the shipment to a service provider, the service provider accepts or declines the tender. Service providers can respond to a tender by sending a transmission through the integration layer, by fax, by email, or by using On-line Booking and Tendering. See Configuring Online Booking and Tendering for details on setting this up.

Broadcast Tendering

Broadcast tendering is the process of finding a service provider to cover a "hot" load. The planner does not have the time to go through the normal tender process for such a load. This load is broadcast tendered to all service providers that accept broadcast tenders.

Spot Bid Tendering

Tender spot bidding is built around an auction or exchange model. The goal is to find the cheapest cost service provider to cover the shipments. The shipments are auctioned to all service providers that participate in spot bidding. There is a time limit for the various service providers to respond

Manual Tendering

Oracle Transportation Management supports tendering shipments to service providers who do not accept automated requests via email, fax, message center or EDI. This is called manual tendering.

Tracking Events

Tracking events support asset tracking and event management in OTM.

The tracking event is a rough equivalent to an EDI X12-214 message and describes:

Party responsible for the event which is stored in the Responsible Party list
What has happened which is stored in the Event Reason section and includes status group and status code
Why it happened which is stored in the Event Reason section and includes reason group and reason code
When it happened which is stored in the Event Info section and can include an event date/time and event time zone
Where it happened which is stored in the Event Location section and can include shipment ID, shipment stop number, location name, latitude/longitude, etc.

Service providers and other parties in your supply chain can send real world information about OTM business objects to OTM with a tracking event. A tracking event must be matched to an OTM business object. All matching is done by automation agent actions or it can be done automatically via a property. A tracking event can be linked to order bases, order releases, shipments, equipment, drivers, and power units.

Visibility

Visibility provides different ways to view data about your orders and shipments. You can view: