c2c-oerpscenario team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello Kevin,

Thanks for your quick reply and excellent video.

Now I have totally checked your issue but I am not agree with you,
because I think you have missed the functionality of the "Normal BoM"
and "Sets / Phantom".

Let me clarify it.

1)Normal BoM : If you have a parent and child relationship in "BoM"
means you have hierarchy in "BoM structure ". It creates a different
procurement order as well as  different production order (MO) for all
produces products.

2) Sets / Phantom : It creates a one procurement order as well as
production order (MO) for all produces products that means it creates a
always one MO.

According to your scenario you have created a two main product "Pivot" and "Pivot 2" like 
Pivot : (Normal) :
           -> subassembly ("Sets / Phantom")
                              -> product2
                              ->product3 
Pivot2 : (Normal) :
           -> subassembly2 ("Normal")
                              -> product7
                              ->product8 
Now you have created a SO for these two product. Before run the scheduler please check the procurement of the related SO. You can see the one procurement for Pivot and two different procurement for pivot 2 (one for pivot2 and another for subassembly2). Run the scheduler you can see the one MO for pivot and two different MO for pivot 2 which is fine as per the BoM type concept.

I have seen the one more another issue in your video. You have changed
your "BoM Type" as a "Sets / Phantom" for subassembly2 product, but in
BOM  there is a one2many field as a component. If you want to modify it,
go to the main record and then change it. Other wise you can not see the
percent BoM in  subassembly2 product, so it didn't consider it type as a
"Sets / Phantom" and created a two different MO.

I have attached a video for more clarification so would you please check
it.

Currently all are working fine so I am closing this issue.

Thanks and correct me if I am wrong.

** Changed in: openobject-addons
       Status: Incomplete => Invalid

** Converted to question:
   https://answers.launchpad.net/openobject-addons/+question/170992

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