← Back to team overview

c2c-oerpscenario team mailing list archive

Re: [Bug 702288] Re: Cost price calculation limited to 2 levels in product bom

 

Fabien, Olivier, Antony, all,

Thanks for the clarification.

1. I agree this should not be the default behaviour of OpenERP, wether
it's an option in the mrp module or a new functionnality brought by an
extra module like product_extended is fine for me.

2. It's good to have product_extended available in V6. Thanks.

3. I understand the problem of legal or not legal calculation for cost price of a finished product. And i agree it's not because you update the price of a component of the BOM that the finished product cost price should be automatically updated.
BUT, you should have a mean to update it manually when required (i.e. once a year).
That's what product_extended is doing, but only for two levels not more.
Which is not usable for my customers. (i.e. one have around 100 level in its BOM). So we should have a kind of "compute all products cost price based on their BOM" method or something like that.

We could develop something like that from partner side but i think it's
better to have it globalized and standardized from OpenERP.

So the bug i reported was not for OpenERP MRP module but for product_extended one... and it was not certified yet, sorry i didn't noticed it.
But now that it's certified, can you please re-consider to solve it to have n level of BOM calculated now ? :-)



________________________________________
From: bounces@xxxxxxxxxxxxx [bounces@xxxxxxxxxxxxx] On Behalf Of Antony Lesuisse [al@xxxxxxxxxxx]
Sent: Friday, April 01, 2011 00:04
To: Bertrand Hanot
Subject: [Bug 702288] Re: Cost price calculation limited to 2 levels in product bom

I said:  think cost price should not be AUTOMATICALLY updated from cost
price of bom component. What could possibly go wrong... ?

This feature will go back in the product_extended module (or maybe a
specific mrp_bom_price one) and will be correctly implemented there.
Because i think there are different possible policies on how to do it
and that specific module should implement them all.

For example: Updating a price from bom children vs updating the parents
when a children is updated (but then what happens if a product is parent
of multiple bom with the same children and different coeficients?).

--
You received this bug notification because you are a direct subscriber
of the bug.
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.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/openobject-addons/+bug/702288/+subscribe

-- 
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.



References