Last updated on JULY 13, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.
SPECIFIC TO: Enterprise Time and Labor Release 9.0
Customer upgraded from 8.81 to 9.0, they use dept security not group security
The majority of their employee's are unable to report future time as they do not have row security permission lists assigned to them.
His end users were never given row security permission lists in the past. They use the 'Create Row Level Security for Dept Managers process ' which generates a managers Permission list when the user becomes a department manager.
When they are no longer a manager this process deletes the row security permission list.
Below is an excerpt from PeopleBooks on how the Dept Manager Row Level Security process works:
Understanding Data Permission for Managers Use the Create Row Level Security for Dept Managers process to grant the appropriate data permission security access for department managers. The process will:
Create a user profile if the manager is new and has no user profile.
Create or update an existing row security permission list for each department manager, giving them access to the data in the departments that they manage.
Delete the row security permission list for a user if it is obsolete (for example, the employee is no longer a manager).
You will notice the third point - it will delete the row security permission list. It appears as though the T&L assumptions that people have row-level security conflicts with HR assumptions where this is not
necessary if the person is not a manager.
Also, if you look at the Oracle Red Paper titled "Enterprise HRMS Row Level Security in Release 8.9", you will see a note on Page 53 in the section Assigning Security to Users that states "The Row Security field
is not required. You do not need to enter any value in this field."
So, I believe either Time and Labor should not rely on this field, or the Row Level Security for Dept Managers has to somehow determine a permission list to put in this field. I don't think it should be a customization to make these two work together.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms