External Rating Engine RateWare from Southern Motor Carriers (SMC) can be used to compute rates for individual shipment details. See "SMC RateWare Integration"
Tracking Numbers can be captured for individual shipment details during Shipment Confirmation. Shipment detail Tracking Numbers can be auto-generated, or provided from an external source. See "Delivery schedule example".
A/P vouchers can be created at shipment detail level if appropriate data has been captured for each shipment detail (Shipment detail Tracking Number and Shipment detail Level Rating Results).
The Reference Number Search function in the Track and Trace module will allow shipment legs to be identified using a Shipment detail Tracking Number.
Under certain conditions, Transportation Manager will allow updates to be applied to shipment detail composition for shipments even after confirmation has been reported for one or more of the shipment's legs. One of the requirements for post-confirmation updates to be permitted is that none of the legs for the shipment can be attached to a manifest. Therefore, shipment legs with attached shipment leg details will never be eligible for post-confirmation updates.
Shipment leg detail information will not be created for shipment legs that are attached to a load.
The Track and Trace module will allow user to drill from the List of Shipment Legs to view shipment leg detail level information for the shipment leg. For shipment legs where individual Shipment detail Tracking Numbers were provided during Shipment Confirmation, the following operations are supported at shipment leg detail level:
The Operational Status for shipment leg shipment details will be one of the following:
These Event Notification messages can be triggered for activity at shipment leg detail level:
Also, a shipment leg detail structure is included, if applicable, when these Event Notification messages are generated for a shipment leg:
Operations performed for a shipment leg detail will directly impact the Operational Status at shipment leg detail level. Once an operation has been performed for all shipment leg details for a shipment leg, the Operational Status for the shipment leg will also be promoted. For example, once POD has been reported for all containers for a shipment leg, the Operational Status for the shipment leg will be advanced to POD. The Operational Status for the shipment leg in Track and Trace will be Partially Delivered or Partially POD when the event has been reported for some but not all of the associated shipment details. This mirrors the behavior Load Operational Status in Track and Trace where a load will be Partially Delivered when delivery has been reported for some but not all of the attached shipment legs and Partially POD when delivery has been reported for all attached legs but POD has only been supplied for some of these legs.
The Operational Status for shipments will be handled in the same way as just described for shipment legs when shipment leg detail tracking is enabled for the final leg on the shipment's itinerary.
If an operation is performed in Track and Trace at shipment leg level for a leg where shipment leg detail tracking is enabled, the Operational Status for any shipment leg detail that has not already reached the designated status will be affected. This is consistent with behavior when operations performed in Track and Trace at load or stop level cascade down to the related shipment legs where the event has not already been reported.
If the Status Verification for a carrier is "POD Required", any voucher created for the carrier at shipment leg detail level will be placed on System Hold until POD has been reported for the applicable shipment leg detail.
A user can modify the Shipment leg detail Tracking Number for a shipment leg shipment detail after Shipment Confirmation has been performed for the corresponding shipment leg; Shipment Leg Confirmation Reversal is not required. This operation is allowed provided the shipment leg detail is still in In Transit Operational Status and the voucher for the shipment leg detail or parent manifest, if it exists, is still in Eligible status. See Change Shipment Detail Tracking Number (Carrier).
When shipment detail tracking is enabled for a shipment leg, POD data will be captured at shipment leg detail level. If POD is reported at shipment leg level for a shipment leg with shipment leg details, default values for weight and quantities will be used.
Proactive Monitoring will track activity at shipment leg level even for legs where shipment leg detail level data has been provided. When applicable, the latest Delivery Date/Time or POD Date/Time for any of the shipment leg details for a shipment leg will be used to evaluate Late Delivery Violations.
Confirmation reversal is available only at shipment leg level. If a shipment leg undergoing reversal has shipment leg detail level data, the shipment leg is only eligible for reversal if each of the shipment leg details is in In Transit status. If any of the related shipment leg details have progressed beyond In Transit, the Return to In Transit operation must be performed at shipment leg or shipment leg detail level to reverse the Operational Statuses for the applicable entities.
Voucher Reversal is available only at manifest level. All shipment legs with shipment leg detail level information are attached to a manifest.
Rows are captured in the A/P operational transition table for each shipment leg detail level event for each status where the Generate Event flag has been enabled.
The Shipment History list for a shipment leg includes manifest, shipment leg and shipment leg detail level activity from the A/P operational transition table. For rows representing shipment leg detail level activity, columns provide visibility to both the internal Shipment Leg detail ID as well as the external Shipment leg detail Tracking Number. A version of the history list is also available at shipment leg detail level. When accessed from this perspective, the list includes all recorded events for the selected shipment leg detail, plus all shipment leg and manifest level activity not associated with any specific shipment leg detail.
Appointments cannot be defined for a shipment leg detail.