3810360 - Freight Agreement Lacks From/To Route Fields for Automatic Charge Determination

Business requirement is to create a freight agreement based on From & To route-based determination, so that transportation charges can be calculated automatically based on the applicable route. 

 SAP S/4HANA Cloud Public Edition

1. Open the Manage Freight Agreement app
2. Select and open a Freight Agreement
3. Observe that there is no field to maintain From and To locations for route-based determination

In SAP S/4HANA Cloud Public Edition, the Freight Agreement does not include a direct "Route" concept (From/To location) at the agreement level. This is a current limitation of the public cloud version of Transportation Management.

The Freight Agreement is determined based on the carrier (business partner) and purchasing organization — not by route. The calculation date must fall within the validity period of the freight agreement. Once a valid, released freight agreement is identified, the system uses logistical data from the Freight Order — including source location, destination location, item information, and quantities — as the basis for charge calculation. The Freight Order itself carries the From/To location data (source and destination locations), and this is where route-relevant information resides, not in the Freight Agreement.

Charge calculation is triggered automatically when freight orders are transferred from a decentral TM system or when the freight order is updated; it can also be triggered manually via the Manage Freight Orders app. Ensure the Freight Order is correctly populated with source and destination location data, as this is the primary vehicle through which route-relevant information feeds into charge calculation.

Activate the Determination of Geocoordinates, Distances and Durations (Scope Item 46P) if distance-based freight charges are required. This scope item integrates SAP S/4HANA Cloud Public Edition with SAP HANA Spatial Services on BTP to automatically calculate distances and durations between location pairs. (Refer to KBA https://me.sap.com/notes/3774344) Ensure the Freight Agreement is in Released status before charge calculation is triggered. 

As an alternative, you can try the below approach.

Rate Tables with Location-Based Scales Maintain Rate Tables within the Freight Agreement's Calculation Sheet that use source and destination location (or zone) as scale dimensions. This allows differentiated rates to be applied based on the origin/destination pair captured in the Freight Order at charge calculation time. The system matches the logistical data (source/destination location) from the Freight Order against the rate table scales to determine the applicable charge. 

In the rate table app - Dates & Values tab - Calculation Rules - There are different set of Calculation Base available and you can make use of them for charge determination. 

Note: If you expect the fields From and To for route based determination for charges, it will be a new requirement. Kindly post the idea in influence forum. Please use session "SAP S/4HANA Cloud for Supply Chain Logistics, public edition" (https://influence.sap.com/sap/ino/#/campaign/2897) to address specific feature requests for the Transportation Management business processes.

• Refer to: SAP Note 3774344 - Determination of Geocoordinates, Distances and Durations (46P)
• Refer to: SAP Influence: SAP S/4HANA Cloud for Supply Chain Logistics, public edition

freight agreement, route-based charges, From/To, origin destination, TM public cloud, charge calculation, rate table, calculation sheet, carrier determination, purchasing organization, manage freight orders, distance-based pricing, scope item 46P, location scales, transportation management , KBA , TM-FRA-2CL , Freight Agreement Management (Public Cloud) , Problem