Skip to main content

Morning All,  My working environment is a machinist shop for the aviation industry.  We use “clock entries” to account for for the machinist time when they are working on production orders.  The process is this a machinist physically has the production order on his person.  They proceed to a scanning station and scan both their id card and production order to acknowledged they are working on the production order and whatever work center was assigned to them.  At this point no other machinist should be able to scan the same production order(physical part) and work on a different work center.    But it happen last week.  Please, see the embedded picture.  How can this be prevented?

 

We are currently using Acumatica 2022 R1.  We will be upgrading in few weeks to next the version of Acumatica.

 

 

 

@BOSullivan - the system won’t stop two people from clocking in to the same production order because technically you could have two people working on the same thing. (maybe not in your case - but in other companies this may be true) 

 


Writing/implementing a customization which checks upon employee clock-on to see if the production order operation already has an active clock record might be your best option.


Thanks, for the feedback.  Am I able to write this?  Or is this a source level coding issue?


Reply