DAP - updates for the complaint and deviations table

On Monday, December 9th, we will release updates to the DAP system, introducing significant improvements to the Complaint and Deviation tables.

Complaint Table Updates

New complaint_id Column

• A new column, complaint_id, has been added to the f_complaint table to simplify complaint identification.

• Purpose:

  • The complaint_id serves as a unique identifier for each complaint, enabling easier tracking and more efficient complaint management.

Improved delivery_id Population

• Previously, the delivery_id column was rarely populated. With this update, you will find this field more consistently populated.

• Important Notes for Users:

• If a customer has multiple deliveries of the same product on the same weekday and there is no external_delivery_id, any associated complaint will link to all these deliveries. This will result in duplicate rows with the same complaint_id but different delivery_id values.

  • Example: If there are two such deliveries, you will see two rows with the same complaint_id but distinct delivery_id values.

  • Complaints linked to deliveries without an external_delivery_id but where the delivery does have an external_delivery_id will not have the delivery_id populated.

• Deliveries older than three months, where the source data is no longer available, will also not have delivery_id populated.

• Purpose:

  • The delivery_id connects a complaint to a specific delivery, providing greater accuracy in tracking issues.

Deviation Table Updates

In our product news update from November 22nd, we addressed an issue where deviations with the prefix SL were missing the address_id.

This has now been resolved: deviations with the SL prefix will include the address_id, improving the completeness and reliability of the data.