c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #32030
[Bug 845221] Re: phantom bom not exploded in MO
I have found the problem which explains the difference between your results and mine.
When I set up sub-assembly2 I did so as a phantom/kit. I then added this kit as a product in pivot2, and when I ran the SO/MO process, it appears as an unexploded line (hence my bug request).
After seeing your video I created a new instance and have found that the bill of materials bom type can be different from the bill of materials component bom type.
For the sub-component (itself a kit) ff the Bill of materials Component value is not set as phantom/kit but the Bill of Materials is set as a phantom/kit then you do not get an exploded MO.
Attached are screen shots showing the different values for the same product.
Do you want a new bug or keep as this one?
** Attachment added: "Sub-Assembly Issue.ogv"
https://bugs.launchpad.net/openobject-addons/+bug/845221/+attachment/2399678/+files/Sub-Assembly%20Issue.ogv
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/845221
Title:
phantom bom not exploded in MO
Status in OpenERP Addons (modules):
Invalid
Bug description:
I have created a simple BOM (Product = Pivot, Stockable, Make to order, Produce) with a sub-BOM of type phantom.
If the sub-BOM has the parent BOM set then a SO for Pivot creates a MO with the sub-BOM explded into its component products.
Then deleted the parent field from the sub-BOM and added as a product
line into the parent BOM. Re-ran the process - now the MO has the sub-
BOM as a product line only, not exploded to its component products.
My issue is that the first option is fine as long as a sub-BOM only
has one parent, but no good if has multiple. Other option is to make
the sub-BOM a normal BOM, but then I get MO for each component, which
will get very confusing in complex assembly situations (which is my
instance).
Have I missed something or is this the expected behaviour?
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/845221/+subscriptions
References