This is the one use case I know of where you’d use a phantom and NOT a subassembly. It came up on this ticket, but I didn’t explain it there because the OP said no phantoms.
In the pic below you have the method (includes the part “MyPhantom”) and the Job (that part is nowhere to be seen.
Why?
Because perhaps you want to use the same exact list of materials but in different work cells.
Thus I made
- The BOM part to be a phantom with no operations
- A subassembly part (not phantom) that has the workcell operation and a single material that is the phantom.
When the job is created (normally - via get details or MRP - no human intervention), you get the BOM assigned to right cell (op).
