Report Quantity only transaction in MES

Checking the forum to see if anyone else has experienced this issue. We’ve recently seen when an employee reports quantity on a job through MES it doubles the quantity. When reviewing the transaction in job tracker and time and expense we see two identical entries posted to the job. This is random not specific to a job, user or machine. Working with epicor but have no resolution so far. Any advice is appreciated!
Lisa

Are there any Method or Data Directives? Is the resource marked as backflush? Is it the final operation or one prior?

John, We’ve seen this on the last and prior operations. We do not use backflush. We do have data directives and methods on part and customer but not jobs. When I say it’s random we did 3 successful transactions testing with epicor over teams. Our fourth entry doubled. Of course!

Is the employee the same on both records when it is doubled? Is all of the data the same?

Yes it’s a duplicate entry of the employee’s transaction. Same timestamp etc.

I have seen this when there is more than one resource on the operation.

Hi Mark,
Can you elaborate? One than one person clocked in on a job at the same workstation? In this case they are signed into MES, enter their ee id and shift and then report qty, save and then check Job tracker to review the transaction.

More than one scheduling resource (Op Dtl Seq)

There may be some other settings at play too, but this was from E9 days.

Oh, are you thinking that two scheduling resources that are both marked as Location might cause this?

I don’t recall the details but removing one of the resources also removed the double entry. Split Labor = Burden might have had a hand in it too, but it’s been a long time ago.

We have 6 resource groups all scheduled the same and have 1 assigned scheduled resource per and only have two resource groups where qty is doubling.


This only started happening in April.

Does that mean you mark employee resources as being a location? Employees should generally not be a Location, the machine/bench where they work should be the location.

When was the last time that your environment was updated? Was that also in April?

We’re cloud on Kinetic 2023.2.11