Hello,
Maybe a simple question or maybe not. We run Global schedule every night. How can I view the changes its made, currently my only mechanism is exporting all jobs prior to global running then comparing the dates after its run. Is there a report I can run, a log file ect?
Thanks
I guess you could turn the change log on for JobOper, but I would be scared to try that.
IIRC - there is a “previous due date” or similar on the Job Oper table. Maybe just set a DD to shift the previous date into that field…
Thanks for the suggestions. I do not see anything relating to a previous due date on the joboper table.
It seems surprising there is no record of what global schedule is doing.
When running there is a “log file” field. Would this contain relevant information, if so how/where is this accessed?
I believe that only exists in the MRP/Scheduling engine to hold the old date while the new one is not locked in yet.
Yes, you should see the old dates in the job specific logs if you have detailed logging turned on.
yep - I was incorrect. Maybe I was thinking the WI* fields in the table are for What If scenarios and could be used for this?
Do you have any more information on this? I did have a support ticket which we ended up closing determining there was not an existing mechanism.
The screen shot below is the output of a log file. It seems to indicate the job was unfirmed and scheduled but no record of previous date.
You need to capture the detail logs. There ends up being one file per job.
Is this separate then “Log Level” assigned via global scheduling window?
You need to select Process and Scheduling.
The screenshot I provided was with process and scheduling selected; at least that was my intent its possible I neglected to change it. I will run again once production ends for the day to verify.
You will have the process file that is the overview of the whole run and will be named whatever you called it in the Global Schedule. You will then have 1 file per job and each file will be named the job number.
John, yup got it! I discovered that this morning the individual file was what I was missing before. I see the log file, can se the original date and the date it changed to - perfect!
Ill look through the log file a bit more. Its significant for a single job. Is there a particular location in the log I should be reviewing as to why it did what it did? It appears most of the log is going through each and every possibility until it found one that worked, generating almost 6k lines of text…
Correct, it’s a lot!
If you search on this site, you should be able to find some creative things people have done to extract data from log files. I don’t know of any specific ones that you might be able to leverage.
As for figuring out what the engine is doing, I would select a job that gave you results that you were not expecting and then go through that log to see how it made it’s choices. There are so many variables that effect the engine, it is really hard to say go look here.