Can't Close Job - A valid job number is required

So, we have an open job… shows up in Job Entry… went through production, no issues.

Demand was against an Order… that line was shipped on 7/9/2024 and closed.

Final Op completed.

Now trying to close the job in Job Closing… whether I type the JobNum in manually or click on it in the grid, we get an error that “A valid job number is required”.

It shows up on the landing page grid… its obviously THERE. Its even flagged as a candidate for closing. But the JobNum won’t be accepted for some reason.

Thoughts? Never seen this behavior before.

Did you try completing the job first?

You do that IN Job Closing, don’t you?

Oh yes… if you’re referring to my first image… we generally ship from the job and not worry about “final op” etc. I DID go back and throw in a time entry against the final op… Job Entry now shows complete:

image

… but didn’t make a difference. Still can’t open this job in Job Closing.

Is Clear Client Cache still a thing in kinetic?

e: although I assume someone else already tried to close it which is why you are trying to close it now.

2 Likes

I jumped into the Client and classic form (errors there provide more detail)… here’s what it is saying:

image

The NEXT job: 5-5050-13 opens right up. But 5-5050-12 is stuck.

Perhaps corrupt in some way. I can enter a case, perhaps need a datafix. Just wasn’t sure if anyone has come across this before.

The error says table:JobAsmbl. If you open the job in job tracker, can you see an assembly on it?

1 Like

Are you in the right site?

1 Like

Yeah, full capital equipment job build… MANY assemblies (0 through 190+).

1 Like

Single-Company, Single-Site

I’d try closing via DMT, but if that doesn’t work yeah it looks like you might need a datafix.

Good thought… Checking with my CFO whether he was looking to make any changes IN job closing during his process.

I’ll try DMT once I get those deets. See if I can back door this SOB.

1 Like

No, I was referencing the Complete check box in Job Closing. There are 2 different functions in Job Closing, Complete and Close. I was wondering if you got the same error when you just tried Completing the job.

Gotcha. Yeah, the problem is I can’t even load the job IN Job Closing. So I can’t even get to those checkboxes.

1 Like

Gotcha. I actually have seen this before, but don’t remember what the problem is. There is something wrong with one of the assemblies. Wish I could remember what the problem was, hopefully it will come to me later.

1 Like

WELL IT BETTER COME BEFORE I OPEN A CASE!

hahah… chances are you’ll come to the conclusion before they do.

OH!! Maybe you’re hitting on something. I believe this order shipped… then our CFO wanted to add additional cost to the job (post-engineering hours?)… so I see our planner ADDED an assembly with some engineering operations so our engineers could continue to enter time.

Let me look at that assembly… could be the culprit!

1 Like

Check the quantities. That asm might be 0.

No, you can’t have a a subassembly set to 0. (I just tried to change it, haha… got smacked down).

I just put in another time entry on that subassembly so I could complete the qty of 1.

Still failed.

DMT… no bueno.

image

1 Like

Ok one last thing to check. The method in your error is JobOperAfterGetRows. Did a quick search and found someone who was running into an issue releasing a job. There was a JobOper with no parent assembly: Unable to release a job. Receiving error "Record not available" - #3 by dgross

2 Likes

Is it marked as Make Direct?