EHR: Changes to Job Component Is Making The Employee Data Available To All Security Access Types
(Doc ID 2674698.1)
Last updated on JUNE 03, 2020
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
Four different access types are created to ensure Security of Employee Information between companies. After creating a new Security Access type, it was that when we make any job data update such was adding a new effective dated row to Job Data, the specific employee data becomes accessible to all security access types.
Select Employee for Testing purposes
- Create a new Security Access Type 111
- Modify the SQL of the where clause to exclude (not Include) specific data
- In the test we chose to exclude employee with a JOB.JOBCODE NOT IN (XXX)
- Run a SQL query against the PS_SJT_PERSON table for the employee used in the test, note the initial results of the query show that the person has 2 SCRTY_TYPE_CD
Insert an effective dated row in Job Data for the employee used in testing
After the row insert Run a SQL query Against the PS_SJT_PERSON table note the results, now this employee has 3 SCRTY_TYPE_CD, it added the new one even this employee is not supposed to have access to employees in that access type.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document