Phantom BOMs & Operations

I understand what you want. I’m just saying the system isn’t built to handle the way you want it to be handled. So you’ll have to customize to be able to do what you want. Out of the box, there isn’t a workaround.

The delights, I suppose I was anticipating that ‘eureka’ moment where someone interjected and declared this is absolutely achievable. It’s disheartening that it’s not. :frowning:

As others have said, PHANTOMS always include both the OPERATIONS and the related MATERIALS. This is different than other systems my work, but in my experience, this added feature can really help out in some engineering worlds.
for example, using the “bike” example, you can have a BOM/Routing for how to assemble a wheel with its tire… you can also have assembly instructions for how to assemble the frame, which also includes the wheel.
What Epicor will do is if you have the wheel as a phantom, then it will rollup all the labor and material up to the upper BOM at the time it creates the job. It will INSERT ABOVE, all the operations… therefore the wheel assembly will be completed before the frame.
NOTE that in your question, you state that you sometimes may make the assembly (to stock) while other times you want it to be a phantom… THIS is a problem for Epicor. You basically cannot have a stocked phantom. The system. always considers the part as a phantom if it is marked as a phantom. Therefore, if you want to stock it, you need a second part number that would be the stockable item, and that stockable item would need the phantom as a component.

2 Likes

Thanks Tim, appreciate the detail.

1 Like