We have resources setup in resource groups. This is used to do very basic capacity calculations (number of resources in resource group x production calendar hours). Within a resource group, the resources may have different capabilities but we do not specify the resource on the route, when we schedule the job, it just takes the first resource in the list and adds all of the load onto that.
We have retired some shop floor equipment so in our test environment I deactivated the relevant resources, which is some cases was the first resource in the list, to reflect this. I tested booking labour through and in the affected operations I started to get error messages about inactive resources which would require the operator to chose an alternative resource to run the job on, which is a decision too many for our shop floor operators.
I quickly worked out what was going on and if I go to job entry | Job Details | Operations | Scheduling Resources | Scheduling Resources I can see the inactive resource is specified for an operation. Using field help and I can see the epibinding is to JobResources - a table that does not exist and does not seem to be queryable.
I can find no other way of querying which jobs have been scheduled to run on this inactive resource (not in jobop, jobopdtl etc) and the only fix I can find is to manually reschedule every single job (global reschedule didn’t do anything), which moves the load onto the next active resource in the resource group. As we have 100’s of jobs open at any given time, I’m struggling to see how I can find a window to make a resource inactive, without creating a ton of manual work.
What I would hope to find is a way of finding which jobs are scheduled on inactive resources and also the best means of quickly updating this via DMT.
Alternatively if there is a robust process for making a resource inactive and rescheduling the jobs that use that inactive resource on an active resource then I would appreciate knowing how to do this.