SAP reference for the transportation network¶
This page complements the transportation network. The closest analogy depends on the installed SAP solution: SAP TM, SAP IBP/APO, and LE routes do not expose the same contract.
| OpsFactor | Nearby SAP concept | Note |
|---|---|---|
originLocationId, destinationLocationId |
TM or IBP/APO logistics locations/nodes | Resolve to existing OpsFactor IDs |
laneId |
transportation lane or origin-destination-mode combination | There is no universal S/4HANA table |
networkVersionId |
planning version/scenario | Must be materialized in OpsFactor |
leadTime, distance |
route/lane duration and distance | Document unit and source |
lots and uomId |
quantity/capacity constraints | May come from planning, not LE |
| validity | connection or rule validity | Convert to validFrom/validTo |
A safe composition is NET-2026-1000-DC02-ROAD. Classic LE routes (TVRO
and route determination) may help, but they do not replace a versioned planning
lane with capacity and lot constraints.
In SAP TM, a trade lane is also not a direct substitute for a transportation lane; verify the object that actually describes the operational flow.
Nearby SAP transactions or apps¶
There is no universal transaction. In classic LE, route maintenance is in Customizing; in SAP TM, use the location and network apps available in the release. In SAP IBP/APO, reconciliation occurs in the corresponding planning area master data and operators.
SAP references¶
Return to the transportation network or the SAP index.