c2c-oerpscenario team mailing list archive

["Jan Verlaan \(Veritos\)" <702288@xxxxxxxxxxxxxxxxxx>]

I see the site effects Fabien has mentioned in comment 21.
I also see the need for having calculated the costs for a item that contains a BOM.
The proposal Steffie made is in my opinion a good one, that way a user has the calculated cost available while the cost price field isn't updated.
Please rethink my proposal to have manual calculation button on a BOM item to direct calculate the price and a calculation triggert by the scheduler for mass updates (so daily system performance isn't affected)

If this is acceptable the bug description in https://bugs.launchpad.net/openobject-addons/+bug/747056 should be changed.
Don't remove the method do_change_standard_price in the line 57 in mrp/product.py but
change the function to update the new suggested field and make the calculation multilevel.

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

Title:
  Cost price calculation limited to 2 levels in product bom

Status in OpenERP Modules (addons):
  Invalid

Bug description:
  A concrete example better than a long and difficult explanation :-)

  We have the following product A composed of the product B and product B is composed from product C. So the below BOM:
  A
  -----B
  -----------C

  If the price of B is modified, then the price of A can be also modified.
  But if i modify the price of C, only B is modified and not A.

  This is a very important blocking issue, since in most of the real prod environment, we've of course more than 2 level of boms (in some customer installation, up to 100 levels !).
  So any modification at the bottom should have a consequence on all the bom structure until the top, else OpenERP cannot be used for production.