HRHISTORY - Securing individual field number

We're working on setting up Lawson security for our employee training staff where they can see basic employee information but no pay. We have ESS so we want them to be able to see their own pay rate history in ESS but need to secure Salary History in drill around. I'm thinking I need to secure the HRHISTORY table for field 62 Rate of Pay. However, I'm not sure how to write that conditional rule. Has anyone done this before? Or, know of a better way to secure Salary History?

Thanks for any help you may be able to provide.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

Maybe something like below? You would use this in the[View:/cfs-file/__key/communityserver-discussions-components-files/18/hrhistory_5F00_security.docx:320:240] Security Class that is assigned to ESS

slivak

It's been years since I was a Lawson SysAdmin, but I seem to recall that there is a master ESS user ID that sets security for all ESS users, whereas functional access to Lawson Application screens is controlled at the role level.

Gelangens_Anlage_Entwurf.pdf

unknown

Just to let you know the pay rate history module in ESS gets that info from the PA67.1, not the HRHistory table. As far as securing a field, we do that for some tables in ESS using a rule similar to - table.EMPLOYEE==strToNum(user.getEmployeeId())||user.isSupervisorOfEmpInHR(table.COMPANY,table.EMPLOYEE)||user.isInChainOfCmdOfEmpInHR(table.COMPANY,table.EMPLOYEE) - this would be a rule created for the specific field and matches the employee number on the table against the user employee number. Note that this rule also gives access to the employees supervisor and mgt above that supervisor. This rule would let the employee and their mgt see the value of the field, but no one else. If the conditions were met, then you would give inquire,update or whatever access otherwise, no access. We have a rule similar to this on the PA67 for ESS. Hope that helps get you started.

unknown

I was able to get this to work. Thanks for your suggestions everyone. They helped!

Copyright © 2025 Infor. All rights reserved.