What's new in version 2602.2.0.0
Transport
•
Release Note
•
6/24/2026
•
Resolved issues
The following issues have been resolved in this release.
| ID | Description |
|---|---|
| 372336 | The system fails to populate the Location Code field on all Transport Orders created from the Transport Planning page when multiple lines with the same Shipping Agent and different Transport Route Codes are processed simultaneously. |
| 375180 | The system previously inherited the decimal precision in the Quantity per Transport Floor Space Type field on the Item-Transport Floor Space Type page from another setup. This issue arises when the inherited precision does not provide sufficient accuracy for quantity conversions. |
| 378643 | The system fails to retain the special characters entered in the Comments field on the Transport Order page. Additionally, the system replaces them with question marks (?) after the order is saved and reopened, without displaying an error message, resulting in corrupted text. |
| 377430 | The system fails to select the Changed checkbox on the related Transport Planning Lines page when the Promised Delivery Date field value is updated on a sales order. |
| 376739 | The system fails to return data from the Source Document Info action on the Transport Order subform for inbound requests. |
| 376751 | The system fails to correctly allocate the transport rate when multiple purchase orders are included in the same Transport Order. When the rate is configured as Lump Sum, the total amount is divided equally between orders without considering relevant criteria such as the number of pallets. |
| 377947 | The system fails to recalculate the Calculated Volume field value when executing the Update Weights action on a transport order, resulting in incorrect weight and volume values being displayed on the transport order. |