Skip to main content
Solved

Labor allocation on Phantom BOMS


claudematherne24
Jr Varsity III
Forum|alt.badge.img

I was hoping someone may have some insight to this question.  I am coming up with a large WIP variance in our Production Orders, and are thinking Phantom BOMs might be the cause.

 

At the parent level, we backflush material and labor.  We also exclude the Phantom, thus allowing us to bypass the move in the production order.

 

At the BOM for the phantom, we have run rates as if we were going to make a Production Order and backflush labor and material.

 

Is the WIP variance related to excluding  the phantom and thus not capturing the labor?

Best answer by angierowley75

I would encourage you to create an Idea (enhancement request) and detail your Use Case so this can be voted on and prioritized appropriately for a future release.

View original
Did this topic help you find an answer to your question?

5 replies

angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • 790 replies
  • April 10, 2023

What do you mean by you exclude the Phantom… can you provide an example / screen shot of your Production Order Details?


claudematherne24
Jr Varsity III
Forum|alt.badge.img

At the BOM, we chose Material Type as Phantom, then select Exclude as the Phantom Routing step.  This allows us to not have to make a extra move transaction.  We see material consumption still occur, but it seems like the labor of the Phantom BOM does not get captured in the Production order, leaving us with a large WIP Adjustment at the end of the Production order.

 


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • 790 replies
  • April 13, 2023

I believe you’d want to include the Phantom Routing so the labor of the Phantom operation can be back-flushed.

You don’t need to report on the ‘extra’ phantom operation - reporting on the succeeding operation will trigger the backflush.


kristianharianja
Semi-Pro I
Forum|alt.badge.img+3

I hope that there is one more option to exclude the parent operation but using the child operation in the production order. The current routing Exclude is excluding the child operation and only using the parent operation.

Yes, we can choose include options (before or after) but this will result in many unnecessary operations in the production.


angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • 790 replies
  • Answer
  • April 19, 2023

I would encourage you to create an Idea (enhancement request) and detail your Use Case so this can be voted on and prioritized appropriately for a future release.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings