Phantom BOM \ UOM Material Consumption

We have recently been reviewing our procedures to book out each part as we manufacture it, instead of at the end of each shift. As we have experimented with this in our test system we have noticed that the job costs are highly inflated if we book out 1 part x 10 times instead of 10 parts once.

After some research we have found this in the Help: ‘When a part is designated as a phantom, the Epicor application moves all related operations and materials up a level in the bill of material for the end item, and this assembly part number disappears’. We believe this is where the costs are rounding up as the part that consumes the Phantom BOM has a UOM of EA1 (which only allows integer transactions as it is for fully manufactured whole parts), however the Phantom BOM has a UOM of KG as it is all raw chemicals.

We are unsure of a way to work around this as the Phantom part cannot exist physically - example BOM below. Any suggestions on how we can set this up to consume the materials correctly?

Or does anyone have any idea why the UOM for Phantom BOM’s are ignored before I raise an Idea for this?

Thank you :slight_smile:

1 Like

Update on my testing… the calculation below shows one of the materials listed on my original post but transacted in 2 different jobs for 2 different parent parts.

The Phantom BOM Part number that the materials are in is set to KG. The Parent part for the Phantom BOM part is set to EA1 (whole numbers only as for inventory we can only have whole manufactured parts).

IssuedQty = RequiredQty / RunQty * QtyCompleted

I understand we will have to find a way to work around this but if it does affect anyone else then I have raised an Idea for it - Log In - Epicor Identity