PeopleSoft Learning

HCM - RowLevel security directly driven by the - "RowLevelSecurity" Permission list.
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.
Each 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 Campus solution.

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).

Core Person Model -- Record PS Query View for CS
ACCOMPLISHMENTS -- SCC_ACCOMP_QVW
ACCOM_DIAGNOSIS -- SCC_ACCOM_D_QVW
ACCOM_JOB_TASK -- SCC_ACCOM_T_QVW
ACCOM_OPTION -- SCC_ACCOM_O_QVW
ACCOM_REQUEST -- SCC_ACCOM_R_QVW
ADDRESSES -- ADDRESS_NPC_VW
AUDIOMETRIC_TST -- SCC_AUDIO_T_QVW
CITIZENSHIP -- SCC_CITIZEN_QVW
CITIZEN_PSSPRT -- SCC_CITZN_P_QVW
DISABILITY -- SCC_DISABLE_QVW
DIVERSITY -- SCC_DIVERS_QVW
DIVERS_ETHNIC -- SCC_DIV_ETH_QVW
DRIVERS_LIC -- SCC_DRIVERS_QVW
EMAIL_ADDRESSES -- SCC_EMAIL_QVW
EMERGENCY_CNTCT -- SCC_EMERG_C_QVW
EMERGENCY_PHONE -- SCC_EMERG_P_QVW
EYE_EXAM -- SCC_EYE_EXA_QVW
NAMES -- SCC_NAMES_QVW
PERSON -- PERSON_NPC_VW
PERS_DATA_EFFDT -- SCC_PER_EFF_QVW
PERS_DATA_CAN -- SCC_PDE_CAN_QVW
PERS_DATA_USA -- SCC_PDE_USA_QVW
PERS_NID -- SCC_PERS_NI_QVW
PERSON_PHONE -- SCC_PERS_PH_QVW
PHYSICAL_EXAM -- SCC_PHYS_EX_QVW
PUBLICATIONS -- SCC_PUBLICA_QVW
RESPIRATORY_EXM -- SCC_RESP_EX_QVW
VISA_PMT_DATA -- SCC_VISA_P_QVW
VISA_PMT_SUPPRT -- SCC_VISA_S_QVW


Query Views to be used in place of core Person Model Tables with PeopleSoft
Query for Campus Solutions reporting needs.