False Demand

I have a part that is generating false demand. The work order that is showing up in demand is a closed work order that has been issued complete. I’m not sure why this is happening and I can’t figure it out. I queried it, checked time phase, and also reviewed the part setup but nothing is looks out of the ordinary. Anyone have know what may be triggering this?

Hi Jessica,

Is the job marked Complete?

Mark W.

Yes sir :slight_smile:

What does Part Tracker > Warehouse show for Demand?

Try Refresh Part Quantities and Allocations on that part?

2 Likes

I already tried that and it didn’t work this time.

nothing

Hmm. If you query JobHead and JobProd for that job in a BAQ, does it match what the trackers say? (Quantities match to what you expect?)

Mark W.

In your screenshot in the Demand pane, what does the rest of the Source column read for the Job number? That Job should be what is driving your demand for that Job.

The job is marked complete and closed… The material was all issued complete as well… I have about 4 parts that are like this that I know of. I have checked everything and I cannot find a pattern.

Yes

What does the sales order for this part look like? Is this part a stock part or a non-stock part?

stock part… theres no specific SO for this part.

Is there a MIN set up for the part?

no, I checked for min, max, etc… Nothing is set up for that part.

Jessica,
So with what your screenshots show, this part should show up on that job on material Seq 310 on that job, do you see that seq on that job and is it this part number in Job Entry\Tracker?
Also check for this part in the the PartDtl table and if it’s there what Job & source it references, should be the same job as your screenshot.
Do a BAQ on that table looking for either the Source Job number or the Part Number.
Job Manager & Time Phase get their data from PartDtl, but TimePhase I think has a join that confirms that contents in the PartDtl exist in JobMtl or wherever.

The Refresh Part Quantities & Allocations that @pmarques mentioned should have recalced the PartDtl… you sure you ran that and you ran it in Report & Update and not just Report mode? It defaults to Report Mode. Make sure you set the Filter tab to only be this part number.

-Rick
www.getaligned.solutions

3 Likes

Rick, I took your advice and you were correct the demand show a suggestion for mtl seq 310 but the job didn’t have 310 listed for that part… it was listed as just mtl seq 10. I corrected everything and re-closed the jobs then ran MRP for those parts and everything cleared up.

Thanks,

Jessica,
Awesome… hope it doesn’t happen again… It’s concerning how this happened… is there a bug in there somewhere? Did Mtl Seq 310 ever exist? How did 10 end up as 310 in PartDtl? Was 310 deleted and PartDtl didn’t update… If you run into this again you might want to report it to Epicor Support, probably a bug.
You can probably modify your BAQ to just show you ‘orphaned’ PartDtl records, so you can keep an eye on this if you want.

-Rick
www.getaligned.solutions

Does anyone know if Epicor has a fix routine for this issue? it seems to be coming from re-engineering a job and then closing it before running MRP again.

Where do I find this?