Possible bug found with Weight and Freight Estimator. When Weight of a product is greater than 2 decimal point to the right Freight estimator ignores weight for multiple of 12.
1. Enter 0.333 or 0.3333 for weight in the item profile.
2. Add the item with the weight to a Sales Doc and enter multiple of 12's(12,24,36) into the quantity.
3. Use Everest Freight Estimator or Web based "Shipping Calculator", the weight of the item will be ignored. Causing freight not to be charged for the item. This can cause under charging of the freight charge.
AIM Data Service
www.aimds.com
Everest Finding:
This is with reference to the issue related Everest freight rates were not getting calculated when
the weight goes beyond 4 decimals. According to the update I have got from Technical team Everest does support only 2 decimal weight accuracy. When they weight gets calculated to 4 decimal there might be a chance were it will not Calculate correctly.
the weight goes beyond 4 decimals. According to the update I have got from Technical team Everest does support only 2 decimal weight accuracy. When they weight gets calculated to 4 decimal there might be a chance were it will not Calculate correctly.
Kinldy reduce decimal accuracy to 2 decimal.
Corrective Actions Needed:
This is a definate bug in the program. What is happening is that the rate import program in Everest is creating starting weight and ending weight that is not consistent between the different shipping method. Sometimes it creates 1.01 to 2.00 and sometimes it creates 1.00 to 1.99. So when the total weight falls between these ranges, it will not work.
Everest refuse to see it as a bug. If weight can not be calculated for decimal accuracy greater than two, then the weight value in item profile should be limited to only 2 decimal digit accuracy. Otherwise people will inadvertently make the mistake. Righ now the weight profile in Everest allows 6 digit decimal accuracy.
No comments:
Post a Comment