Hello Everyone,
Is there a way to see who changed what and when for a job?
Or can I make this function using BAQ?
Any help would be appreciated.
Yes make a data directive on jobhead, jobmtl, jobasm. Use the change log widget.
1 Like
We’ve used Prevent Changes and Create Audit Log in the past. It’s in Company Config > Modules > Production.
If a job is engineered, you have to uncheck engineered and then are prompted to put in a change note when you checked engineered again.
You might get people who just put a “.” in the change description put that’s not a software issue 
. A job has to be engineered in order to schedule. I’ve always suggested a job should be rescheduled if you are adding material or operations anyway. Seems to keep demand and scheduling cleaner.
Jenn
Just adding my unasked for two cents into this topic as well. Try and identify the fields that are important to change log and don’t just change log everything. It’s important to know that although adding a record to the change log isn’t strictly time consuming, it does take time/processing power and having enough fields in there will impact performance.
1 Like
I concur with activating a change log. It’s the only way to truly capture not only who and when a field was changed, but also documents both what the value was changed from, and as well as what the field was changed to.
Be selective as to what fields are important to track. If too many fields are tracked (i.e. just selecting every single field on the different tables in Job Entry), then the system gets overwhelmed and some of the changes won’t be captured every time - especially true in older versions of Epicor.
Then you can run the Change Log Report for the specific tables every day to review all the changes that are occurring (instead of merely waiting until well after the fact to realize something changed); or you can even set up automated alerts/emails when specific fields are changed.
As well as still being able to review what changes were made to specific jobs via the change log on the Job Tracker/Entry screens.
All the Audit Log does is require people to un-engineer the job prior to making changes, and relies on them typing in what they changed - which almost always falls short and ultimately relies on a person’s memory when approached later.