Guessing here…
What you’re looking at on the Part Tracker is an embedded dashboard, probably calling out something in the PartBin table. If you look in the Data Dictionary for that table, you’ll find a RevisionNum field.
How the logic works and what is required to make the functionality work in Classic is beyond me. The last time I tried it (in Kinetic, just after 2023.1 was released) the bug I described at the top of this thread had not been fixed.
Same issue here. Ughhh
Using DMT to upload parts for NEW system in preparation for cut-over to LIVE, had to clear all checkboxes for tracking to update Revision and Attributes.
Created Sales Price Lists via DMT prior to finishing up with setting the checkbox back to Track By Revision, and now receive this error. The Price List addition created PartTran records so now cannot Track By Revision.
I believe, but not tested yet, that we will now need to create Custom UOM Conversions to use the standard UOMs of EA and every other one.
I wish we were on-Prem and could do so much of this easier and faster via SQL, though not recommended, sometime is needed. Head-hurts now…
Stumbled into this one because I thought wow that sounds exactly like the problem we’re still having, only to realize that this was probably posted during our implementation (hi @Ernie !)
For some background, we originally had DMT’d most of our part MoM’s in before this feature was added. We then tried turning this on for all manufactured parts in the system (including subassemblies) but after having significant problems with Jobs after turning it on via the BPM Ernie mentioned, we managed to turn it back off or rolled the DB back to before we made the change.
What was odd was that newly created parts, where the flag was on from the beginning, did not have these issues, which lead me to believe that something wasn’t set properly…somewhere…
After much back and forth with Epicor the last year, what appears to have been most of the issue was that because we brought the MoMs over, then turned this on, was that the Revision field on the PartMtl table was not actually populated. This was the cause of the many issues we experienced about either missing attributes or revisions, but primarily the inability to ‘get details’ when creating jobs.
This was further obscured by Method Tracker and Engineering Workbench showing a revision on the screen despite the record not actually having one set. What was suggested I do is change out subassemblies that also had tracking turned on with some other part, then change them back to get the rev to properly populate. After testing this, I was able to get details on tracked parts with subassemblies that were also tracked.
So far so good, but there still is a particular situation that is giving us grief. If we have a Tracked part, with an untracked subassembly, it is impossible to take a completed quantity when ending an activity on that subassembly. This throws a similar ‘missing attribute’ error as others have mentioned here. We have to end activity with zero qty and then do some kind of adjustment to get the numbers in there on the few parts that got setup in our live environment with tracking on before I could prevent its use. This does not occur when ending an activity on the top level part. This also does not seem to happen on parts where the subassemblies also have tracking set that went thru the ‘change part/change back’ process I mentioned above. I’m still trying to run this issue to ground with Epicor, but will update here if I learn anything else.
@Ernie Did you happen to keep a copy of that BPM around to mass update the flags? I’m going to try looking in some of the backups from around Mar 2023 to see if I can find it, but thought that if you kept a copy that might be quicker/easier to get.
Hey @JaJuJo! The royal “we” in my original post was indeed “you”…
I don’t have a copy of that BPM, but I THINK it had two steps:
then I ran a DMT that updated the Track by Revision field so it kicked off the BPM for every part.
Use with EXTREME caution… I broke your data once before with this!
Same here, still dealing with the clean up.
Does anyone here have had this issue where setting the MRP Planning by Revision on part brings an error: System Attribute Class “zInventoryTracking” has not been enabled for MRP, can’t set MRP Planning by Revision to true.
I do not know what to do there or where this setting is. All the parts are revision-tracked and conversion is done, but I cannot set MRP for this. Any good idea what to check?
Well, the answer is here: Knowledge Search Articles - EpicCare