c2c-oerpscenario team mailing list archive

["Vinay Rana \(openerp\)" <vra@xxxxxxxxxxx>]

Hello Kyle,

As for I think It's ultimately a user fault to changing the UOM which already have a stock move in another UOM.
For more clarification and discussion I am setting this as opinion.
@experts: Would you please share your view.

Thanks.

** Changed in: openobject-addons
       Status: New => Opinion

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

Title:
  Changing UOM can corrupt database

Status in OpenERP Modules (addons):
  Opinion

Bug description:
  I have a product. Its uom by default is PCE. I sell this product but
  didnt know about UOM. Later I configure them correctly as a Ft, or
  length measurement. I also create a BOM for the product. OpenERP
  cannot compute properly the value of the stock, nor compute a
  manufacturing order because in the history of the stock_move table
  there is entries of uncompatible conversion factors. This is due to
  the field of stock value being a function field. It calculates the
  value of stock based on all past purchases and sales, but it cant
  because there exists entries that are not compatible.

  OpenERP freely allows anyone to change the UoM in the program with
  ease, with no warning of any kind that doing so could potentially
  corrupt the database, break the scheduler entirely, and prevent that
  product from ever being able to use a BOM. This bug references the
  problem in detail.

  https://bugs.launchpad.net/openobject-addons/+bug/707287

  Propose,
  You should if a person changes the UoM from a compatible to incompatible factor alter all of the previous records UoM in the database to match so the conversion is compatible,

  rewrite the function field and manufacturing methods,

  not allow the person to change the measure due to integrity violations

  or place a warning when the attempt to change it telling them they
  could corrupt their database.

  This is a serious problem and should not be ignored

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