Invoice line quantity must have "Product UoS" decimal precision

[Paulius Sladkevičius @ hbee]

For example: If invoice created from sale order which have 3 decimal numbers for product quantity I think quantity must be shown in invoice with 3 decimal numbers too.

[Amit Parik (amit-parik)]

Hello Paulius,

I have checked your issue and I agree with you.
The problem occurs when, we will create a invoice from the sale order and our sale order created with "UoS" as well as we have set s decimal accuracy for "Product UoS" i.e 5. So the problem is in invoice line which is removed the decimal accuracy of product qty and rounding it.

Now comes on your solution, I do not agree with your solution, because here we have used a same object(account.invoice.line) for customer invoice line and supplier invoice line. So If we assigned a decimal precision of "Product UoS" to qty field of account.invoice.line then it will updated for both customer invoice and supplier invoice.

So we can not use this decimal precision for qty field of the account.invoice.line object. As per my suggestion we have to create a new decimal precision for invoice quantity then we will use this precision for invoice line's quantity.

That's before implementing this we need a more dissuasion on this, So please provide more information here on same.

Thanks and waiting for your reply!

[Paulius Sladkevičius @ hbee (komsas)]

Hi Amit,

yes your are right, there must come to separate UoS/UoM. So question is why account invoice don't have 2 more objects like account customer invoice and account supplier invoice. Then it will be easy to add this feature. So better to change background and don't have in future other issues like this, when customer/supplier invoice have like these important differences. What you think?

[Amit Parik (amit-parik)]

Hello Paulius,

First of all thanks for your reply!

Yes, that will be better if we have to use different object for customer invoice line and supplier invoice line.But If we wants to do this then there must be a required a major changes likes we have to create a new methods for that.

So before implementing this we need to more discussion on this then after we will decide which solution is better for this

That's why currently I am setting this as an "Opinion".

@Accounting Experts: Would you please share your views on this.

Thanks and more suggestions are welcomed!

[Numérigraphe (numerigraphe)]

I don't see the point in splitting the invoice object in customer/supplier.
Can't we simply use the biggest precisions of the 2 (UoM and UoS)?
Lionel Sausin.

[Graeme Gellatly (gdgellatly)]

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 <email address hidden>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 is why there
> is actually a different dp for both and unfortunately not at invoice level)
>
>
>
> *Eric CAUDAL*, <email address hidden>
> Cell: + 86 186 2136 1670. Skype: elico.corp*Elico Corp - OpenERP Ready Partner, Shanghai.*http://www.openerp.net.cn
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-accounting
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openerp-expert-accounting
> More help : https://help.launchpad.net/ListHelp
>
>

[Vadim - Enapps LTD (vadim-enapps)]

Good approach Graeme.

Sent from my Windows Phone
--------------------------------
From: Graeme Gellatly
Sent: 25/01/2012 04:34
To: <email address hidden>
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.]