In a query for production control using the JobHead table we noticed a true/false field called JobHead.JobHeld. The definition of the field is “Indicates if the Job has been placed on “HOLD”. Currently this field is only used for display purposes. It may be used later to prevent or provide warnings and messages in appropriate areas such as Shipping, Purchasing, Labor processing, etc.” We added the filed to the query and are surprised that many of our jobs are flagged as true.
How / where do you turn this flag on or off?
I don’t think there is a flag for that. I couldn’t find one at least. I just created a Data Directive that for all new JobHead records JobHeld = false;
What is the purpose of your data directive, please?
Hi Kay! Tried using that field on another project and we had all sorts of unexpected results – sometimes worked, sometimes didn’t, stopped shipping, etc. Seemed like it was only partially developed. We ended up using UD fields so we knew what it was doing. Actually used multiple fields to be able to track different types of holds.
Hey Jeff, But why do some on my jobs show on hold and others do not? How did this happen?
Should I try to change them using DMT if there is nor other place to set this flag?
Not sure why some would show as on hold. This was the sort of inconsistent behavior I saw previously. There are a number of unused, “for future development” fields across the tables. Best just to leave them alone so when they do get fully developed they don’t break something you were using them for.
To default a job to not on hold. MRP jobs are otherwise defaulted on hold at least on our current version.
I could not find a pattern as to whether jobs created from Job Status Maint recommendations or QuickJobEntry or Job Entry had the flag set - seems to be random. Any idea if changing the flag results in anything happening or not happening?
I’m not aware of that field serving any functional purpose in the system. I just checked the 2022.2 instance we have here and the field description has actually gotten worse.
You could put a change log on it and see how and when it’s getting set, but my guess is that they are all created on hold, and for whatever reason someone is taking some off hold thinking it’s a problem (because logically one would think that)