Stop Confirmation Operation
Stop Confirmation can be used to confirm an individual pickup stop for a load. A pickup stop is one where at least one shipment leg will be picked up.
Transportation Manager will trigger Stop Confirmation for each pick-up stop, if necessary, when Load Confirmation is performed for a load. Also, Transportation Manager can be configured to automatically perform Load Confirmation once Stop Confirmation has been performed for all pickup stops for the load.
Establish eligibility to perform the operation
The Stop Confirmation operation will be disallowed if any of the following requirements cannot be satisfied:
- Stop Itinerary Sequence: The operation can only be performed for the first pickup stop on the load's itinerary (in ascending pickup sequence) where Stop Confirmation has not already been performed. If Stop Confirmation has already been performed for all pickup stops for the load, the Stop Confirmation operation cannot be performed.
- Trip Itinerary Sequence: If the load is attached to a trip, it is only possible to perform Stop Confirmation for the first unconfirmed pickup stop on the trip's itinerary. If some of the pickup stops for the first load on the trip's itinerary remain unconfirmed, Stop Confirmation cannot be performed for the pickup stops for the second load on the trip's itinerary.
Note: When RelaxPriorStopStatusChecks in Global Settings - List of Application Configuration Settings (Employee)is set to "T", the operation can be performed on any pickup stop irrespective of the pickup sequence.
Note: Stop Confirmation can be performed for the pickup stops for a load on a trip as long as stop confirmation has been performed for all pickup stops for earlier loads on the trip's itinerary. There is no requirement that the Load Confirmation operation (or "final" confirmation) be performed for one load on a trip before stop confirmation can be performed for the next load.
Note: When RelaxPriorStopStatusChecks in Global Settings - List of Application Configuration Settings (Employee)is set to "T", the operation can be performed on any pickup stop irrespective of the pickup sequence.
Trigger updates
The following updates will be performed, as required, when Stop Confirmation is triggered for a specific pickup stop for a load.
If Auto Confirm After Final Stop in the Global Settings is True and Stop Confirmation is performed for the final pickup stop on the load's itinerary, Load Confirmation will also be performed for the load. See Load Confirmation operation for update considerations for that operation.
Load
The following columns in the load table may be impacted:
- Operational Status: If the Operational Status of the load is currently Tender Accepted or Confirming:
The status will be advanced to In Transit.
- A row in the A/P operational transition table will be recorded to provide a permanent audit trail.
- If the status for the tender request is Tender Accepted, the status will be advanced to Completed.
- Shipped Date / Time: If Stop Confirmation is being reported for the first pickup stop for the load, the Shipped Date / Time will be updated using the Actual Shipping Date/Time supplied when triggering the Stop Confirmation operation.
- MBOL: If Stop Confirmation is being reported for the first pickup stop for the load, the MBOL number will be updated.
Note: When RelaxPriorStopStatusChecks in Global Settings - List of Application Configuration Settings (Employee)is set to "T", then the Shipped Date/Time will be updated with the Actual Shipping Date/Time supplied when triggering the Stop Confirmation operation for any pickup stop (the stop may not be the first pickup stop). The Shipped Date/Time will be overridden by the Actual Shipping Date/Time supplied when triggering the stop confirmation operation for the first pick up stop.
Note: When RelaxPriorStopStatusChecks in Global Settings - List of Application Configuration Settings (Employee)is set to "T", MBOL number will be updated when Stop Confirmation is reported for any pickup stop (may not be the first pickup stop).
Event Notification
If enabled, the Event Notification message LoadStopConfirmed will be generated for the stop that is confirmed.
Reference Numbers
When Stop Confirmation is performed for the first pickup stop for a load, a row will be created in the Reference Numbers table to capture the Master Bill of Lading Number for the load.
If Bill of Lading Numbers have been assigned for any of the shipment legs to be picked-up at the stop, a row will be created in the Reference Numbers table to capture each BOL.
Stop
The following columns in the stop table will be impacted for the stop that is confirmed:
- Confirmed: The Boolean flag that designates whether confirmation has been performed will be set to True.
- Confirmed Date/Time: The Confirmed Date/Time will be set using the Actual Shipping Date/Time supplied when triggering the Stop Confirmation operation.
Shipment
The following columns in the shipment table will be impacted for each shipment where a corresponding shipment leg is being loaded at the stop:
- Financial Status: If all other legs for the shipment have previously been confirmed, the Financial Status for the shipment will be advanced to Eligible.
- Number of Times Confirmed Counter: The counter in the shipment table which records the number of legs for the shipment that have moved through the confirmation process will be incremented by one.
- Operational Status: If the shipment Operational Status is not Picked Up or higher, the shipment will be advanced to this status.
Shipment Leg
The following column will be impacted for each shipment leg being loaded at the stop:
- Operational Status: The Operational Status will be advanced from Processed to In Transit. A row in the A/P operational transition table will be recorded to provide a permanent audit trail.
Proactive Monitoring Alerts
The Load Stop Confirmed monitoring situation will be generated, if enabled. This will be used to close Alerts for Pick-up Overdue and create Alerts for Late Pick-Up violation for the pickup stop, if applicable. The Monitoring Situation can also be used to trigger user-enabled Notification Alerts.
See Also