I have requirement to only charge Fuel Surcharge on US miles for Shipment from Mexico. Itinerary handles addition of Interim Point (border crossing stop) and it's only Single Pickup and Single Delivery shipment. So Shipment is S-B-D where S= Source, B = Border Crossing stop and D= Delivery stop.
I configured Accessorial Code and Accessorial Cost ID to account for this scenario where " Destination Distance to the Previous Stop (if any)" Rate Basis has been used in Accessorial Cost ID. This configuration to support apply fuel surcharge only on distance from B to D (US miles only).
After configuring Rate Factor, Rate Factor Rule OTM is successfully applying Fuel Surcharge Accessorial and Accessorial Cost to Rate Offering (as Rate Offering is defined in Rate Factor Rule). However, during building shipment it's not applying fuel surcharge to shipment (Shipment is within effective and expiration date of Rate Factor which was processed).
In log I see following: Basically it's calculating distance but still not applying to the shipment (not sure why)
RateEngineDebug REStop.setDistFromPrev(): dist = 0.0 MI, gid = XXX.705 [batch - 2]
2015-05-27 14:39:38.315 669220 Debug RateEngineDebug REStop.setDistFromPrev(): dist = 16.3 MI, gid = XXX.BC_PROGRESO_TX [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.setDistFromPrev(): dist = 1336.6 MI, gid = XXX.104 [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): stopNum = <3>, gid = <XXX.104>. [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): distanceFromPreviousStop is empty, calling initDistances() [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): stopNum = <3>, gid = <XXX.104>. [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): distanceFromPreviousStop is empty, calling initDistances() [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.32 669220 Debug RateEngineDebug RECharge.getMultiplierValue(): Initial <0 MI>, count <1>, value <0 MI> [batch - 2]
2015-05-27 14:39:38.32 669220 Debug RateEngine RECharge.evaluate(): Applying a charge of 0.3 USD * 1 per: [batch - 2]
2015-05-27 14:39:38.321 669220 Debug RateEngine RECharge.evaluate(): 1 MI of SHIPMENT.DEST.PREV_DISTANCE <0> [batch - 2]
2015-05-27 14:39:38.321 669220 Debug RateEngine RECharge.evaluate(): Cost for this iteration is 0.0 USD [batch - 2]
Expectation is it should apply fuel surcharge on 1336.6 MI which would be (1336.6 * 0.30 = 400.98 ).
Any of fellow OTMers have tried using this functionality? Has it worked for you? We are on OTM 6.3.1 version.
I am leaning towards OTM Bug as conclusion, but wanted to bounce it off against this Forum if anyone has encountered this issue?
Thank you,
Cshah8
I configured Accessorial Code and Accessorial Cost ID to account for this scenario where " Destination Distance to the Previous Stop (if any)" Rate Basis has been used in Accessorial Cost ID. This configuration to support apply fuel surcharge only on distance from B to D (US miles only).
After configuring Rate Factor, Rate Factor Rule OTM is successfully applying Fuel Surcharge Accessorial and Accessorial Cost to Rate Offering (as Rate Offering is defined in Rate Factor Rule). However, during building shipment it's not applying fuel surcharge to shipment (Shipment is within effective and expiration date of Rate Factor which was processed).
In log I see following: Basically it's calculating distance but still not applying to the shipment (not sure why)
RateEngineDebug REStop.setDistFromPrev(): dist = 0.0 MI, gid = XXX.705 [batch - 2]
2015-05-27 14:39:38.315 669220 Debug RateEngineDebug REStop.setDistFromPrev(): dist = 16.3 MI, gid = XXX.BC_PROGRESO_TX [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.setDistFromPrev(): dist = 1336.6 MI, gid = XXX.104 [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): stopNum = <3>, gid = <XXX.104>. [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): distanceFromPreviousStop is empty, calling initDistances() [batch - 2]
2015-05-27 14:39:38.316 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): stopNum = <3>, gid = <XXX.104>. [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): distanceFromPreviousStop is empty, calling initDistances() [batch - 2]
2015-05-27 14:39:38.318 669220 Debug RateEngineDebug REStop.getDistanceFromPreviousStop(): Returning <null> [batch - 2]
2015-05-27 14:39:38.32 669220 Debug RateEngineDebug RECharge.getMultiplierValue(): Initial <0 MI>, count <1>, value <0 MI> [batch - 2]
2015-05-27 14:39:38.32 669220 Debug RateEngine RECharge.evaluate(): Applying a charge of 0.3 USD * 1 per: [batch - 2]
2015-05-27 14:39:38.321 669220 Debug RateEngine RECharge.evaluate(): 1 MI of SHIPMENT.DEST.PREV_DISTANCE <0> [batch - 2]
2015-05-27 14:39:38.321 669220 Debug RateEngine RECharge.evaluate(): Cost for this iteration is 0.0 USD [batch - 2]
Expectation is it should apply fuel surcharge on 1336.6 MI which would be (1336.6 * 0.30 = 400.98 ).
Any of fellow OTMers have tried using this functionality? Has it worked for you? We are on OTM 6.3.1 version.
I am leaning towards OTM Bug as conclusion, but wanted to bounce it off against this Forum if anyone has encountered this issue?
Thank you,
Cshah8