Can anyone please explain the difference between the “locked” column in Adjust Global Scheduling Order and the “locked” field in Job Entry (JobHead.SchedLocked)?
We’re seeing “locked” Jobs in the Adjust Global Scheduling Order grid and they are not locked when checking Job entry.
This is resulting in these “locked” jobs not being rescheduled as we’d expect.
(and “Ignore Locks” has no impact on global scheduling)
I am looking thru the training & tech ref guides but so far… haven’t found an explanation for where the locked values are pulled for jobs in the Adjust Global Sched Order grid.
Steps…
1.) Run Calc Global Sched Order
2.) Run Adjust Calc Sched Order - AND - copied all the “locked” jobs to Excel.
3.) Run a Dashboard listing all “Locked” Jobs - copied those to Excel
4.) Compare Excel data - identify 4 jobs where
— Job Entry locked NOT = True
— Adjust Glob Sched Order “Locked” IS = True
5.) Ran Global Scheduling - selecting “Ignore Locks” and highest logging level.
Result: 4 jobs from step 4
were not listed in the global scheduling log.
AND… now when I check them in Job Entry they magically show as locked???
Hmmm… maybe always did this for certain jobs & I just never noticed before this?
There is also the possibility that the priority level has something to do? Like high priority will be reschedule to the earliest available date and then lock it so that next time it runs it won’t be moved?
After Epicor verified that the “Locked” values in shown in “Adjust Global Scheduling Order” are pulled directly from JobHead, and I verified there are no BPMs or custom code involved.
I retested everything (Test) and am no longer able to duplicate the issue.
I will monitor Live for a while longer just in case but… seems to have cleared itself for now.