openerp-expert-accounting team mailing list archive

[Vadim Chobanu <vadim@xxxxxxxxxxxxxxx>]

Good approach Graeme.

Sent from my Windows Phone
--------------------------------
From: Graeme Gellatly
Sent: 25/01/2012 04:34
To: openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openerp-expert-accounting] [Bug 919572] Re: Invoice linequantity must have "Product UoS" decimal precision

This old debate.  Fundamentally decimal precision (and for that matter uom
conversion) is broken.

I still maintain that for purchases, sales, invoices the correct approach -
1 level of precision at the price_unit level, and a seperate precision at
the subtotal/total level shared across all 3 objects.  The totals on these
documents MUST match.  You cannot give a quote to a customer and then
invoice a different price.  We have been running this 6 months trouble
free, by just creating a precision called unit_price, and using 'Account'
for all totals.  The only other change I would like to say, but it is
strictly wishlist is to have a separate display and storage precision.
 Quite simply to avoid the fact that 800g of something costs more than
0.8kg (sometimes by as much as 50%).

On Wed, Jan 25, 2012 at 3:58 AM, Eric Caudal <eric.caudal@elico-
corp.com>wrote:

>  It makes no point for UoM/UoS but it is neessary for unit price which
> precision can be different for sales and purchases (and this
[The entire original message is not included.]