3.3 Production BOM Advanced Features
Phantom Bill of Material
A phantom BOM is a bill-of-material coding and structuring technique used
primarily for transient (nonstocked) subassemblies. For the transient item, leadtime is set to zero and the order quantity to lot-for-lot. A phantom BOM
represents an item that is physically built, but rarely stocked, before being used
in the next step or level of manufacturing. This permits MRP logic to drive
requirements straight through the phantom item to its components, but the
MRP system usually retains its ability to net against any occasional inventories
of the item. This technique also facilitates the use of common bills of materials
for engineering and manufacturing.
Phantom BOMs are used to reduce the number of levels in the BOM and
therefore in the product structure. They simplify what you view on the BOM.
Used exclusively for determining dependent demand, phantom BOMs never
lead to a finished product. This production BOM type does not have its own
inventory master data.
Dear vairager,
as far as I know phantom BOM is one of other production BOMs (phantom BOMs) included in the main production BOM. This production BOM type never leads to a finished product, but is used exclusively for determining the dependent demand. Phantom production BOMs do not have their own item master data. if you have made phantom BOM, you may not use it directly to item card.
To create phantom BOM is generally by using production BOM and using it after type field selected is production BOM in a main production BOM.
rgds,
Johnson Alonso
"British Army Saying - (The 6 P's) - Proper Planning Prevents Piss Poor Performance"
Here is another description phantom BOM from me and some examples:
A phantom assembly is used when you want to be able to structure a BOM so it is easy to understand, but don't want to create too many production orders.
Assume an auto Engine. There are hundreds of components. You might structure them as: Engine block and parts, camshaft and parts, and 6 piston assemblies. But you don't want to create 3 production orders, too much hassle. So you want to issue the components for the piston assembly in the same production order as the Engine block. So you create a new material number for the Piston assembly, but you mark it as a phantom assembly. That means that when you create the bom for the Engine assembly, you only have two assemblies, the Engine block and the Camshaft. You add the phantom assembly for the Piston Assembly to the Engine block BOM, saying it requires 8 of the phantom assembly. When the production order is created for the Engine block, the picklist will also include all of the components of the 8 piston assemblies.
1) When to use, or not use a phantom assembly?
If you need to do cost accounting on how many hours it takes to assemble a piston assembly, it cannot be a phantom assembly, because as a part of the Engine block assembly, the labor costs are included in the Engine block production order, and therefore in the standard cost.
or :
If you plan to purchase a sub-assembly from a vendor and not build the subassembly in house, it would be called a phantom BOM. The MRP module would then create action items to buy the sub-assembly from a vendor rather than buying the components and issuing a make for the sub-assembly. However, you would still be able to print this phantom BOM in the BOM module.
Comments
Hope that help ...
as far as I know phantom BOM is one of other production BOMs (phantom BOMs) included in the main production BOM. This production BOM type never leads to a finished product, but is used exclusively for determining the dependent demand. Phantom production BOMs do not have their own item master data. if you have made phantom BOM, you may not use it directly to item card.
To create phantom BOM is generally by using production BOM and using it after type field selected is production BOM in a main production BOM.
rgds,
Johnson Alonso
"British Army Saying - (The 6 P's) - Proper Planning Prevents Piss Poor Performance"
sea-navision-community-subscribe@yahoogroups.com
detail in:
http://sea-navision-community.blogspot.com
A phantom assembly is used when you want to be able to structure a BOM so it is easy to understand, but don't want to create too many production orders.
Assume an auto Engine. There are hundreds of components. You might structure them as: Engine block and parts, camshaft and parts, and 6 piston assemblies. But you don't want to create 3 production orders, too much hassle. So you want to issue the components for the piston assembly in the same production order as the Engine block. So you create a new material number for the Piston assembly, but you mark it as a phantom assembly. That means that when you create the bom for the Engine assembly, you only have two assemblies, the Engine block and the Camshaft. You add the phantom assembly for the Piston Assembly to the Engine block BOM, saying it requires 8 of the phantom assembly. When the production order is created for the Engine block, the picklist will also include all of the components of the 8 piston assemblies.
1) When to use, or not use a phantom assembly?
If you need to do cost accounting on how many hours it takes to assemble a piston assembly, it cannot be a phantom assembly, because as a part of the Engine block assembly, the labor costs are included in the Engine block production order, and therefore in the standard cost.
or :
If you plan to purchase a sub-assembly from a vendor and not build the subassembly in house, it would be called a phantom BOM. The MRP module would then create action items to buy the sub-assembly from a vendor rather than buying the components and issuing a make for the sub-assembly. However, you would still be able to print this phantom BOM in the BOM module.
hope it could be used.
rgds,
Johnson Alonso
sea-navision-community-subscribe@yahoogroups.com
detail in:
http://sea-navision-community.blogspot.com