I like to update threads when I discover a solution to my problem. I’m not sure how widespread this issue is, it may not apply to V9, but in 10.2.400.10 if you have a job released and an individual had clocked into it and worked on it, maybe just the first OP or the first two, no labor on the “last OP” and no completed qty on the last OP either. If you go to Job entry and un-check engineered to perhaps add an additional operation, or materials, when you do that the job is tagged as a candidate immediately. I found this by adding the Engineered box as a change log event for a different purpose, but I also added Candidate and Job Header Completed QTY as logging events, that’s when I noticed this on a job that was showing up as a candidate.
Seeing as how the Candidate check box is not user editable this shows there is a program glitch somewhere. I also noticed on jobs where there was a Sub Assembly with a completed qty on that, last OP on the SA was not tagged as last OP either, It would take that completed qty from the SA and post it to the job header.
Epicor has taken this problem to Development and we’ll see where it goes from there.