Transport Management
Release: Transport Management – 27.0.9762.51570
Description
This release addresses a critical bug in the “Get Transport Request From Transfer Orders” function within the Transport Management extension. The fix corrects an incorrect code scoping issue in the MarkTransferLineMultipleAddress procedure of Codeunit 71925909 briTMS_TransportPlanningMgt. Previously, a validation check on the Receipt Date was applied unconditionally, preventing valid Transfer Order lines from being proposed when the Route Sequence option was disabled on the Transport Route. This correction ensures that Transport Order lines are now correctly marked for selection regardless of the Route Sequence setting, aligning the behavior with the equivalent functions handling Sales Lines and Purchase Lines.
User Stories
No User Story developed in this release.
Bugs
| Title | Description | Impact on previous version |
|---|---|---|
| [24549] – Bug in “Get Transport Request From Transfer Orders” Function | In the MarkTransferLineMultipleAddress procedure of Codeunit 71925909 briTMS_TransportPlanningMgt, only the Shipment Date check was guarded by the if TransportRoute."Route Sequence" then condition, while the Receipt Date check ran unconditionally. This caused valid Transfer Order lines to be incorrectly excluded from the transport request selection when Route Sequence was disabled. The fix encloses both the Shipment Date and Receipt Date checks within a single begin...end block scoped to the Route Sequence condition, so both checks are entirely skipped when Route Sequence is false. This aligns Transfer Order line handling with the existing Sales Line and Purchase Line logic. |
Breaking risk: Low. Users who relied on the previous (incorrect) filtering behavior when Route Sequence was disabled may notice that more Transfer Order lines are now correctly proposed. No migration or setup change is required. |
Events
No event added or updated in this release.