Same product with multiple BOMS defined - MO defaults to first BOM

[Kevin McMenamin]

The same inventory product can have multiple BOMs defined to allow for multiple ways of making the same product. When a SO is raised for the product, the related MO is for the first BOM - while you can change the BOM in the MO this does not update the products to be consumed, so there is no way of using an alternative BOM.

[Amit Parik (amit-parik)]

Hello Kevin,

I have checked your scenario with latest trunk at my end but all are Woking as expected.

I did not faced the problem as you described in bug report so would you please elaborate more information on this.
I have attached a video for your more reference so would you please check it and notify us where you faced the problem.

Thanks and waiting for your reply!

[Kevin McMenamin (kevin-mcmenamin)]

The difference I am getting is that in procurement exceptions my state for the SO is "running" and the products for the BOM have already been assigned.
I have un-installed mrp-jit but no change in behaviour.
Any ideas?

[Kevin McMenamin (kevin-mcmenamin)]

Juts created a brand new database from scratch without MRP-JIT installed and process works as per your video. So bug is with MRP-JIT - if a product has > 1 BOM then should be an exception created with state of confirmed and no procurement records created at individual product level.

As a side note, uninstall of MRP-JIT does not uninstall the functionality.

[Amit Parik (amit-parik)]

Hello Kevin,

"mrp_jit" used for the "automatic run the procurement" so if the "mrp_jit" has installed then your procurement will be automatically run. This is the functionality of the mrp_jit(Just-in-time).

So if there are more then "BoM" available for one product it will consider the first "BOM" and run the procurement.
With "mrp_jit" your procurement directly goes to the "Running " state so you can not change the "BOM" on procurement.

That's why this is not a bug but functional behaviour with "mrp_jit".

For your last issue for the uninstallation , current OpenERP version does not fully supported to uninstallation.

Hope this will help for you.

Thanks.

[Amit Parik (amit-parik)]

Hello Kevin,

"mrp_jit" used for the "automatic run the procurement" so if the "mrp_jit" has installed then your procurement will be automatically run. This is the functionality of the mrp_jit(Just-in-time).

So if there are more then "BoM" available for one product it will consider the first "BOM" and run the procurement.
With "mrp_jit" your procurement directly goes to the "Running " state so you can not change the "BOM" on procurement.

That's why this is not a bug but functional behaviour with "mrp_jit".

For your last issue for the uninstallation , current OpenERP version does not fully supported to uninstallation.

Hope this will help for you.

Thanks