I’ve been looking here and have not found exactly what I’m looking for. If a user enters a quantity in Report Qty in MES and click ok, I want to stop then if that operation has already been clocked.
When a user clicks okay is that when the clocked in date in LaborDtl gets set? If so, can I do a post processing BPM on Labor.DefaultOprSeq to see if the operation and seq are the same and if the clock in date is already set?
LaborDtl (Clock-In) starts as soon as they start a Production Activity.
They can report quantity in MES at any time, but I think this just updates the LaborQty on the LaborDtl record. It does not update or even record the time that LaborQty transaction happened.
What are you trying to prevent? Over-reporting of Qty?
We have many operations that could have many “clock-in” transactions. Could be an operation that takes days to complete, and they’ll clock-in against that operation multiple times.
The ask was to prevent a user from clocking an operation that had already been clocked. Maybe the way they worded it is what is throwing me off.
When a user enters a quantity on report quantity and clicks okay what does Epicor do data wise?
Updates the LaborQty on the selected/active LaborDtl record.
Until the job is closed, even if an operation is marked complete (all required quantity was accounted for), there’s nothing stopping an employee from clocking into that operation again and reporting additional quantity.
So, an employee first starts a Production Activity. This creates a LaborDtl record.
Then they can report qty. Which updates the LaborQty on that LaborDtl record.
I guess the question is WHERE do you set up the road block? When they try to start a production activity? Or when they try to Report Qty?
And in either case, what are your criteria for stopping it? If the operation already has a LaborDtl record associated with it? (that sounds dangerous… someone could start time against an operation by accident by choosing the wrong one from the list… and now that blocks anybody else who needs to get to that operation. I think that will cause you more grief than its worth.)
You could prevent starting production activity against an operation that is already complete? (RequiredQty = LaborQty?)
Or, you could allow them to start activity, but not report qty if the operation is complete. But, keep in mind, if they clock-in on an operation, they’re adding labor cost to that operation whether they report qty or not.
Again, not sure the “request” makes sense (in my head).
It’s my GUESS that your “requestor” would probably want to prevent a new time entry (LaborDtl) against an operation that is already flagged as “complete”??