PeopleSoft HCM Security Fundamentals - Future Dated Security and Actions

Assigning Paygroups to employees in Job data is a required task in a PeopleSoft Payroll/Absence Management implementation. A common issue we have seen being reported after this activity is that business users have lost security access to certain employees after the paygroup assignment job. More often that not, we have seen that this issue can be attributed to the 'Actions that trigger future dated security' setting in core HR row level security. This setting controls whether a user has access to an employee becoming effective under the user's row security critiera in a future date. In the 'Actions that trigger future dated security' setup, the actions in Workforce Administration module that trigger the insertion of a future effective dated row into the security tables can be setup. Only those actions that are present in this setup page will enable future dated security.

In the case of paygroup assignment, it is required to use the action, Change of Pay System (PSF) for a number of customers and this action is not in the list of delivered actions that trigger future dated security. So, a miss to add this action in the security installation settings can cause row level security issues. We have also noticed this during Workforce Administration implementations, after data conversion of Job data.

We always recommend adding this check as a step in the data conversion activities, so that this is tracked effectively.