Ok all you MRP experts.
We made a change on an MPS and MRP Net Change did not catch it.
What changes on the following with a MRP Net Change catch?
- SO Dates
-SO Qty’s - PO Dates
- PO Qty
-Job rescehduled - MPS Change
etc…anything else you can think of.
I am certainly no expert, but we always run the MRP Recalc Needed before running a Net Change MRP. That process catches the changes made to parts, Jobs and Orders and sets a flag so that when the Net Change MRP comes around, it sees that there has been a change and acts on it.
1 Like
How long does that take to run? Do you feel it is beneficial to run every time before a net change?
It takes less than 15 minutes for us, but I think it will depends on the number of parts, orders, jobs, etc. in your system. We feel it is required to run that process before any Net Change MRP. Without running it, we would see the same results you listed. Changes would be made to a part, an order or a Job and nothing would change.
1 Like
There is a field in the PartPlant table called PartPlant.MRPRecalcNeeded that is either true or false… if true, it will be analyzed during Net Change.
This field is SUPPOSED to be turned true for any parameter or value change that would change the MRP results. Example: I KNOW that changing a sales forecast WILL turn this flag to true.
All that said, as @DavisStd1 suggested, you can run the “MRP Recalc Needed” process which rechecks a bunch of things and sets the MRPRecalcNeeded flag to true if it needs rechecked.
The GOOD thing about net change is that it reduces how many parts MRP will examine… but One problem with the entire “net change” concept, is that that “Since full regen was run” it is now “tomorrow” and the next day… if you ran MRP with a cutoff date of the end of the week… 5 days later, the end of the week is now 5 days later (sorry… gets confusing)… and new orders are now within the view of MRP, but net Change will not examine them because nothing changed. The “MRP Needed” process re-examines the parts to determine if there are new demands within the view that were ignored with previous MRP runs.
2 Likes
So we removed all MPS and I am running MRP Recal needed the night before the MRP NetChange Run.
We have some SO that they change the Part Num (development reasons) and the NetChange Run did not run that part.
Any reasons why the change in PartNum wouldn’t be caught?
Honestly between all the experts and Epicor there seems to be different answers on MRP Net Change and i don’t trust what it is really catching or not to run for MRP.
Thoughts?