• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Financial Management Lawson S3 Financials

Req- operator ID

 2 Replies
 1 Subscribed to this topic
 43 Subscribed to this forum
Sort:
Author
Messages
Chesca
Veteran Member
Posts: 490
Veteran Member
5/28/2015 5:37 PM
We are having an issue with some Reqs that are being created with an unknown operator ID= "essuser". We looked in security and there isn't such user. The requester is a Handheld device and header source is Upgrade. I have attached a screenshot.
Attachments
JonA
Veteran Member
Posts: 1163
Veteran Member
5/28/2015 6:08 PM
I have only second-hand knowledge about this but I believe essuser will default when there's no UNIX id created for a requester whether they use the handheld, RQC or RQ10. So if I'm correct you'll have to figure out which of your handheld users do not have a UNIX account and build one.

Regarding the Header Source of "Upgrade", when we first implemented MSCM the header source showed "Upgrade" but in March 2012 we upgraded to a different version, 9.0.1 I think, then the source changed to "IC83".
Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
Chesca
Veteran Member
Posts: 490
Veteran Member
5/28/2015 6:25 PM
You are the best! Indeed, those users do not have a unix account setup so whenever they ran the job, it didn't pick up their account so it defaulted to "essusers" as you mentioned. Thanks a bunch!!