I am (starting to be less) sure that the Receive Time value allows me to walk back the final operation due date of a job x # of days from the job due date.
Are there any other variables that do this as well? I am seeing jobs with a receive time of 3 days but the job due date and the final op due date are 3 weeks apart.
Look at move hours on the resource/resource group. I believe that will have that effect… but you’d see it on all operations that ran through that resource, not just the final operation.
Move Hours on the resource/resource group in question is 0.
Is it possible anything changed since the last time the job was scheduled? For instance, if you change receive time but don’t reschedule the job, it would still show the improper receive time. Is this an MRP job or manually created job?
It’s an MRP job.
We did change the receive time value recently but I would expect the receive time on the job to reflect what it was when the job was written.
I just tried manually creating a job and it behaved the way I expected.
Do you recycle MRP jobs?
We do not. We also auto-firm. This job was written on 2/2 after the change to Receive Time was made and then firmed the following morning.
Oddly enough, the spread in days is what I would expect to see if the old Receive Time value was still in place (15).
Are any of your materials constrained?
No constrained material, thank you.
