c2c-oerpscenario team mailing list archive

["Fabien \(Open ERP\)" <fp@xxxxxxxxxxx>]

Hello,

Thanks for the patch, but it does not fix the problem. It's like putting
a try/except when something crash instead of fixing the real issue. As
an example, the problem reappear if you click "assign products" manually
on a picking.

The real problem is why do we have several stock.move for the same
product with non compatible UoM in the inventory ? What kind of manual
operations allows this ?

This means we must add constraints. I propose this:
  - You can never change the category of an existing UoM
  - You can never change the UoM/Purchase UoM category of a product (you can change the UoM if it's in the same UoM than
    before)

I am not sure, but these two constraints should be enough. I propose that the one who work on this bug tries a lot of scenario by changing/forcing the categories manually:
  - change the UoM (another category) during inventory, pickings, stock.move, sale, purchase..


I reopen the bug and reject the merge proposal.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/707287

Title:
  Manufacturing orders broken UOM

Status in OpenERP Addons (modules):
  Fix Committed

Bug description:
  We have around 5,000 products. We have custom UOM like ft, OZ and
  Pound. On certain products we cannot make manufacturing orders with
  this error

  Conversion from Product UoM m to Default UoM PCE is not possible as
  they both belong to different Category!.

  It is extremely frustrating because it doesnt make sense. We do not
  have a single product with UoM 'm'. The error only happens with
  certain products, not in any specific instance except that mabe the
  category UoM but not every item in that category. If we created new
  products then we dont have the issue.

  I discovered many of the products were having problems base on an
  inventory we did with the stock_move table. Deleting entries fixed
  many of the issues but we still have this problem and it makes no
  sense to us.

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