Material Request Queue - No Employee Attached to User

Hello,
We have users getting the following slide out message when trying to access the Material Request Queue. “No Employee attached to User [Insert User ID]. An Employee ID is required for access.”

I’ve followed this older post: Material Queue Manager Error: No Employee Attached - Epicor ERP 10 - Epicor User Help Forum, and added both an employee to the user and user to the employee. However, the message still appears even after refreshing the browser, clearing account cache, and restarting their computer.

We’re on Kinetic 2025.2 (cloud). Is there something different in Kinetic that I might be missing?

Do you have the emp number in the warehouse team?

No, we don’t use Warehouse Team.

Are they using their actual accounts to log into Epicor? Or are they using a shared computer that might be using a generic log in?

I could be wrong but…on the employee record, I think one/both entries (depending upon user) in yellow are probably required for MRQ and the green for MQM.

That is controlled VIA MES Menu Security Maintenance

so between the two of us we threw out a couple of leads…hopefully it helps

Both Material Handler and Shipping/Receiving are checked. Not concerned about MQM for these particular users, but I’ve certainly made note about having Warehouse Manager checked if that ever changes.

Dadgum it. Oh well…thought we were getting somewhere. :frowning:

Well now one out of two users now have access. It makes me wonder if it was a user issue where they didn’t actually restart.
For example, I just created a test user and was furiously refreshing my browser but was still getting the same message. I then decided to close and reopen the browser, and to my surprise, my test user had access. Ugh, users! :face_without_mouth:

Thank you very much for your time and help!

When I add user IDs, I have to select the employee name (ID) for that company. When I add employee IDs, I designate the User ID. Check to ensure the user ID is linked to the employee ID and vice versa. I have seen access problems when they are not paired in each direction.