Route and deviation table improvements

We continue to improve DAP, and lately we have focused on the tables route, f_complaint and f_deviation. We have now released the following:

Route Table

We have introduced a new column, terminal_id, in the Route Table to support all geographic structures.

Purpose:

• terminal_id serves as a reference to the lowest level of geography a route can be connected to, allowing users to define an optional grouping level between Areas and Routes.

Geographic Structures:

• Routes can be organized using one of the following structures:

  • Company → Region → Area → Route

  • Company → Region → Area → Terminal → Route

Deviation Table

The Deviation Table has undergone a comprehensive quality assurance process, resulting in significant improvements to data accuracy and usability.

Key Updates

• Improved Address Deviation Accuracy:

  • Enhanced integration ensures that address deviations previously filtered out incorrectly are now included.

  • Depending on local factors, companies may experience varying impacts: some will see a substantial increase in address deviations, while others will notice only minor adjustments.

• address_id Column Enhancements:

  • Previously, the address_id column was only populated for the deviation group AddressDeviation.

  • Based on user feedback, address_id is now also populated for deviations in the DeliveryDeviation group, simplifying the process of linking deviations to addresses and improving usability.

• Consistency in delivery_id for deliveries with SL prefix:

  • Inconsistencies in linking deliveries with SL prefixes in f_planneddelivery and f_deviation have been resolved.

  • The deviation table now includes deviations with both SL and L prefixes, facilitating easier joins between deviations and deliveries.

Important Notes for Users

• To prevent double-counting:

  • Filter out deviations with the L prefix if a deviation with the same deviation_id exists with an SL prefix.

• Current Limitation:

  • For deviations with an SL prefix, the address_id column is not yet populated. This will be addressed in a future update.

Delivery_id's with prefix SL is only applicable in Norway.