Before I open a ticket, I was wondering if anyone has contacted Epicor about load not being removed from completed operations. I would expect that when an operation is marked as complete that the load would be removed. But it does not appear to function that way.
If anyone can save me the ticket it will be appreciated.
What do you mean by “load”?
Marking an operation complete is one thing… entering a completed quantity (LaborQty) is another. We have a LOT of instances where operators complete an operation but don’t enter a quantity so the job looks incomplete.
The Load that is placed against the resource by the scheduling engine.
@jkane How is your load relieved by setting in Company Config set?
Hours. But I don’t want to do Quantity or Cost pretty much for the same reason why I asked my question. I was trying to build a BAQ and filter out the completed operations, but I could not figure out a way to get back to the Job.
Well I thought that ShopLoad or ResourceTimeUsed would be updated when I moved a quantity, but it did not, so I am at a loss on how the load gets relieved.
Would adding PartWip table to your BAQ get you back to the job?
Load is relieved automatically based off of your Company setting. But let’s say the load is 1.5 hours. Employee logs in, logs out, and marks the operation as complete. If they logged in for only .5 hours, then the system still leaves an hour of load on them until the job is completed or closed.
Seems like the load should disappear when the operation is completed (or at least when global scheduling is run next). I have a feeling that this will be “operating as designed”.
No, not on the ShopLoad table.
I think I just need to switch my table from ShopLoad to ResourceTimeUsed. I’m going to try that.
Sorry for necro-posting, but I was asked if I ever figured this out in a direct message.
I had figured out that what was being left behind was Setup time. There is a flag on the Site that will clear setup time when the Production is marked complete. I believe the field is “Auto Complete Setup”. If this flag is not set to true, you have Setup time on your operations, and the employees do not log into Setup; this will result in the load staying on resources until the Job is Closed.