Employee Name/ID on Transactions

Kinetic ERP
1

Hello Friends,

We have MES tablets deployed and they all use a generic account to login, then the employee must log in with their ID. However, transactions performed by the logged in Employee are tagged as initiated by the generic MES login. Is there a way to make the transaction reflect the employee name/ID that performed it, instead of the generic logon user?

2

Best thing would be to get rid of the generic user and have them all log in with their personal ones.

1 Like
3

Yep that is what we thought, but that eats up normal licensing instead of data collection, and also the web version (we use IDP, not basic) does not actually log someone out when you click log out. The IDP session remains active and anyone can just click log in and it logs in the previous user. :man_facepalming:

4

I agree… however you might just get away with some UD fields and a BPM or two depending on where this is important.

5

Really? That’s not good as it should not. Is it a bug in Kinetic?

6

Let me double check

7

if I recall correctly you can consume a full license instead of a DC license if you get the URL just a little bit wrong. Not sure if you are using classic MES or Kinetic DC

8

Hey Evan,
We are using Kinetic DC in the browser with the MES URL

9

And you are using the URL format of

https://epicorservername.domain.net/EpicorProd/Apps/Erp/Home/#/home/MES/home?mode=DC

right? If you still see full license consumption on that, I think you should put in a case

1 Like
10

Oh ok no it does not consume a full license. I think we may have to go the BPM UD field route if we want to use MES, otherwise using a normal full login has the problem of not actually logging the user out (we use IDP).

11

I’m going to preface this with some caveats as they might play different in your situation. We’re using classic MES and standard Epicor logins (not SSO or SSO adjacent). If you’re logging in some way that isn’t the standard login you might get different results.

There is a spot on the Employee record to indicate Username which then links those two records. What this will then do in MES, or at least does in Classic, is that if the current User doesn’t match the one linked on the Employee record, it will prompt for a password and then change the background user to the linked on upon a successful login.

This is the way I’ve always seen a common terminal used so the transactions capture the specific user and employee that did them.

3 Likes