Rounding errors cause PO receipts errors

[Jonathan Wilson]

V6.0.3
products module
When receipting products defined with precision of less than one it is possible to get the error message "Processing error (qty) (uom) (product) is larger than the available quantity (qty) (uom)!". This is due to slack programming when rounding the qty's using the associated unit of measure precision value.

eg we had a quantity of 5.6 with a precision of 0.01 which was returned as 5.60000000006 and this caused the the error as 5.60000000005 > 5.6 !

Fix patch attached to this bug report

[Graeme Gellatly (gdgellatly)]

There is slightly more to this bug. In mrp.bom the quantity line is
declared as a float and not a numeric type. It would be expected to be a
numeric type with the decimal precision of uom the same as every other uom
in openerp. This could very likely have stopped the error in the first
place.

On Fri, Oct 7, 2011 at 6:45 PM, Priyesh (OpenERP) <<email address hidden>
> wrote:

> ** Changed in: openobject-addons
> Assignee: (unassigned) => OpenERP Publisher's Warranty Team
> (openerp-opw)
>
> ** Tags added: maintenance
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> https://bugs.launchpad.net/bugs/868881
>
> Title:
> Rounding errors cause PO receipts errors
>
> Status in OpenERP Addons (modules):
> New
>
> Bug description:
> V6.0.3
> products module
> When receipting products defined with precision of less than one it is
> possible to get the error message "Processing error (qty) (uom) (product) is
> larger than the available quantity (qty) (uom)!". This is due to slack
> programming when rounding the qty's using the associated unit of measure
> precision value.
>
> eg we had a quantity of 5.6 with a precision of 0.01 which was
> returned as 5.60000000006 and this caused the the error as
> 5.60000000005 > 5.6 !
>
> Fix patch attached to this bug report
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/868881/+subscriptions
>

[Somesh Khare (somesh.khare)]

Hello Jonathan,

With reference to your OPW Ticket, As we did not received any information from your end on your ticket, So for the sake of clarity we will set the status of this bug as Incomplete.
You can re-open this bug with the detailed information as well as with the steps to reproduce this bug into the stable version.

Thanks,
Somesh Khare