Transport Management
Release: Transport Management – 27.0.9642.61358
Description
This release introduces analytical dimension propagation across Transport Order Lines and Posted Landed Cost Assignments. When Transport Order Lines are created from source documents (Sales Orders, Purchase Orders, or Transfer Orders), the Dimension Set ID is now automatically copied from the originating source document line. Dimensions are preserved through the full lifecycle: from Transport Order creation, through posting, and into the Posted Landed Cost Assignment records. Users can also view and edit dimensions directly on Transport Order Line subforms and Posted Transport Order Line subforms via a new dedicated “Dimensions” action (Alt+D). This enhancement supports accurate cost analysis and allocation for logistics operations, particularly relevant for supply chain scenarios where landed cost traceability by dimension is critical.
User Stories
| Title | Description | Setup Instructions | Impact on previous version |
|---|---|---|---|
| [24008] – Populate Transport Order Lines and Posted Landed Cost Assignments with Analytical Dimensions | As a Transport Planner, dimension values from source document lines (Sales, Purchase, or Transfer) are now automatically copied to Transport Order Lines upon creation. Dimensions are then carried forward to Posted Transport Order Lines during posting, and propagated to Posted Landed Cost Assignments during landed cost generation. A new “Dimensions” action (Alt+D) is available on both Transport Order and Posted Transport Order subforms for viewing/editing dimension sets. Corresponding Transport Order Lines sharing the same source document automatically synchronize their Dimension Set ID on modification. | No specific setup required. Dimensions are automatically inherited from source document lines. The new “Dimensions” action is available in the Line action group on Transport Order and Posted Transport Order subforms. | New field added: “Dimension Set ID” (field 41) on tables briTMS_Transport Order Line (71925885) and briTMS_PostedTrnsportOrderLine (71925888). Codeunit briTMS_TOApplicationEntriesMgt (71925922) is now SingleInstance — any extension assuming a fresh instance per call may need review. No data migration required; existing records will have Dimension Set ID = 0. Low breaking risk overall. |
Bugs
No bug fixed in this release.
Events
No event added or updated in this release.