My suggestion to you is to stay as far away from phantom BOM as possible. The reason is because you cannot plan for the finished product of a phantom BOM when you run MRP.
It also makes routing link setups more unnecessarily complicated.
We only recommend using phamtom BOMs for formulas that you do not have an item number for that requires assembly using your raw materials. i.e. a special color mixture requested by a customer for a special order that you cannot resell to other customers.
Phantoms are a standard manufacturing structural design aide. If you are not aware of what a phantom is, do not use it.
In essence if a subassembly is an item you need it in stock to consume it, if it is not there a production order will be raised. If however you never stock it then you "could" set it as a phantom and then the assembly will be blown through and the components will be required on the top build.
The art of teaching is clarity and the art of learning is to listen
here we hold in item table only raw materials (materials we buy from vendors) and final products (we sell to customers)
however in the process of manufacturing we have many semi-products that consist of raw materials and other semi-products. We define these as BOMs but they have no representation in the item table
then in a BOM description of a final product we have these semi-products as Type=::"Production BOM" and have raw materials as Type=::Item
Comments
whereas the inventory of the child item will be affected that is shown in item master if we use "item" in BOM.
For virtual inventory we use Phantom BOM ( "production bom" in BOM )
For actual inventory we use ordinary BOM ( "item" in BOM )
Regards,
Santosh
Santosh
Where Stones can be transformed to Gold
It also makes routing link setups more unnecessarily complicated.
We only recommend using phamtom BOMs for formulas that you do not have an item number for that requires assembly using your raw materials. i.e. a special color mixture requested by a customer for a special order that you cannot resell to other customers.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
In essence if a subassembly is an item you need it in stock to consume it, if it is not there a production order will be raised. If however you never stock it then you "could" set it as a phantom and then the assembly will be blown through and the components will be required on the top build.
however in the process of manufacturing we have many semi-products that consist of raw materials and other semi-products. We define these as BOMs but they have no representation in the item table
then in a BOM description of a final product we have these semi-products as Type=::"Production BOM" and have raw materials as Type=::Item