In any case I’m trying to chase revisions. We don’t do a good job controlling revisions and I’m trying to see what all is available or what is the best way to get going, with minimal information to start with.
The purchase orders are set up with a revision, so theoretically, EPICOR should be able to tell me what revision of what part is at what location, right?
I’m trying to get a handle on what parts do we have on hand with multiple revisions.
If multiple revisions are all at one location, I’m going to assume that EPICOR is auto set to FIFO, so it’s controlling revisions at that location by that.
For parts in multiple locations, where rev A is in Aisle B, but rev B is in Aisle C, the system should be able to tell me that right?
My worry is that it stops tracking revs after receipt.
For example, we received 10 in in April and Rev A and 10 more in in June at Rev B, and i’ve pulled 5 Rev A and 6 Rev B ( on accident). Since I’ve pulled more than the previous revision receipt of 10, it’s going to tell me I only have the new revision in stock, when really I would have 5 of one revision and 4 of the other…
Thoughts? suggestions?
I wish Part Transaction History would give me revisions or show me what it’s doing with them at least.
I know newer versions let you track inventory by revision, but I am of the opinion that if something isn’t 100% interchangeable with another piece, it should be a different part#.
Having said that, we lot track basically everything in our inventory, so it’s possible for us to trace a piece back to a specific revision via the job or receipt. However, breaking changes are still rolled into a new part ID.
What exactly do you mean by this? Are you not adding the correct rev to PO’s and receipts? Are you doing a poor job of managing changes to the revisions themselves?
The Track Inventory by Revision shows a lot of promise… but it’s still pretty buggy…
It is a new feature first implemented in 2023.1, and I tried to implement it but found these problems:
LOTS of folks chimed in on that, and as yet I’ve not heard of a complete solution to the problems.
Apparently It’s best when added during an implementation (meaning BEFORE any part transactions have taken place). I have not yet had it function successfully on anything other than top-level manufactured parts.
PLEASE let us know what problems you find.
That is NOT true. Epicor does NOT do any filtering on stock levels out of the box.
That is the desired functionality of Track Revision by Inventory.
Again, this is the desired functionality of Track Revision by Inventory. Without that working properly, Epicor does NOT track part revisions for inventory transactions.
Thanks John. Interchangeable yes, but I’d still like to be sure we’re pulling the oldest, not latest, revision of the part first. If I have Rev A at one location and Rev B at another and when my material handler goes to pull a part, he picks a location to pull from. I’d like to be able to give him the knowledge of what rev is what and realistically the only way for me to do that at the moment is tag every part in the warehouse with a revision and somehow document whether a part has 2 revisions available in stock right now, or not.
As mentioned, I’m certain I have multiple parts in the warehouse with more than 1 revision available. I’d like to pull all old revisions first, but I’d like something to tell me that I have multiple revisions available, without doing all of the manual work.
If that makes sense.
Yes, put your old revs on top. Yes, find a designated location for new revisions.
Some things we’re better at than others and this is not one of them… yet.
Thanks Ernie.
I’m still reading through your thread. I believe we have some updates coming that upper management is looking into. I’ll try to keep this at the forefront so maybe we can get this all sorted during that EPICOR change/update.
@Sommer3M If you are not using lot FIFO and just FIFO there are some oddities that can happen between bins and FIFO layers. We found this early on and only do Lot FIFO. I want to get to rev control, but have a workaround using the lot first reference date to keep fifo sorting.