c2c-oerpscenario team mailing list archive

["Rifakat Haradwala \(OpenERP\)" <726816@xxxxxxxxxxxxxxxxxx>]

Hello Don Kirkby,

It has been fixed in lp:~openerp-dev/openobject-addons/trunk-bug-726816-rha ,
Revision ID: rha@xxxxxxxxxxx-20110303055618-qprsaa75mrnspxd5
Revision no: 4473
Thanks for reporting.

Regards,
rha


** Changed in: openobject-addons
       Status: In Progress => Fix Released

-- 
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/726816

Title:
  Product field standard_price should use 'Purchase Price' precision
  instead of 'Account' precision

Status in OpenERP Modules (addons):
  Fix Released

Bug description:
  The product_product.standard_price field gets its precision level from
  the 'Account' entry, and not from the 'Purchase Price' entry of the
  decimal_precision table. In my opinion, it would make more sense to
  use the 'Purchase Price' entry.

  The scenario I'm thinking of is when products are purchased in bulk so
  that the individual price might be very small. For example, a company
  might order 5000 screws each month for a total of $6.00. In that case,
  the price would be $0.0012 per screw. All the accounting entries could
  be held to the nearest cent (two decimal places), but the purchase
  price requires four decimal places in this case.

  I tested the behaviour in version 6.0.1.