Infor SyteLine4 min readNetray Engineering TeamUpdated March 4, 2025

How to Set Up Phantom BOM Items in Infor SyteLine

Phantom BOM items in Infor SyteLine represent sub-assemblies that are not physically stocked or produced as separate jobs. Instead, their components blow through to the parent item's production order during BOM explosion. Phantoms simplify engineering documentation by maintaining logical sub-assembly groupings while eliminating unnecessary production orders and inventory transactions. This guide covers phantom item setup, BOM explosion behavior, and planning considerations for effective use of phantom items in your manufacturing environment.

Configuring Items as Phantoms in SyteLine

Open the Items form (SLItems) and navigate to the Planning tab for the sub-assembly item you want to configure as a phantom. Set the Phantom Flag to Yes, which stores the phantom indicator in the item table's phantom column. Phantom items do not generate separate production orders during MRP processing. Instead, their components are pulled into the parent item's job during BOM explosion. Phantom items should still have complete BOMs and routings defined for engineering documentation purposes, even though the routing is not used for production scheduling. Set the Supply Source to Manufactured (M) and the Order Policy to Lot-for-Lot to ensure MRP handles phantom items correctly during planning calculations.

Set Phantom Flag = Yes on the Items form Planning tab for each phantom sub-assembly
Maintain complete BOM and routing for engineering documentation even though routing is bypassed
Set Supply Source to Manufactured (M) and Order Policy to Lot-for-Lot for proper MRP handling
Phantom items do not appear on the planned orders list and do not generate separate jobs

Understanding Phantom BOM Explosion Behavior

When a production order is created for a parent item containing phantom components, SyteLine explodes through the phantom levels and adds the phantom's child components directly to the parent job's material list. The BOM explosion process reads the bom table recursively, detecting phantom flags at each level and continuing the explosion until non-phantom components are reached. Multi-level phantom explosions are supported, meaning a phantom can contain other phantoms up to the maximum BOM depth of 20 levels. The job materials list on the parent job shows the phantom's components with their quantities adjusted by the phantom's quantity-per relationship. Review the Job Materials form (SLJobMaterials) after job creation to verify the blow-through results match expectations.

Phantom components blow through to parent job materials during BOM explosion automatically
Multi-level phantom nesting is supported up to 20 BOM levels of depth
Component quantities are adjusted by the phantom's quantity-per ratio from the parent BOM
Verify blow-through results on Job Materials form after job creation to confirm accuracy

Planning Considerations and Best Practices for Phantoms

Phantom items affect MRP planning behavior in several important ways. MRP does not generate planned orders for phantom items, so all demand passes through to the phantom's components. If you occasionally stock and produce the phantom sub-assembly as a standalone item, use the Supply Source toggle rather than the Phantom Flag to maintain planning flexibility. Inventory can exist for phantom items in SyteLine, and MRP will consume existing on-hand before passing through demand to components. Configure safety stock at the component level rather than the phantom level since phantom demand is transparent to MRP. When converting existing manufactured items to phantom status, review all parent BOMs to ensure quantity-per relationships produce correct component requirements after blow-through.

MRP passes all demand through phantoms to their components without generating planned orders
Existing on-hand inventory for phantom items is consumed before demand passes to components
Set safety stock at the component level since phantom-level safety stock is ignored by MRP
Use Supply Source toggling instead of Phantom Flag for items that are sometimes stocked

Frequently Asked Questions

When should I use phantom items versus regular manufactured items in SyteLine?

Use phantom items for sub-assemblies that are never stocked independently and always consumed immediately in the parent assembly. Common phantom candidates include wire harness sub-assemblies, pre-mixed material batches, and intermediate machining stages. Approximately 15-25% of manufactured items in a typical BOM structure are good phantom candidates. If you sometimes stock the sub-assembly for service parts or occasionally build it to inventory, keep it as a regular manufactured item with its own production orders.

Can a phantom item have its own routing operations in SyteLine?

A phantom item can have routing operations defined for engineering documentation, but SyteLine ignores the phantom's routing during production scheduling. Only the parent item's routing operations are scheduled and used for labor tracking. If the phantom's operations represent significant labor content, add equivalent operations to the parent item's routing to capture those hours. Approximately 40% of implementations define phantom routings for reference purposes while duplicating the labor steps on the parent routing for accurate scheduling and costing.

How do I handle engineering changes to phantom BOM items in SyteLine?

Engineering changes to phantom items follow the same ECO (Engineering Change Order) process as regular items. Modify the phantom's BOM through the ECO form, and the changes take effect on all parent items that reference the phantom during their next BOM explosion. This is a key advantage of phantoms since updating the phantom BOM once propagates changes to 5-50 parent items automatically. Implement effectivity dates on phantom BOM revisions to control when changes take effect across production orders.

Key Takeaways

1Configuring Items as Phantoms in SyteLine: Open the Items form (SLItems) and navigate to the Planning tab for the sub-assembly item you want to configure as a phantom. Set the Phantom Flag to Yes, which stores the phantom indicator in the item table's phantom column.
2Understanding Phantom BOM Explosion Behavior: When a production order is created for a parent item containing phantom components, SyteLine explodes through the phantom levels and adds the phantom's child components directly to the parent job's material list. The BOM explosion process reads the bom table recursively, detecting phantom flags at each level and continuing the explosion until non-phantom components are reached.
3Planning Considerations and Best Practices for Phantoms: Phantom items affect MRP planning behavior in several important ways. MRP does not generate planned orders for phantom items, so all demand passes through to the phantom's components.

Let Netray AI agents analyze your SyteLine BOM structures to identify sub-assemblies that should be converted to phantoms, reducing unnecessary production orders and simplifying your shop floor scheduling by up to 30%.

Talk to an Expert See a Demo

Related Resources

Infor SyteLine