Welcome Guest [Log In] [Register]
Bookmark and Share
Welcome to LawsonTalk. We hope you enjoy your visit.


You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.


Join our community!


If you're already a member please log in to your account to access all of our features:

Username:   Password:
Add Reply
Manager Self Service; Drill down security
Topic Started: Oct 27 2008, 07:04 AM (586 Views)
mwingmgh17
Member Avatar
Member
[ *  * ]
Does anyone know how to secure certain areas of the Employee Drill around information that is available to managers through MSS?

using laua security with 9.0 applications and lsf9 foundation

what I have found is that if a manager drills down on the category of Overtime,
payroll schedule, they get to the next screen which shows the pay plan if they drill down there, they get a list of all employees in that plan (which is ALL employees) and their socials..


Anyone got a suggestion? Needless to say our Compliance division wants my head at the moment
Offline Profile Quote Post Goto Top
 
tltwite
Member
[ *  * ]
Lawson has a document that might help you. It's called Employee/Manager Self-Service Technical Documentation. It lists all of the back office screens and files that need to be secured for ESS and MSS. I think you can find it on their support site. If not, let me know and I can email you a copy. I didn't know this document existed until one of Lawson's business consultants emailed it to me last week.
Offline Profile Quote Post Goto Top
 
mwingmgh17
Member Avatar
Member
[ *  * ]
I actually have that document sitting in front of me, and its been helpful with other things, and it shows me what is needed to get to that page, but its the drill down piece from this section that I am having the issues with. Nothing in that document about the Employee Drill down information that managers have access to.
Offline Profile Quote Post Goto Top
 
tltwite
Member
[ *  * ]
According to my consultant, the files listed in the DME section are suppose to be the ones you need to secure for Drill Around. Is that not the case then?
Offline Profile Quote Post Goto Top
 
arvin
arvinojales
[ *  *  * ]
Try to set the Access to "N" in RM for those MSS users and refresh your server cache, this will limit them to only see their own and their direct report's profile.

Arvin Ojales
Offline Profile Quote Post Goto Top
 
mwingmgh17
Member Avatar
Member
[ *  * ]
Arvin-Thanks for your reply
I tried your suggestion in test and it worked, it was my understanding that they needed the Y in RM to view their employees data is that not the case?

Offline Profile Quote Post Goto Top
 
arvin
arvinojales
[ *  *  * ]
Setting the Access in RM to "N" will use the "My Data" security, it will look for the Services in RM, in this example it will look for the employee number and behind the scene will also check the HR07 record for that employee and if that employee has a supervisor code, it will give access to all of his/her direct reports.

As long as these supervisors are not running Lawson programs in HR suite this is fine, I supposed you disabled the search box in portal for these users. If any of these supervisors need to run HR suite app programs in portal and need to have access to all employee record (a good example is your payroll manager), you may want to set their access flag to "Y", otherwise your payroll manager will get a security violation in portal if he/she tries to inquire on an employee record that is outside his/her direct reports .

Another issue, if your company is using the Organization chart in portal, those users that has access = "N", they will get a security violation error because the Org chart is accessing employee profiles from your CEO down to the lowest supervisor level. This was working in 8.0.3, if the RD30 access flag is "N" you can still run the Org Chart without problems.

Arvin Ojales
Offline Profile Quote Post Goto Top
 
oceana6
Member
[ *  * ]
I just fixed this problem the the other day. You can fix this in LSF9. Take a look at the rules on the LP tables (I think TAEEMASTER) and make sure there is a Conditional rule to restrict the data to a Manager's own direct reports:

if (user.isSupervisorOfEmpInHr(lztrim(table.COMPANY),lztrim(table.EMPLOYEE)))
'ALL_ACCESS'
else
'NO_ACCESS'


Hope this helps.
Offline Profile Quote Post Goto Top
 
Cindy
Super Member
[ *  *  *  *  * ]
oceana6
Feb 9 2009, 12:30 PM
I just fixed this problem the the other day. You can fix this in LSF9. Take a look at the rules on the LP tables (I think TAEEMASTER) and make sure there is a Conditional rule to restrict the data to a Manager's own direct reports:

if (user.isSupervisorOfEmpInHr(lztrim(table.COMPANY),lztrim(table.EMPLOYEE)))
'ALL_ACCESS'
else
'NO_ACCESS'


Hope this helps.
I think the OP said he was using LAUA security. Conditional rules are in Lawson Security, so if I understood the post, I don't think that will work for his situation. Good for those already using LS though.
Offline Profile Quote Post Goto Top
 
« Previous Topic · Security · Next Topic »
Add Reply