Skip to main content

Anyone in community using BOM’s with Phantom Items?

How does it work for you? What settings work best in your manufacturing facility?

We have multiple items with BOM’s with component parts and subassemblies and we want these component parts and subassemblies to have their own BOM. However, we don’t want to have to MOVE all the component part and subassembly Work Orders in order to process the Parent Item Work Order.

If Phantom Items will work, what is the best way to set these items up?

 

We use Multi-level BOMs with Phantoms basically like this. We create the Work Order for the Final Finished Good and then utilize the generate linked work orders (under Actions) Acumatica will then generate all linked orders at every stocked and controlled item linking it via the Parent Order Number (ie WO#001)

 

Final Finished Good WO#001

-----------→ Stocked & Controlled Item WO#002

--------------→ Phantom Item

--------------→ Phantom Item

-----------→ Stocked & Controlled Item WO#003

--------------→ Phantom Item

--------------→ Phantom Item

-----------→ Stocked & Controlled Item WO#004

--------------→ Phantom Item

--------------→ Phantom Item

 

Hope this helps a little. 


Do you need to have separate work orders for each sub-assembly? If not you can accomplish this by putting the sub-assembly(s) on the BOM for the finished good with a material type of “Phantom” instead of “Regular” and set Phantom Routing to “Before”. (We backflush all labor and materials.) When the work order is created there will be an “operation” for each phantom (with the associated parts and labor) and for the finished good. We do a Move for the final operation and all the prior sub-assembly parts and labor are pulled into the finished good.

We like the ease of a single step for the Move and fewer work orders in the queue. Hope this helps!


Just an additional note - any inventory item with a BOM can be used as a phantom depending on the application or can be used as a traditional stocked item. This was an adjustment for us as our prior ERP required the item itself to be designated as a phantom. In Acumatica the use as a phantom is specified on the BOM (or configuration if you are using the configurator module). We now can use the same part and BOM both to build for stock and to blow thru as a phantom.


@cmoreland 

hi, some of our work orders are set up like this. we are not yet Acumatica customer and trying to explore into it.

so, when you received the parents WO#001 as FG into the warehouse, do you back flush WO#002, 003 and 004? how do you handle WO#002,003 and 004?

thank you Zoey

Final Finished Good WO#001

-----------→ Stocked & Controlled Item WO#002

--------------→ Phantom Item

--------------→ Phantom Item

-----------→ Stocked & Controlled Item WO#003

--------------→ Phantom Item

--------------→ Phantom Item

-----------→ Stocked & Controlled Item WO#004

--------------→ Phantom Item

--------------→ Phantom Item


One question that comes up with Phamtoms when you choose to use the Exclude Phantom Operations is how to group the components of the phantom on the Production Ticket Materials.  The AMProdMatl DAC has two columns which can be use to get to the subassembly bill and subsequently to the inventory item itself: PhtmBOMID and PhtmBOMRevisionID.  Those columns are always populated for the parent item also.


Reply