Odoo Addons (MOVED TO GITHUB)

Bug #985525
Comment #7

Comment 7 for bug 985525

Revision history for this message

Colin Bacon (ym8-colin) wrote on 2012-07-08:

Hello Amit,

I must agree with Lionel - it is very normal practice to have many of the same components within one BOM.

I also have also the same issue for a customer of mine - in the textile industry.

Let me explain:

I'm trying to set-up a 'master' BOM containing many sub-components - consisting of cotton threads. Many of these sub-component (threads) are referencing the same core product - but with slightly varying quantities per meter. i.e. each threads is the same raw-material, same costs per meter, etc. - just different length (due to the patterns the weaving machines are creating).

When trying to add multiple threads directly to the BOM - I also get this error message "ValidateError - Error occurred while validating the field(s) product_id: BoM line product should not be same as BoM product"

Work-around:
One work-around I found that work (well sort-of) -....

a) first create a BOM without any components, but ensure all workcentres and other information has been added.
b) Then create the BOM components with reference to the same products (but with different quantities) and also referencing Parent BOM (in the properties/parent BOM field) .
c) When complete you can open the parent BOM again and see the multiple sub-components have been added.

As I needed an exact sequence of material on the BOM this seems the only way I could create the master BOM.

Nevertheless, the main issue with this work-around is you can't change anything on the master BOM again - without getting the error message :

"ValidateError - Error occurred while validating the field(s) product_id: BoM line product should not be same as BoM product"

The error message in this case is also misleading as the final product (Master BOM) is not included anywhere in the BOM component list - so there is no issues with recursive errors of the same product on this BOM. I only have many repeating items in a BOM - but with varying quantities.

As you can imagine this is really irritating when you have over 10.000's products. So please reconsider a solution for these type of business scenarios.

Thanks

Colin

Hello Amit,

I must agree with Lionel  - it is very normal practice to have many of the same components within one BOM.

I also have also the same issue for a customer of mine - in the textile industry.

Let me explain:

I'm trying to set-up a 'master' BOM containing many sub-components - consisting of cotton threads.  Many of these sub-component (threads) are referencing the same core product -  but with slightly varying quantities per meter.  i.e. each threads is the same raw-material, same costs per meter, etc. - just different length (due to the patterns the weaving machines are creating).

Work-around:
One work-around I found that work (well sort-of) -....
  
a) first create a BOM without any components, but  ensure all workcentres and other information has been added.  
b) Then create the BOM components with reference to the same products  (but with different quantities) and also referencing Parent BOM (in the properties/parent BOM field) .  
c) When complete you can open the parent BOM again and see the multiple sub-components have been added.

As I needed an exact sequence of material on the BOM this seems the only way I could  create the master BOM.

Nevertheless,   the main issue with this work-around is you can't change anything on the master BOM again - without getting the error message :

"ValidateError - Error occurred while validating the field(s) product_id: BoM line product should not be same as BoM product"

The error message in this case  is also misleading as the final product (Master BOM) is not included anywhere in the BOM component list - so there is no issues with recursive errors of the same product on this BOM. I only have many repeating items in a BOM - but with varying quantities.

As you can imagine this is really irritating when you have over 10.000's products.   So  please reconsider a solution for these type of business scenarios.

Thanks

Colin