Transportation network¶

The transportation network describes which flows are possible between locations. It brings together direct lanes, multi-stop routes, eligible materials, lead times, lots, capacities, fleets, and costs.

This page documents a logical family. Each part may have its own operation in the platform so lanes, costs, fleets, and routes can have independent validity and ownership.

Path in the platform¶

Data > Data Operations > Master Data > Network Structure > Transportation Network > Transportation network

Grain and key¶

Direct lane: one origin, one destination, and one network version.
Material rule: direct lane and material.
Route: an ordered sequence of locations.
Cost: lane, validity, and, where applicable, material, fleet, or vehicle type.

Required lane fields¶

Logical field	Meaning
`laneId`	Stable lane identifier
`originLocationId`	Origin location
`destinationLocationId`	Destination location
`networkVersionId`	Network version containing the lane

Optional lane fields¶

Logical field	Meaning	Default Value When Not Provided
`leadTime`	Time from shipment to availability at destination	No lead-time value
`distance`	Distance used in analysis and freight rules	No distance value
`minimumLot`	Smallest quantity allowed in the flow	No minimum-lot constraint
`multipleLot`	Rounding multiple for the transfer	No rounding constraint
`uomId`	Unit for lot and capacity values	Default planning unit from Units of Measure
`validFrom`	Start of validity	No additional initial restriction
`validTo`	End of validity	No additional final restriction

Capacities and material-specific rules live in related datasets. Direct lane, material-level transfer, tax, and node valuation is documented in Logistics and location costs.

Dependencies¶

Locations for origin, destination, and route stops.
Materials for eligibility and item-level specialization.
Units of Measure for lots, capacity, weight, and volume.
An active network version to provide scenario context.
Fleet, vehicle type, logistics capacity, and freight table master data when these constraints are part of the model.

Used by¶

Supply Planning data model;
Supply Network Planning and Design;
DRP, Deployment, and Load Building;
Supply Plan generation and analysis;
projected inventory, coverage, and write-off;
Cost-to-Serve and P&L;
direct flow and node valuation in Logistics and location costs;
Supply Network Explorer and dependency diagnostics.

Validations¶

a lane without leadTime is not used by a calculation that requires transit time until the rule is defined;
distance is not inferred automatically;
origin and destination exist and are different;
no duplicate lane in the same version and validity;
lead time, lots, and capacities use the correct unit;
materials are enabled only on valid lanes;
routes are complete and have no unintended cycles;
material-specific rules override general rules unambiguously.