Troubleshooting Future Dated Security in Peoplesoft HRMS 8.9, 9 and 9.1

Troubleshooting Future Dated Security in Peoplesoft HRMS 8.9, 9 and 9.1 [Video]
Future dated security, or granting access to users based on rows in the future involves 2 important setups:
1. Security Access type:
To turn on future dated security, the corresponding enabled security acceess types in your system must have the "Include Future dates check box" turned on.
2. Security Installation settings.
The actions that trigger future dated security SECTION IN THE INSTALLATION SETTINGS must have all the actions for which you want ENABLE future security.

If you have both of these set ups in place then creating a future dated row in Job for the Employee, in addition to the current row, SJT_PERSON will be updated with information about this Future row.

For example, Employee KU0007 who is currently in the department of "Admin" is to be transferred to a new department of "Finance" in future. This future dated entry in job will automatically create a new entry in SJT_PERSON with the Future flag set as Y for the future row.
In effect any user having access to department of Admin or department of Finance will be able to access the Employee's information.

For troubleshooting issues around future dated security:
1. The first thing you need to check is if include future dates is enabled for the enabled access types in your system.
2. Second step would be to check if the action used in the future dated row is included in the Security installation settings.
**Please note that if you make any changes to these 2 set ups, you need to run Refresh Trans SJT Tables Process and Refresh SJT_CLASS_ALL process..

Additional tips:




  • Most of the issues related to Future dated security get resolved by running the Refresh Trans SJT process.
  • If you are having issues with the access of rows that have recently become current rows, then you need to run Refresh Trans SJT Tables Process. This process will delete the history rows and update the future flag of the row that became current now to N.
  • Please note that Query security records are designed to fetch only current rows. These will not bring up future rows even if you have future security enabled.
  • Also note that Future security is currently not designed to work with other Security Sets like RSOPN.
  • Irrespective of whether you have enabled Future security in your system, it is important that you schedule Nightly refresh process to run a short time after midnight to keep your security tables in synch. This process, will update all the future rows that are becoming current on the given date. If this is missed, then running the Trans SJT process will get the table in synch.