We have multiple approved revisions on many parts. Each approved revision has an Effective Date specified. All of our parts have the “Use Part Rev” checkbox selected. For some reason, when MRP runs, it doesn’t always use the most recent Effective Date to choose the revision. It should, but it isn’t consistent. Has anyone else experienced this?
From the field help:
Use Part Rev
Select this check box if the Material Requirements Planning (MRP) should use the highest (most current) revision available of the part. If the check box is selected, an entry of the part number automatically specifies the most current revision.
If you clear this check box, you can manually create demand in MRP for different revisions of the same part, and the Epicor application honors the different revisions.
This option does not apply to requirements for stock. This check box has no effect if you do not use MRP.
Take a look at your part settings. Is the part set as non-stock? Is Process MRP turned on for this part? Be sure to check both the part Detail tab, and the part sites tab, in case you have specifics setup by site. Also look closely at your revs to make sure they have been approved. Can you provide a more specific example with some details we can dive into?
1 Like
Yes. Part is non-stock.
Yes. Process MRP is turned on for this part.
Only 1 site.
Both revisions are approved.
We have a job where there were 2 subassemblies that had revisions done and approved. The job selected the correct revision (the latest revision) for 1 subassembly, but the incorrect revision (the older revision) for the other assembly.
I had a similar issue at an implementation in 2021, (Epicor BOM question - how does it know which rev to choose if multiple approved revs and how does View/Pull As Assembly impact this? - #8 by Ernie) and I got from support that when MRP creates a job, the subassemblies will ALWAYS pull their most recent revision (by Effective Date) regardless of the “Use Part Rev” setting (which only applies to top-level parts). In our testing, that turned out to be our experience as well. In that situation, the customer wanted to control the revision on the subassembly on a per-order basis, which would have required a significant customization (we specced it out but they didn’t go for it).
Your experience is counter to that… I recommend putting in a ticket.
Here is a very specific example:
We have 2 unfirm jobs created by MRP on the exact same date, for the exact same Parent: RCC-245-72221 (rev K). Asm 5 on one job used rev B, while Asm 5 on the other job used rev C, which is the latest (the correct one).
What is the Need By/Ship By dates on the orders? That is part of what drives the revision.
We do everything make to stock, so there are not any make-direct links.
What are the MRP job start dates for both jobs? is one of them before the 6.25 date?
1 Like
Yes…one of the start dates is 6/13…we do backwards scheduling. The start date on the job impacts the revision that is used?
yes. One suggestion if you only want to build the latest REV is to set the effective date of the new REV to 1 day after the old rev. this will drive all suggestion to the latest rev
Can’t believe I didn’t think of that! It actually does make sense…I believe that is what we are dealing with.
Thank you!