Hi All,
Hoping to pick your brilliant brains again. We have noticed several jobs are not getting scheduled (i.e. they are not getting picked up at all by the scheduling process, and are missing start and due dates). This is not consistent within a part - the same part can have some successfully scheduled jobs, and some not (same revision, and some times even the same required by date). These jobs do not appear in the global scheduling order or the scheduling log.
When I try to manually schedule the job via backward scheduling, with finite capacity selected, I get the error message below. When I try to schedule it with forward scheduling (finite capacity still), I get a warning that I will miss my req date, but it still successfully schedules. THEN, when I try to go back and backwards schedule the same UF job (after a successful forward schedule that populated the dates), I am then able to backwards schedule. I saw another user reported this error, and I tried to troubleshoot according to the suggestions on that thread, but I was unable to resolve the issue. I suspect that the issue is tied to the fact that we are set to backwards scheduling but we are at full capacity, however, I expected the job to just be scheduled past the req date, not live in limbo as unscheduled.
Any insight would be greatly appreciated!!
This is the error message we are seeing:
Application Error
Exception caught in: Erp.Adapters.ScheduleEngine
Error Detail
============
Message: Nullable object must have a value.
Program: Erp.Adapters.ScheduleEngine.dll
Method: MoveJobItem
Client Stack Trace
==================
at Erp.Adapters.ScheduleEngineAdapter.MoveJobItem(Boolean& l_finished, String& c_WarnLogTxt)
at Erp.UI.App.JobEntry.Transaction.scheduleJob()