Shipment Set Criteria

This page is accessed via:

• Sourcing > Historical Shipments > Shipment Set Criteria
• Cooperative Routing > Historical Shipments > Shipment Set Criteria

A shipment set represents a collection of shipments. It is common practice to export shipments from a remote Oracle Transportation Management system. However, you may directly upload shipments into the database using CSV files if your shipment data does not originate from an Oracle Transportation Management instance. Shipment sets are used to establish the shipments that will form the basis for the lanes to be built.

The Shipment Set Criteria page provides the ability to specify which shipments you want to pull from Oracle Transportation Management in terms of date range, equipment type, transportation mode, service provider, and region. If these criterion items are not sufficient for your needs, you have the additional option of specifying a saved query.

A shipment set contains no data until it is built using the Build Shipment Set action. Once the Build Shipment Set action is run, you can use the shipment search page to view the shipments that were added to the shipment set. To view sourcing shipments, go to Sourcing > Historical Shipments > Shipments.

Shipment sets are also used for Cooperative Routing.

Creating a Shipment Set Criteria

Note: If your saved query needs columns from a table other than the shipment table, the saved query must use a nested sub-query. For example, if you wanted to select only those shipments that had a particular shipment reference number, you would need a saved query of the form:

WHERE SHIPMENT.SHIPMENT_GID='DOMAINA.01000'

where exists (select 'X' from shipment_REFNUM where SHIPMENT_REFNUM_QUAL_GID = 'GLOG' and SHIPMENT_REFNUM_VALUE ='DOMAINA.01111' AND shipment_refnum.shipment_gid = shipment.shipment_gid)

where shipment.shipment_type_gid ='TRANSPORT' AND SHIPMENT.PERSPECTIVE='B' AND exists(select 'X' from shipment_status where shipment_status.status_type_gid = 'KRAFTWERK.ENROUTE' and shipment_status.status_value_gid ='DOMAINA.ENROUTE_ENROUTE' AND shipment_status.shipment_gid=shipment.shipment_gid)

You could not do the following because the shipment_refnum table is not in the from-clause of the underlying select statement. The following will fail where shipment_refnum.shipment_refnum_value = ‘whatever’.

1. Enter a Shipment Set ID.
2. Enter a Start and End Date.
3. Enter a Source Region.
4. Enter a Destination Region.
5. Enter a Service Provider Profile ID.
6. Enter a Saved Query ID.
7. Enter a Mode Profile ID.
8. Enter a Equipment Group Profile ID.
9. Select a Shipment Type from the drop-down list.
   
   The shipment type is important because it tells Oracle Transportation Sourcing whether to treat this shipment as a TL, Ocean or LTL shipment later in the sourcing process. This is particularly important when creating the lane summary since a lane summary for Ocean has different options than a lane summary for TL. For example, since you can create your own transport modes, Oracle Transportation Sourcing needs to map the user-created transport mode of Truck Load to the sourcing shipment type of TL.
10. If you selected a shipment type of ocean, indicate the Ocean Shipment Type by selecting one of the following:
    1. Arbitraries
    2. Port to Port
11. Enter an Equipment Reference Unit ID. Note: For a shipment to be considered in the ERU calculation, there must be an Equipment Reference Unit on the shipment.

Prevent Bad Lanes

Sourcing shipments can cover a wide variety of lanes which can be grouped into geography hierarchies. For a particular sourcing project, you will want to standardize the demand into a preferred geo-hierarchy. You can specify a desired geo hierarchy profile ID to eliminate bad lanes from being assigned to shipments. A bad lane is a lane that does not match the desired geo hierarchy profile.

When a shipment with a bad lane is copied into Oracle Transportation Sourcing, the system looks for an existing lane based on the ranking in the desired geo hierarchy profile and then associates the existing lane with the shipment. If no existing lane is found, then the system creates a new lane for the shipment based on the “best” source and destination geography specified on the lane summary.

In order to prevent bad lanes, both a shipment set criteria and a lane summary criteria must exist. The desired geo hierarchy profile specified on the shipment set criteria determines what existing lanes to reuse, while the desired source geo hierarchy and desired destination geo hierarchy specified on the lane summary criteria determine the geo-hierarchy of the newly created lane.

1. Enter a Desired Geo Hierarchy Profile ID.
2. Click Finished to save the shipment set criteria.