What's new in version 2604.0.0.0
Features
With the feature added in this release of the Aptean Beverage Logistics extension, Drink-IT Edition, the return control process tracks differences between expected and actual return quantities and assigns discrepancies to either the driver or the company. An assignment differences code configured per route defines how the system handles differences automatically. Based on the configuration, the system creates and posts item journal entries or sales invoices when the return control is concessed, eliminating manual follow-up postings. For more information, see Set up assignment differences and Handle differences in return control.
With the features added in this release of the Aptean Beverage Logistics extension, Drink-IT Edition, holiday and exceptional shipment date changes can be managed centrally using the new Route Shipment Date Exceptions setup page. Exceptions can be defined per route or narrowed down to an individual customer, and support AM/PM delivery splits on the same date using the Line No. field.
When the Apply Exceptions action runs, it:
- Processes only new or changed exception rows — rows already applied in a previous run are skipped automatically based on the Processed flag, which resets when a row is modified.
- Warns before applying if any unshipped sales orders may be affected by the date change.
- Updates the Call Date, Call Till Time, and Shipment Date field values on any linked ASM Call Entries, keeping the call planning calendar in sync without manual follow-up.
For more information, see Set up holiday delivery exceptions and Setting Up Logistic information for a customer.
With the features added in this release of the Aptean Beverage Logistics extension, Drink-IT Edition, a customer can be temporarily assigned to a different route for a defined period using the new Customer Route Overrides setup page. This covers scenarios such as a vehicle being out of service or a customer needing delivery on a different day around a holiday. The override route can be added alongside the customer's normal route, or it can replace the normal route entirely for the period — in which case existing customer shipment dates on the normal route are removed for that period and regenerated on the override route.
When the Apply Temporary Assignments action runs, it:
- Generates and updates customer shipment date entries for the override route for the specified date range.
- Deletes existing normal-route shipment date entries for the period when Replace Normal Route is enabled.
- Locks processed rows — a processed temporary assignment cannot be changed; a new record must be created to correct a mistake.
- Updates the Call Date, Call Till Time, and Shipment Date field values on any linked ASM Call Entries for the affected period, keeping the call planning calendar in sync.
For more information, see Setting Up Logistic information for a customer.
Enhancements/Modifications
With this release of the Aptean Beverage Logistics extension, Drink-IT Edition,
-
Changing the Route or Shipment Date field value on a Sales Order that has an existing Route Planning No. field value no longer silently recalculates or overwrites the shipment date. The same cut-off confirmation dialog used elsewhere is shown and requires explicit confirmation before the date is updated, regardless of whether the change came from the Route field or the Shipment Date field directly.
-
Changing the Route or Shipment Date field value on a Route Plan Request line on the Route Planning Worksheet page displays the same cut-off confirmation dialog used on sales orders instead of an unconditional error, when the new date does not match the route's scheduled day. The change is blocked when open warehouse activity lines exist for the linked sales order, matching the order's own restriction.
-
The system calculates a shipment date based on the source route's or route's shipment day when Customer Shipment Dates do not exist for a customer/route combination, instead of raising an error. This applies when creating or changing the route on sales, purchase, transfer, sales return, and purchase return documents.
-
Setting or changing the Requested Delivery Date or Shipping Time field value on a Sales Order header calculates the Shipment Date field value backward from the requested delivery date, using the nearest valid Customer Shipment Date on or before that calculated date. The new Shipment Date based on Req. Del. Date field on the Route page controls what happens when the route is changed afterward: a notification preserves the calculated shipment date when enabled, or a confirmation dialog offers to recalculate it via standard route logic when disabled.
-
The system does not display the cut-off time confirmation message when an order's route is updated by a non-interactive batch import from an external app.
UI/UX changes
The following UI/UX changes have been made in this release.
- The Assignment Differences page has been added.
- The Assignment Differences action has been added to the Logistics Setup page.
- The Route Settlement FastTab has been added to the Logistics Setup page.
- The Driver Difference Reason Code field has been added to the Logistics Setup page.
- The Company Difference Reason Code field has been added to the Logistics Setup page.
- The Diff. Item Journal Template field has been added to the Logistics Setup page.
- The Diff. Item Journal Batch field has been added to the Logistics Setup page.
- The Bill-to Customer No. field has been added to the Drivers page.
- The Bill-to Customer No. field has been added to the Shipping Agents page.
- The Assignment Differences field has been added to the Routes page.
- The Assignment Differences field has been added to the Route Planning Worksheet page.
- The Return Control Status field has been added to the Route Planning Worksheet page.
- The Difference For Driver field has been added to the Return Control page.
- The Difference For Company field has been added to the Return Control page.
- The Driver Diff. Settled field has been added to the Return Control page.
- The Company Diff. Settled field has been added to the Return Control page.
- The Route Shipment Date Exceptions setup page is now available, accessible from the Logistics setup menu.
- The Shipment Date based on Req. Del. Date field now appears on the Routes list page and Route Card page.
Resolved issues
The following issue has been resolved in this release.
| ID | Description |
|---|---|
| 350562 | The system fails to prevent changing the Shipment Day field value on a route that is included in a source route, and fails to prompt for confirmation before updating all routes in the source route when changing an existing Shipment Day field value. |
| 387388 | The system fails to lock the Shipping Agent Code and Service Code fields on multiple order route documents, fails to propagate shipping agent changes to the linked warehouse document, and incorrectly raises a status error when changing the shipping agent on a released sales order or sales return order. |
| 356430 | The system fails to delete a warehouse pick from a warehouse shipment, displaying the error "You cannot update to previous status for Status Code" when no logistic statuses are configured in the environment. |
| 393823 | The system fails to validate the Shipment Date field value against the Source Route's Shipment Day field value when the Route itself has no Shipment Day configured, silently accepting dates that don't match the Source Route's scheduled day instead of showing the cut-off confirmation dialog. |
| 396887 | The system fails to write the Shipping Agent Code and Shipping Agent Service Code from the Route Planning Worksheet back to the Sales Order or Sales Return Order header after batch posting for non-warehouse locations on a Multiple Order Route. As a result, the posted sales shipment also carries blank shipping agent information. |