Order Management

Order Base Ship Unit

This page is accessed via:

  • Order Management > Purchase Order > Order Base. Click the Ship Unit tab. Click New Ship Unit.
  • Order Management > Purchase Order > Order Base Ship Unit.

The following properties impact validation:

Adding Order Base Ship Units

  1. The Order Base Ship Unit ID field identifies the ship unit that you are shipping. Enter a unique ID or leave the field blank to generate an ID based on the default Business Number Generator rule for ship unit ID.
  2. Released Count is the number of ship units that are released to date. The comparison of the value in this field to the value in the Ship Unit Count field determines the Ship Unit Release Status.
  3. Source and Destination Location fields identify where the freight is picked up and delivered. Oracle Transportation Management uses these fields to identify appropriate itineraries and service providers during shipment planning and optimization.
  4. Plan From/To Location fields let you override the default alternate location from which an order will be sourced/delivered for transportation planning purposes.
  5. If you want to stage your shipment in another location than your plan from location, enter a Buffer Location.
  6. Shippable controls whether the ship unit can be released. By default this check box is selected which means that when you save the order, the ship unit will be automatically released for the full amount (Number Ship Units) and an order release is created. Any time you edit/save the same ship unit again, the default state of the Shippable flag is off. Any ship unit that is not marked as shippable can be manually released using the Release Ship Units action on the Order Base or Order Base Ship Unit Manager.
    The property glog.webserver.obshipunit.defaultIsShippableToTrue indicates what the Shippable flag should be set to when adding an order base, creating an order base from a template, and when copying an order base. The default is true.

    Note: Release instructions for a ship unit are always based on quantity as defined in the Ship Unit Count field.

  7. Splittable By lets you designate if the ship units can be split based on bulk, count, or individual units. If you make no selection, the shipment will not be splittable. If you select count, this ship unit will be split using the ship unit count field. If you select individual, the order release may be split by placing individual ship units into multiple pieces of equipment, but the ship unit themselves are not splittable.
  8. Enter the Transport Handling Unit Count.
  9. Select a Transport Handling Unit to define what the item is shipped on, such as a pallet. Transport handling units are a type of ship unit specification.
  10. Select a Flexible Commodity Qualifier to describe the content of your order in terms of a specific classification.
  11. Enter a Commodity Code. The value that you enter in the Commodity Code field depends on the flexible commodity qualifier that you select.
  12. Enter the Net/Gross Weight and Volume (per Ship Unit) and choose a unit of measurement for each.
  13. Enter the Length, Width, Height, Diameter, and Core Diameter per Ship Unit.
  14. Declared Value (per Ship Unit) is for information purposes only and describes the value of the item in terms of a specific currency.
  15. Early and Late Pickup and Delivery dates can be used to constrain the time period during which the ship unit can be picked up and delivered. Oracle Transportation Management also uses these dates to determine whether multiple ship units can be bundled into one order release. The pickup and deliver dates for multiple ship units must overlap if you want to bundle them on one order release. The Early and Late Pickup/Delivery dates can also be used to set appointments.

    Note: When the Early Pickup field is populated and the Hold As Late As Possible constraint is true, Oracle Transportation Management will no longer allow shipments to plan in the past unless the Date Emphasis constraint is set to PAST.

  16. Enter Tags.
  17. Enter a Load Configuration Setup ID in the Load Configuration Setup field.
  18. Each order base ship unit has one internal status type that identifies the state of the ship unit from a releasing perspective. You can also create and assign external statuses to a ship unit.

Ship Unit Line

Use this section to describe the content of a ship unit in terms of the ship unit line items that are contained within the ship unit. The content of ship units are assumed to be for all of the ship units specified.

Release Instructions

This section of the page summarizes the existing release instructions that have been processed for the ship unit (if there are any).

Seal Numbers

  1. Enter the Ship Unit Seal with which the ship unit is associated for the order.
  2. Click Save for each seal number.

Equipment Reference Units

You can select Equipment Reference Units (ERU) to limit the number of specific units being loaded on a specific Equipment Group. If any ERU level information is provided on the ship unit, it overrides any defined on the ship unit specification.

Note:  You either need to enter Equipment Reference Units Per Ship Unit or Total Reference Units.  If you enter a value in the Equipment Reference Units Per Ship Unit, the value is multiplied by the Transport Handling Unit Count to determine the total reference units needed while planning the order release on a shipment.

  1. Enter an Equipment Reference Unit ID.
  2. Enter the number of reference units in the Equipment Reference Units Per Ship Unit field.
  3. Enter a value in the Total Reference Units field.
  4. Click Save for each equipment reference unit you enter.

Reference Numbers

Involved Parties

  • Use this section to assign contacts and/or locations as Involved Parties on the order.

Remarks

Accessorial and Special Services

Loading Split

If all your pallets are one height and there is not room for an additional pallet, splitting a pallet into halves or thirds may allow more space to be used.

This grid allows you to insert/update/delete possible loading splits during load configuration specified with split number, length, width, height, weight and volume. This grid is available only when the order base ship unit has a count of 1.

For a multi-leg scenario, loading split decisions are made for one leg (the first leg planned), and these initial loading split decisions are carried over for the same ship unit on different legs. The pallets that are split on the first planned leg (this could be any leg in the multi-leg itinerary) must be split and packed while planning the other legs of the itinerary and those which are not split on the first planned leg are never split on the legs that are planned subsequently in the same itinerary.

Related Topics