What impact would it have on your daily tasks in terms of time saving or cost reduction? |
it eliminates the need for manual rate changes/cost addition |
How frequently would you use this improvement? |
1-20 FRO/week |
How should it work? |
The idea is to update specific RCO base rates based on several destination customer location codes (e.g., SI_CU_00000636). In our country, certain major cities have a highway ring encircling them, and the electronic toll is determined by the highway exit. This toll can range from 1 EUR to 20 EUR, causing the rate for the same city code (e.g., SILJU) to vary depending on the placement of the PoD/PoR within the city limits and the specific highway exit the carrier must take. Due to this variability, we cannot establish the toll road as a fixed contractual charge, nor as a percentage or band, as the toll add-on is independent of the actual contractual rate but is however fixed per a specific exit. Although we have information on toll costs for common locations with regular business, the challenge lies in updating these rates accurately. The customer location code or place of loading/unloading is not associated with a customer role in the booking or reflected as a business partner in FRO. Consequently, we lack the necessary parameters to file it accordingly. Correctly filing rates would not only to eliminate the time-consuming task of manually adding costs on either side (whether it's the vendor via supplier connect, as it is not an additional later-generated cost, or the dispatcher in the TMS directly) but also to minimize any need for manual dispatcher intervention altogether. |