Peoplesoft Security Interview Preparation Guide
Enhance your Peoplesoft Security interview preparation with our set of 16 carefully chosen questions. Each question is crafted to challenge your understanding and proficiency in Peoplesoft Security. Suitable for all skill levels, these questions are essential for effective preparation. Download the free PDF to have all 16 questions at your fingertips. This resource is designed to boost your confidence and ensure youre interview-ready.16 Peoplesoft Security Questions and Answers:
1 :: Suppose organization XYZ uses PS department security. There are 4 levels in the department tree 1,2,3 and 4 with 4 being at the top of the tree. If a manager A is in dept 3 and has 2 direct reports in the same department. Can the direct reports view data for employees in department 4?
If the direct reports are also in department 3 then they can see the data for employees in department 2 and 1 only. They cannot see the data for a population which is above their department tree node. Since 4 is above 3 they cannot see the data.
2 :: Suppose organization ABC uses Department Security with Dept 1 as the parent department. Dept 2 is the child of Dept 1, Dept 3 and Dept 4 are the child of Dept 2. A person is given the Read/Write access to Dept 1. Which departments will he have access to? Can we restrict the access to dept 3? If yes, how?
Since Dept 1 is the parent department and read/write access is given for Dept 1, the user will have access to all the departments under Dept 1, i.e. Dept 2, Dept 3 and Dept 4.
Yes, we can restrict the access to Dept 3 by giving ‘No Access’ to Dept 3 while defining the access code for Dept 3 on the Security be Dept Tree page of the respective permission list.
Yes, we can restrict the access to Dept 3 by giving ‘No Access’ to Dept 3 while defining the access code for Dept 3 on the Security be Dept Tree page of the respective permission list.
3 :: Do you know how is Security by Department tree different than Security Access types?
Security by department tree defines which setid and deptid a permission list has access to. Security access types are different ways in which security can be driven for a security set. For example department security can be driven by department tree or department setid. Both these are security access types which belong to security set department.
4 :: Explain the flow of setting up application security. When a new functionality is released how do we setup a user in PS to get access to it?
When a new functionality needs to be provided access for users, then roles and permissions are used. The functionality is associated to a menu—component—page. So the user needs to get access to the page in one of the various modes like: Add, update or view only. For this, the menu – component – page layer is tied to a permission list. This permission list is then attached to a role and the user is then provided this role through user profile. As a result user will be able to access the functionality.
5 :: How to assign row level security to users?
The steps to assign row level security are:
i) Assign desired values of fields (department/ job location/ job company/ business unit etc) to Data Permission Lists
ii) Assign these Data Permission Lists to users
If field is ‘Department’:
i) Data Permission List is given access to values values of ‘Department’ field defined at various levels in Department Security Tree through: Set Up HRMS -> Security -> Core Row Level Security -> Security by Dept Tree
ii) Users are directly assigned to Data Permission List in user Profiles component – ‘General’ page – Row Security field. A user can be assigned to only one Data Permission List at a time.
If field is not ‘Department’ but ‘Location’, ‘Business Unit’, ‘Salary Grade’ etc:
i) Data Permission Lists are given access to values of these fields through: Set Up HRMS -> Security -> Core Row Level Security -> Security by Permission List
ii) Users are assigned to Data Permission Lists through roles in user profiles component (Roles page). Multiple such roles can be assigned to users as per requirement.
OR
Users are directly assigned to Data Permission Lists in user profiles component – General page – Row Security field.
i) Assign desired values of fields (department/ job location/ job company/ business unit etc) to Data Permission Lists
ii) Assign these Data Permission Lists to users
If field is ‘Department’:
i) Data Permission List is given access to values values of ‘Department’ field defined at various levels in Department Security Tree through: Set Up HRMS -> Security -> Core Row Level Security -> Security by Dept Tree
ii) Users are directly assigned to Data Permission List in user Profiles component – ‘General’ page – Row Security field. A user can be assigned to only one Data Permission List at a time.
If field is not ‘Department’ but ‘Location’, ‘Business Unit’, ‘Salary Grade’ etc:
i) Data Permission Lists are given access to values of these fields through: Set Up HRMS -> Security -> Core Row Level Security -> Security by Permission List
ii) Users are assigned to Data Permission Lists through roles in user profiles component (Roles page). Multiple such roles can be assigned to users as per requirement.
OR
Users are directly assigned to Data Permission Lists in user profiles component – General page – Row Security field.
6 :: Suppose if a person is assigned row security for a department, will he have access to all the child departments as well? If yes, is there a way we can restrict access to one of those?
By default, the user will have access to employees of all the child departments. Although, access to employees in a child department can be restricted through data permission list. To define the security profile of a department tree, navigate to: Setup HRMS -> Security -> Core Row Level Security -> Security by Dept Tree. For the particular row security permission list, access codes can be set to ‘No Access’ for a child department to restrict access.
7 :: What is SJT_OPR_CLS?
SJT_OPR_CLS: Contains the User IDs with their data permission lists.
8 :: What is SJT_CLASS_ALL?
SJT_CLASS_ALL: Contains the data permission information for all the data permission lists that are given data access on the ‘Security by Dept Tree’ page or ‘Security by Permission List’ page.
9 :: What is SJT_PERSON?
SJT_PERSON: Contains transaction data for the people (employees, contingent workers, Person of Interest). It has row level security attributes (SetID, DeptID etc) for all the employees.
10 :: Do you know what are security join tables? Why is it necessary to refresh SJT processes?
PeopleSoft system stores security data in user and transaction Security Join Tables. (SJTs).
User SJTs are:
SJT_OPR_CLS: Contains the User IDs with their data permission lists.
SJT_CLASS_ALL: Contains the data permission information for all the data permission lists that are given data access on the ‘Security by Dept Tree’ page or ‘Security by Permission List’ page.
Transaction SJTs are:
SJT_PERSON: Contains transaction data for the people (employees, contingent workers, Person of Interest). It has row level security attributes (SetID, DeptID etc) for all the employees.
SJT refresh processes have to be run to keep security data (in user and transaction SJTs) up to date so that the system enforces data permission using the most current information.
User SJTs are:
SJT_OPR_CLS: Contains the User IDs with their data permission lists.
SJT_CLASS_ALL: Contains the data permission information for all the data permission lists that are given data access on the ‘Security by Dept Tree’ page or ‘Security by Permission List’ page.
Transaction SJTs are:
SJT_PERSON: Contains transaction data for the people (employees, contingent workers, Person of Interest). It has row level security attributes (SetID, DeptID etc) for all the employees.
SJT refresh processes have to be run to keep security data (in user and transaction SJTs) up to date so that the system enforces data permission using the most current information.