Unitization Rule

This page is accessed via Operational Planning > Power Data > Planning > Unitization Rule.

When an order requires unitization (or containerization), unitization rules can be used to determine compatibility and the population of stuffing and de-stuffing locations on the container group that is created and assigned to the appropriate consol shipment as a result of the unitization process.

The unitization rule defines criteria that is compared to data on an order release to determine which rule should be used when an order is to be unitized (or containerized). Once a compatible unitization rule is selected, it also defines how stuffing and de-stuffing locations are populated on the container group that is created and assigned to a consol shipment.

The Unitization Condition Name is any text that you want to assign to the rule. This same field is available on the Order Release Other Attributes tab. Oracle Transportation Management compares the data on the order release to the data defined on rules to find a match. The Lane ID is also used as criteria for rule-matching by choosing a rule with the most specific lane match based on the order's source and destination location.

Use this section of the page to define how Oracle Transportation Management determines the stuffing and de-stuffing locations that are populated on the container group that is created and assigned to a consol shipment as a result of the unitization and order booking processes. These locations can also be defined directly on the order if you do not want the rule to control the assignment.

You can either choose one of the following Stuffing Location Types or enter the actual locations that you want to use.

• Origin/Destination - Oracle Transportation Management uses the Source or Destination location populated on the order release.
• Port of Load - Oracle Transportation Management uses the Port of Load location populated on the order release
• Port of Discharge - Oracle Transportation Management uses the Port of Discharge location populated on the order release.

Add a mode profile.

The Reference Code (any text) that you enter is automatically populated on any container group that is created as a result of the unitization process. This means, when Oracle Transportation Management stuffs an order into an existing container, the unitization rule used for this order must have the same Reference Code as the container group.