• Campuses can access the various PeopleSoft non-production instances through different sites.
• CMS Development Launcher page support both single signon and non-single signon: https://cmsdevlauncher.calstate.edu/launcher/indexH.html
• Note: If testers need to impersonate another user, they should use the CMS Development Launcher page to access the non-single sign-on version of the PeopleSoft sign-on screen.

• CHRS Non-Production support only single signon: https://csyou.calstate.edu/Projects-Initiatives/chrscompletion/Pages/CHRS-Non-Production.aspx

• CFS Non-Production support single signon: https://csyou.calstate.edu/Tools/Financial/common-financialsystem/Pages/CFS-Non-Production.aspx

Each campus may have different methods for provisioning access to Campus Solutions, HR 9.0, CFS, and HR 9.2. During the CHRS implementation, we request that campus users needing access to the various test databases contact either their campus CHRS primary or secondary security administrators.

• If they encounter issues, please submit a ServiceNow ticket with the following details:
  • Type – Access Request/Problem
  • Category – CMS-CHRS
  • Subcategory – Security – User Profile.

During each phase, CMS will copy your production Campus Solutions and HR 9.0 databases to “CMSmanaged” databases. Please refer to the CHRS Pass Tracker for additional details. The Pass Tracker for Wave 4 is still TBD.

Campus Solutions:

Typically, the refreshed copies of the Campus Solutions production database will have the database name CACHRWAx.

Human Resources 9.0:

Typlically, the refreshed copies of the HR 9.0 production database will have the database name: HBCHRSRx.

CFS:

Please refer to the CHRS Pass Tracker for information on the CFS database that will be connected to HR 9.2.

Human Resources 9.2:

Please refer to the CHRS Pass Tracker for information on the HR 9.2 database.

Database-level Oracle accounts, such as SYSADM, DU, or DS, are provisioned and managed by the CO DBA group. Depending on the database, your campus users may have access to their Oracle accounts if they were granted access in production.

Campus Solutions:

Campuses will not receive the SYSADM password for the CACHRWAx database unless there is a business justification requiring that level of access.

If a campus user has a Oracle account in the Campus Solutions production database, it will carry over to the clone copies.

Human Resources 9.0:

Campuses will not receive the SYSADM password for the HACHRSRx database unless there is a business justification requiring that level of access. If a campus user has a Oracle account in the Human Resources 9.0 production database, it will carry over to the clone copies.

CFS:

Campuses will not receive the SYSADM password for the CFS non-production database unless there is a business justification requiring that level of access. If a campus user has a Oracle account in the CFS production database, it will carry over to the clone copies.

Human Resources 9.2:

Campuses will not have Oracle accounts provisioned in HR 9.2.

End of Article