HCM - RowLevel security directly driven by the - "RowLevelSecurity"
User Profile needs to have Rowlevel Security Permission
assigned to get the security.
We can have Department based -
RowLevelSecurity as well as based on the custom Security Set Properties.(It can
be based on COMPANY, BUSINESS UNIT etc.).
1) Security by Department 2) Security by Permission List.
Rowlevel security is enforced in the components by user Security Views as Search Records, where OPRID is a non-search key field. PeopleSoft
Rowlevel Security in the PSQuery is achieved by Search - Query Security Record - which is an property of the Record. Query Security Record (which a security view) is added to query automatically.
Since the Campus has different security model, using HCM Personal data records in PSQuery for Campus Solutions will be a problem.
Campus solution Module doesn't use the "RowLevelSecurity" Permission list in
the User Profile.
Campus solution has 2 options -
a) SCAR security based on the data element
linked to student is accessed. Like INSTITUTION, CAREER, PROGRAM, PLAN.
User ID needs to be configured in the SCAR security for each of the data
elements like CAREER, PROGRAM, PLAN etc.
b) Person Mask security, even if user have access to different data elements
in the SACR for the configuration purpose, we can restrict the access to student
data by using this configuration.
PERSON_SRCH - Delivered search view is used
to control the security and part of many search records of the components in
In this case, User "Primary Permission" list needs to be configured in the
Person Mask component and Person Mask process needs to be executed so that User
can get the access to view Student information in the campus solution.
Set up SACR > Security > Secure Student Administration > Permission
List > Demographic Data Access
Set up SACR > Security > Secure Student Administration > Process
> Demographic Data Access
Since the HR Person records has Row level security attached for the PSQuery
and Campus doesn't use the Rowlevel security model similar to HR. We cannot use
the base Personal records in Campus to create the PSquery reports (unless
security is replicated).