Inconsistent OpComplete Flag Behavior

We have BPMs in place that take data inserted via REST and use it to complete material issue and time entry for jobs. This will sometimes get the OpComplete flag checked TRUE, but it often doesn’t. Since we are doing this automatically, we are relying on Epicor’s logic to set that flag TRUE once the requirement for the job has been met or exceeded. Has anyone experienced and/or worked through this problem before?

Here is a BAQ showing my issue.
JO = JobOper table
LD = LaborDtl table
JH = JobHead Table

Our users are looking for knowledge as quickly as possible that production has completed for a job, so we are not waiting for any or periodic process. We are looking for real-time updates that the operation has completed.

OpComplete isn’t directly maintainable. It is usually derived from MES entries (mainly Setup and Production)

Not sure how you are set up but using the status of the JobOpr.ProdComplete field of the final operation on the job would most likely be the best ‘real-time’ way to determine when a job was finished. I guess it depends on how long it takes for that stuff to get received into inventory/ready to use.

1 Like