Can anyone please clarify that in a make to stock environment MRP and Inventory treat all revsions as the same.
eg Sales Order = Rev B but the latest approved Rev is A - MRP will create a Job for A.
eg We have 2 Jobs for the same Part - Rev A & Rev B - when both complete and are received to inventory Epicor does not differentiate the revisions and again MRP will not differentiate the revisions.
Track Inventory By Revision is part of a module, maybe Advanced Printing and Routing. If you have the module, then you can turn on inventory by revision in Part Entry.
@nateS I believe that is standard for everyone now.
@rppmorris , you are generally correct. The one thing to note is what you described is what happens if Use Part Rev = true. If that field is false on a part, MRP will create the supply based on the demand source.
The Track Inventory By Revision functionality is for all parts; make to stock, order, and job.
Do you mean for a Subassembly? Just want to make sure.
If you want to assign revisions to subassemblies in your method, I believe you have to turn on Track Inventory by Revision. Not 100%, but believe that is what will allow you to select the revision on methods.
Actually, your assumption is a little off too. There are a couple of things that would trigger MRP to select Rev B.
First, if Rev A is not approved, MRP will always select Rev B.
Second, if both revs are approved, the system will use the effective date to determine which method to choose. If the effective date for A is 1/1/2025 and the effective date for B is 1/1/2026, the system should select A until the demand for the subassembly has a date 1/1/2026 or later and then it should select B. It has been a while since I tested this, so I could be wrong. I would do your own testing to make sure.
Whilst i am not 100% sure i agree with you, in any manufacturing business you are always going to need a little bit of manual input. You also have to remember that when MRP runs, it only creates suggestions, purchase or manufacture, based on the data it knows. Someone still has to ‘Firm-Up’ those suggestions OR ignore/change/delete them.
Yes, I definitely agree with that. The only thing I would hesitate to say is which rev it would select. When everything is equal, I am not sure how Epicor determines the one to select. Just thinking out loud, what if B was created first and then A was created? Not sure what would happen there, I would assume A, but can’t say for sure.
Not using Track Inventory by Revision makes this true. Here is a video of a Part that has Track Inventory by Revision as true and has multiple revs. You can see in the tree that when rev 0 is selected (which does not have a method) the details disappear.
Edit: This recording is from Engineering Workbench
What is galling is the number of ERP reference visits I have done and continue to do, largely promoting Epicor.
I know of at least 6 reference visits that turned into almost immediate sales but that is only in the last few years because my memory over the 15 years using Epicor isn’t perfect.
The latest Epicor reference visit was yesterday, I spent 6 hours with a Company that has recently gone live and were looking for some support.
Probably the most disappointing element - I absolutely expected 1) that this enhancement would come with a cost and 2) to be treated this way.
My experience with Epicor in the UK in terms of vision and strategy, get a PO.
