Shipment legs can be removed from a load using the Load Build, Load Processing, Load Confirmation modules, and Transportation Smartbench.
Using Load Build, the load with the applicable shipment leg must be attached to the user's current plan, which means that the load will be in Open status.
Using Load Processing or Load Confirmation, users can manually remove shipment legs from a load in Planned, Tendered, Tender Accepted, Tender Rejected, Confirming, or In Transit Operational Status when the Financial Status is Ineligible.
Using Smartbench, users can manually remove shipment legs from a load in Open, Planned, Tendered, Tender Accepted, Tender Rejected, Confirming, or In Transit Operational Status when the Financial Status is Ineligible. If a load in Open status is attached to a plan, then the user must be authorized to use this plan.
As with all operations that can be triggered from the Transportation Manager web UI or Smartbench, the administrator can determine which users, if any, should be authorized to remove shipments from loads from any of these modules.
Depending on system configuration, user may be prompted to provide a reason code when removing a shipment leg from a planned load via Load Processing, Load Confirmation, or Smartbench. Reason Codes will never be required when a shipment leg is removed via the Load Build module since the removal of a shipment leg from a load in Open status would be considered an expected action rather than an exception.
Validation
For a shipment leg to be eligible, it must meet the following requirements:
Shipment leg must currently be attached to a load.
Operational Status for the shipment leg must be Processed.
If shipment leg is being removed via Load Build, shipment leg and load must be attached to the current user's current load plan.
If shipment leg is being removed via Smartbench and it is attached to a plan, the user must be authorized to use this plan.
If shipment leg is being removed from a load that is not in Open status, if shipment leg is the first or last leg for a shipment (depending on Load MITCC Strategy), the corresponding shipment must not refer to a load Merge-in-Transit Consolidation Class (MITCC). (Note: The Remove Load MITCC operation can be used to eliminate load MITCC requirements for the shipment leg, if applicable.)
For a load in Planned, Tendered, Tender Accepted, Tender Rejected, Confirming or In Transit Operational Status to be eligible to have a shipment leg removed for a load that is not in Open status, it must meet the following requirements:
If Operational Status for the load is In Transit, the Financial Status must be Ineligible.
If Operational Status for the load is Confirming or In Transit and the Confirmed By User ID is populated, the load's Confirming By User ID must be equal to the ID for user making the request.
If Operational Status for the load is Confirming or In Transit, the selected shipment leg cannot be the only shipment leg assigned to the load (the last shipment leg cannot be removed).
Note: Unlike the rules governing the assignment of shipment legs to loads, there are no restrictions that will prevent a shipment leg from being removed from a load that is being re-planned (optimizer) or is engaged in the carrier sequential tendering process. Since removal of a shipment leg could be required based on a shipment update triggered from an external system even while the associated loads are undergoing re-planning or carrier sequential tendering, the Transportation Manager web UI and Smartbench also allows shipment legs to be removed when the corresponding load is engaged in either of these processes.
Updates
When both load and shipment leg meet validation requirements listed above:
Shipment leg will be removed from the load.
Stops for the load will be eliminated if the applicable shipment leg was the only shipment leg being picked or dropped at a location and both of the following are true:
Existing routing/rating/scheduling (RR&S) results on the load will be destroyed.
Load will be suspended if any of the load suspension tolerances are violated.
If the last shipment leg is removed when the Operational Status for the load is Tendered or Tender Accepted, and the load does not represent pre-booked capacity, tender cancel will be triggered, the load will be returned to Open status and it will be suspended.
If the shipment leg that is removed eliminates the last remaining unconfirmed pick stop:
The Confirming By User ID for the load will be cleared.
If the "Auto Confirm After Final Stop" flag in the Global Settings is True, load confirmation for the load will be performed which will advance the Financial Status of the load to Voucher Pending.
If the last remaining undelivered stop is eliminated, the Operational Status for the load will be advanced from In Transit to Completed.
If any other leg for the parent shipment for the shipment leg that is being removed is currently attached to a load plan, the removed shipment leg will be assigned to the same plan.
Logging status transition for shipment leg will always be captured. Status transitions for the load will be generated if the load status is impacted.
If the shipment leg was removed from a load in Planned, Tendered, Tender Rejected, Tender Accepted, Confirming, Picked Up or In Transit Operational Status, the following events will be captured:
Monitoring Situations: Shipment Leg Removed from Planned Load, Load Impacted by Shipment Changed, Load Suspended.
Event Notification: The Shipment Leg Removed from Planned Load event will be triggered.
Auditing Scenarios: Load Suspended or Load Impacted by Shipment Change.
Note: Shipment Leg Removed from Planned Load will be a shipment leg level operation that may trigger load level background events. The Reason Code supplied by the user (if enabled) will be carried only to shipment leg level event data and messages. Secondary load level events generated by the operation will be assigned system-defined Reason Codes.
Note: If the Tender Cancel, Load Confirm or Set Load to Complete operations are triggered indirectly when the last shipment leg is removed from a load, the events associated with those operations will also be generated.