c2c-oerpscenario team mailing list archive

[jobiols <707287@xxxxxxxxxxxxxxxxxx>]

hi all
I have the same problem that Kyle, 

1. a product had a bad UOM
2. an inventory adjustment 
3. mrp run into exception "UoM Conversion Product from m to Default UoM PCE is Not possible As They Both Belong to Different Category!."

Then our first problem was to figure out what was the product that
raises this exception. because m and PCE are harcoded in the string. I
added the following code on product.py line 144 before the raise
statement, to get more information:

sys.stderr.write('conversion desde %s hasta %s no es posible cantidad %s' % (from_unit.name, to_unit.name, qty))
sys.stderr.flush()

After much research we discovered the product that generated the problem
and correct the UOM on the product but the exception did not disappear.

when I read your comments I discover that the inventory adjustment was the blame, then I removed the product from BOM recreate it with the correct UOM and after that adjust the inventory, then put the corrected product in the BOM. This NOT solved the problem. Just moved the error to the next product.
The only difference with Kyle's scenario is that I've never had installed magento

I am in full agreement with what was said by Kile, the bug is very serious.
please see also Bug #716705 Product UoM conversion error needs definition

I hope this helps

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

Title:
  Manufacturing orders broken UOM

Status in OpenERP Modules (addons):
  Triaged

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.