List of Loads Processed by the Optimization Request (Employee)

This page displays the list of loads that are impacted by an optimization request in any of the following ways:

• Created based on optimization
• Modified based on optimization
• Attached to a trip or booking
• Became unroutable during replanning

Note: This list excludes routable loads that are not modified during optimization.

Load data associated with the optimization request is retrieved from the load audit table. Data is available when the plan complete audit event is selected to retain data at load level.

The data displayed in the list depends on the load audit table, so the following scenarios are possible:

• Data may differ from the current values of the load
• The load may not exist anymore
• The load is not in a valid status

Any task triggered from this page (for example, rating, properties, or additional information) is performed on the actual load and fails if the load does not exist. There is a separate purge process for audit data, so the audit data associated with an optimization request can be purged before the request.

Note: If a load is attached to a trip (or a booking), the rating and rate shop operations trigger the corresponding trip (or booking) operation.

To view the failure reason for unroutable loads, perform any of the following:

• Routing Message Log (Customer/Employee)
• Optimization Request Message Log (Employee)

For information on icons and functionalities available on the list pages, see Web Interface lists.