The Feasibility Codes are set when an internal OTM process affects a Shipment that has already been built.
Arguably, you may not want to allow processes that create infeasible shipments, but in case of this being an exception, a process may still be considered desirable for the benefits it otherwise brings.
The FEASIBLITY status indicates that the Equipment, Rate or Time on the Shipment has been impacted by a process and the Shipment has been made infeasible, and further workflow may not be possible before action is taken to resolve the infeasibility.
One example of when this is useful is in the agent action "Order Base - Mod - Edit Shipment". You want to allow Order Base updates and you want to propogate them through the Order Release Ship Unit and assess the impact on the related Shipment.
It can also be used to 'flex' constraints in the Order Release Manual Assign to Shipment action.
As per Help:
Quote:
The Feasibility Code displays the current feasibility state of the shipment. When a shipment is first planned it is assigned a feasibility code of FEASIBLE which means that it passed all the planning logic and main compatibility checks for rates, pick/delivery time, and equipment. However, a shipment can become infeasible as a result of data changes or planning actions such as recalculating costs or changes in service providers, stop sequence, etc. There are many cases when a shipment becomes infeasible; for example, if changes on the order ship unit causes increased activity time on the shipment so that it misses the delivery time window, or if the equipment becomes overloaded after new ship units are loaded. One of the following codes determines the feasibility status of the shipment: - Feasible
- Time Infeasible
- Equipment Infeasible
- Rate Infeasible
|