I just figured this out and wanted to post in case anyone else could see a need and wanted to play around with it (I’m thinking ETO folks).
If you do a Part.UpdateExt on PartRev to mark a revision approved WHILE IT IS STILL CHECKED OUT in engineering work bench, MRP will create a job for it. I am guessing that you have to have checked the part in at least once for this to work.
I am going to continue testing it’s use to see what can be done and I will post updates. If anyone else tests it out and finds anything, please feel free to share.
I have no idea what this might do to other areas in the system. Don’t do it in Production and if it breaks something, it is not my fault.
Additional Findings:
The Revision DOES NOT have to be Approved in the EWB.
MRP will recycle Unfirm jobs.
If the part that is faux approved has edits done in EWB, the part has to be checked in for MRP to pick up the changes.
This sounds like a bug rather than a feature. At least, I hope it is, otherwise a dashboard could bypass a lot of rev control + compliance stuff I’ve put in place.
Thanks for the heads up. I don’t think I’ve built anything that could exploit this, but I’ll double check.
Well, isn’t that what every UpdateExt method is, a bug?
I am purposefully doing this because my current company (and unfortunately, others before it) want to have a job be created before they finish building the MOM. Trying to see if I can bend the rules to get around the settings in Epicor.
I think there should be tighter integration between Jobs and EWB. Allow Jobs to be created for un-engineered parts but have a mechanism that does not allow the job to be firmed until the WB is checked in. Or something like that.
Additional Findings: