Troubleshooting Transportation Optimization errors

A new home for the Coupa Supply Chain documentation

Starting with Supply Chain 42, our documentation will be located on Coupa Compass. The help here will continue to be accessible for the foreseeable future, but will no longer be updated. If you need a Compass user account, contact your company’s Designated Support Contact (DSC).

You can access new and updated Supply Chain documentation in the following location on Compass:

https://compass.coupa.com/en-us/products/supply-chain-design-and-planning

Troubleshooting Transportation Optimization errors

When running Transportation Optimization, the solver will return errors based on incorrect input. For Transportation Optimization, the single quote character (') in site, customer, transportation asset or shipment Name values can cause issues when solving the model. If this character is detected, an error is displayed in the Run Log and you must remove the character from the input in order to solve the model.

In some cases, you may observe unrouted shipments, invalid shipments, or other unexpected results rather than an error from the solver. Information is provided with typical causes for these results.

The following table lists errors that can be returned when running Transportation Optimization and the possible causes of those errors:

Error or Condition	Possible Causes
There are fewer than two locations as required.	Sites or Customers are not included.
There is no valid shipment.	You may not have any quantities defined for your shipments. You do not have any shipments within the model horizon start date and end date.
There is no valid rate.	You have not defined a Rate record. Existing Rate records are specific for the wrong assets and/or locations.
There is no valid asset type.	Site in Asset Availability does not match Name in the Sites table. Asset in Asset Availability does not match the Name in the Transportation Assets table.
There is no valid asset availability.	You have not defined Asset Availability records. You have not defined an Available Units for the Asset Availability records.
There is no asset available for pool site “DC”.	You do not have assets defined at the required locations. Asset Availability dates are too restrictive.

The following table provides possible causes for unrouted shipments or other unexpected behavior:

Condition	Possible Causes
Unroutable Shipments	One or more shipments are unrouted based on the Asset constraints in place. Possible causes include: Insufficient assets in Asset Availability table. Asset Availability Start Date and End Date values that do not cover shipment pickup/delivery windows. Insufficient capacity/fill limits. Asset constraints, such as Max Total Distance Per Route and Max Time Per Route. Constraints, such as Max Duty Time Before Rest Time .
	Shipment-related causes include: Mode on Asset Availability that does not match Shipment Mode value. Shipment pickup or delivery windows that are too constraining.
	Business Hours-related causes include: Business Hours that prevent the shipment from being successfully picked up or delivered.
	Relationship Constraints-related causes include: Conflicting Relationship Constraints (for example, force a shipment onto an asset, but prevent the asset from visiting the customer).
Invalid Shipments: General Issues	Shipment-related causes include: Source Site or Destination Site is not a valid Site or Customer.
Invalid Shipments: General Issues	Baseline modeling-related causes include: Shipments with different sites have the same Route ID and the same Sequence. There is no Relationship Constraint that forces the Shipment onto a Transportation Asset.
Invalid Shipments: “Cannot stop at location Customer_xyz”	Violation of shipment time windows on the route. Travel time (either calculated or based on Transit Matrix records) conflicts with shipment time windows.
Invalid Shipments: “No asset type inclusion assigned”	There is no Shipment - Asset Force Relationship Constraint defined for the shipment.
Invalid Shipments: “Asset type inclusion conflict”	Conflicting Shipment - Asset Relationship Constraints records. For example, two shipments on the same Baseline route have Force Relationship Constraints on different assets.
Invalid Shipments: “Asset type assigned has insufficient capacity”	The total Quantity (or Weight, or Volume) on the route exceeds the capacity of the asset assigned with Relationship Constraints.
Invalid Shipments: “Asset type specified not available around the pool site”	Asset Availability is insufficient for the asset assigned with Relationship Constraints.
Invalid Shipments: “Pool Site location conflict”	When defining a Baseline route, not all shipments with the same assigned Route ID have the same origin for outbound routes or the same destination for inbound routes.
Far more shipments than expected	If you are using a Network Optimization model, you must first convert the optimized network using NO-TO Conversion model transformation.

Last modified: Wednesday May 15, 2024

Is this useful?

Yes No