Epicor revisions don’t seem to have effective date ranges.
How do companies handle the situation where we plan the current revision A to go out of production, say October 31.
We have next revision B ready, an effective date of 11/1 and we want MRP to suggst future jobs after 11/1 to be using Revision B and its BOM.
How are other people achieving this?
Epicor appears to use the earliest approved effective date and ignore the others.
And you can’t expire revisions, other than unapprove I guess.
Yep, we do this. We’ll have 2 approved revisions and the newer one kicks in at a later date. It works well.
FYI the date you want to care about is the ReqDate on the job-head or the sales order release - not the job start date or anything else.
1 Like
Jason - truly?
It has not been our experience.
If I have Rev A, effective now and Rev B effective Nov 1, and I have demand in November, it will use Rev A on the unfirm job.
Is there something we’re not doing correctly?
Thanks for the reply.
Well, It looks like I have none to look at in Production at the moment. My memory says this worked great, but I don’t have a way to prove it until I set up a test.
1 Like
it should work as @JasonMcD says… it looks at the Required date on the job, and compares it to the EFFECTIVITY date on the part revision. if the required date is after the effectivity date, then it uses the new revision.
you are correct that we dont have an expiration date… but the effectivity date acts as an expiration for the previous rev. when the new rev effectivity date happens, it basically supersedes the previous rev.
1 Like
I refreshed pilot, and planned another test, using a part with no demand, no on hand, no min/max.
Just a handful of monthly jobs to fulfill the Forecast quantity. Looking at the unfirm jobs, out to end of year, they all used the old revision.
Created a new revision, copy of the old one with different materials, used Effective date of 10/1
Created a sales order with release Need by of 11/1.
Ran MRP in net change against this part.
The unfirm jobs up to 10/1 kept the old revision, all unfirm jobs past 10/1 now had the new revision.
This is great, and thank you very much.
I know we tested this a few months ago, were disappointed with lack of success, must have done something incorrect in there somewhere.
But now for more tests, appreciate the help.
1 Like