Custom Security Not Working After Running Security List Maintenance(PERSLM) For All Security Profiles (Doc ID 2006120.1)

Last updated on MAY 17, 2016

Applies to:

Oracle Human Resources - Version 12.1.3 to 12.1 HRMS RUP8 [Release 12.1]
Information in this document applies to any platform.
This note provides a brief overview of .

Symptoms

Problem Statement:

Custom Security is not working after running "Security List Maintenance(PERSLM)" for All Security Profiles.

Steps to Reproduce:

The issue can be reproduced at will with the following steps:

  1. Create a custom security.
    (N) Security > Profile
    e.g.
    Name              : XXSecurity
    View All Records: uncheck
    View Employees: Restricted
    Custom Security: Restrict the people visible to this profile
                             people_group_id in (111,222,333) or pay_basis_id in (444,555)

  2. Create an employee assignment with people group and salary basis not included in the custom security. (e.g. people_group_id = 666, pay_basis_id = 777.)
  3. Run "Security List Maintenance" for all security profiles. (Generate lists for: All Security Profiles)
  4. Employee created in the above step 2 is stored in per_person_list and can be viewed by the secured responsibility that the custom security profile is assigned.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms