← Back to team overview

openerp-india team mailing list archive

[Bug 966395] [NEW] Unit of Measures (UoM) not respected for pricelists based pricing

 

Public bug reported:

OpenERP 6.0.3 WebClient

When changing the Unit of Measure for a line in a Sales Order and
Invoice, the conversions are not respected.  For example, if a product
is defined as grams (g) and the pricelist prices are entered for grams
(eg 1$/g), but the line is changed to kilograms, the pricing returned
will be that of grams, which now means the line is prices at 1$/kg.

The pricelist match also does not respect UoM conversions, for example,
if we have a lower price for 100g, entering 1kg will return the price
for 1g, thus being the incorrect price.

All UoM based matched and lookups must respect the UoM conversions
defined in the system.

Additionally and ideally, prices and pricelists should be entered
optionally with a UoM and a per UoM.  example, 10$ per 12 grams, this
provides enough flexibility for many more scenarios and is the format
used in many other ERPs.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/966395

Title:
  Unit of Measures (UoM) not respected for pricelists based pricing

Status in OpenERP Addons (modules):
  New

Bug description:
  OpenERP 6.0.3 WebClient

  When changing the Unit of Measure for a line in a Sales Order and
  Invoice, the conversions are not respected.  For example, if a product
  is defined as grams (g) and the pricelist prices are entered for grams
  (eg 1$/g), but the line is changed to kilograms, the pricing returned
  will be that of grams, which now means the line is prices at 1$/kg.

  The pricelist match also does not respect UoM conversions, for
  example, if we have a lower price for 100g, entering 1kg will return
  the price for 1g, thus being the incorrect price.

  All UoM based matched and lookups must respect the UoM conversions
  defined in the system.

  Additionally and ideally, prices and pricelists should be entered
  optionally with a UoM and a per UoM.  example, 10$ per 12 grams, this
  provides enough flexibility for many more scenarios and is the format
  used in many other ERPs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/966395/+subscriptions


Follow ups

References