c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #24008
[Bug 780413] Re: stab6.02- changing uom leads to erroneous price calculations due to rounding too early
Hello Graeme,
I have tested your scenario again.
May be you have miss something.
First you have to set digit="5" or as per requirement in sale price 's
decimal accuracy and then check your scenario.
If you not set the proper digit then it is calculate by default as a 2 digits so it is made price by rounding.
I have also check your issue with by 2 digit in decimal accuracy and the rounding are proper.
If you want to proper value with decimal point in sale price with using
this type of uom then please change the digit of decimal accuracy as per
requirement.
So would you please check it again and notify us your problem.
Thanks for the understanding!
** Changed in: openobject-addons
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/780413
Title:
stab6.02- changing uom leads to erroneous price calculations due to
rounding too early
Status in OpenERP Modules (addons):
Incomplete
Bug description:
Take this scenario.
Default UOM is 1kg and the net price is 4.99 / kg on a pricelist.
Change it to 1000 grams in an SO and you will see the net price is
$0.00. One would expect 1000g = 1kg = $4.99
Extreme example I know, but lets say it was $14.99 per kilo, how much
is 1000 grams
To my mind it should be $14.99 but OpenERP says it is $10.00 if I
change the price to $15.00 / kg then 1000 grams is $20.00.
What about a much more realistic $44.99/kg and the guy wants 800
grams. Enter 0.8 kg and you charge $35.99. Enter 800 grams and it is
$32.00
IMO net total price should be the same no matter what UOM is chosen to
represent the quantity.
Follow ups
References