[v6]stock accounting: price_unit is not precise enough

Bug #1191041 reported by Kinner Vachhani on 2013-06-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Observed behaviour: Stock accounting entry is inaccurate

Steps to reproduce:

Create a product and configure it for stock accounting and average price costing
* Configure decimal precision and set purchase price to 6 decimal places
* Create an incoming stock move of quantity 100
* Book the stock in at a price including more than 2 decimal places. e.g. 1.123456 (Note that this needs the change to the wizard to show more than 2 decimal places)

Expected behaviour: The stock accounting entry would be for 100*1.123456, rounded to 2 decimal places: 112.34

Actual behaviour: the price is rounded before multiplying: 100*1.12 = 112, ie a difference of £0.34

The problem is due to price_unit in stock move. It has a precision of Account, but this is only 2 decimal places. So we can use the Purchase Price precision instead

Related branches

Amit Parik (amit-parik) wrote :


We had already improved this on v7.
We have used the Product Price accuracy for all kind of cost and sale price . So we have already improved the price_unit on stock with product price.

Issue is only exist on v6, So if you want this on vesrion6 you have to contact out OPW team at <email address hidden>.

Thank you!

Amit Parik (amit-parik) on 2013-06-20
summary: - stock accounting: price_unit is not precise enough
+ [v6]stock accounting: price_unit is not precise enough
Changed in openobject-addons:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers