New RQC User Policy or New Licensed User Policy

Does anyone have a policy and set process for adding new users to RQC? Or adding a new full licensed user to Portal? It makes more sense when one employee replaces another employee, but what about additions? Really any policy in general for new users would be nice to review if you wouldn't mind sharing. Are there any rules or conditions that must be met for the user to be approved and added? Thank you!

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

jon-athey

I don't have a written policy but I do look at the number of requesters there are for a Requesting Location. In general, I like to have no more than 2 per location but there are exceptions like IT, Lab and Biomedical. I might also question whether a person really needs the access. From time to time I'll get a request for a floor nurse and I'll deny the request and direct them to the material handlers that order supplies for the nursing areas. If a new CFO or other exec comes on board I would question that request as well. It's rare that upper management will get involved in ordering supplies or even capital or services because they usually have middle managers or the Admin Assistants do that work.

By "fully licensed" Portal user are you referring to someone that would access PO20, PO30, IC21, WH32, etc.? This is handled by one person in each area - Finance, HR and Materials depending on the access requested of course. If it's Materials related, I would decide whether the access is warranted based on their job role.

Stace Webley

Ya, Jon you are correct in your assumption of what I call a "fully licensed" user. I appreciate your feedback on adding additional RQC users to requesting locations. I think 2 is enough. Do you have a request form that gets filled out or is it just via e-mail?

[Updated on 6/10/2014 12:47 PM]

unknown

I have policies for the procurement LSF roles and the PFI approvers that I can share ( kvila@mhs.net ). We do not restrict RQC although we do require all requests to go through the IT Security tickets.

There is a process flow in place to take out requesters as they leave the organization. IT did ask me once a few years back to tell them requesters to inactivate - I did it by eliminating anyone who hadn't created a requisition in a year.

jon-athey

Our requests go through IT as well. They have an online request form on the Intranet for all systems. They have to check the box for Lawson on the initial page which takes them to another page where they request access to specific Lawson security roles. I only get a notification of the request if the RQC or any MM roles are checked.

0911060553270289.pdf

Stace Webley

Thank you both for your input.

KatVila - I e-mailed you today requesting your documentation. Hopefully it didn't get junked!

unknown

We don't have a written policy, we rely on our Materials Management team to validate the legitimacy of each request. If it comes from them, access is granted, if not, we refer the requester to them for validation.

Then, we too monitor the number of active users as KatVila does, but in a different way. We have a batch/SQL process that is run monthly to identify and deactivate any RQC requester that has not generated a requisition in 9 months. This keeps our number of active requesters in check and helps us to stay below the total number of RQC licenses we have available. (And, perhaps more importantly, the process seems to have been "approved" by Infor when explained during our last two license audits.)

[Updated on 6/11/2014 7:16 AM]

Stace Webley

Thanks, tbonney. Is it pretty easy to develop a batch/SQL process like the one you described?

unknown

Yes, pretty simple process (assuming your Db is SQL). If you'd like, send me your email address (tbonney@mvnhealth.com) and I can send them to you for review.

Copyright © 2025 Infor. All rights reserved.