Use this checklist to prepare your campus to use WA functionality in CHRS.
Security
The CHRS Library - Security Page provides a full list of Dynamic roles, Baseline CHRS Security roles and the CHRS Security Plan and Requirements for review.
Majority of the roles for Workforce Admin will contain "WA" in the role name.
Identify user types on your campus and coordinate with your security admin to assign appropriate roles.
- Self Service Only
- Student Mod General
- Student Mod Config/Superusers
- TFE General Users
- TFE Cong/Superusers
- Position Management Viewer
- Position Management Correction Mode
- Job Data Viewer
- Job Data Correction Mode
- Query View
- Query Manager for Private Queries
- RPT General Users
- RPT Cong/Superusers
Remember to review Department Level Security for your users. This ensures they can access and update the employees they’re responsible for.
Student Mod Configuration
The Student Mod, pulls the ACAD_PROG_PRIMARY value from the PS_STDN_CAR_TERM table in Campus Solutions. Campuses must map these values in that field to either Graduate, Undergrad or No Mapping.
Job Aid: Student Mod Setup
The Student Mod permits only specific action/reason combinations based on the configured setup.
Job Aid: Student Mod Setup
The Student Mod uses the values defined for each job code to determine how the transaction should load to the job and whether the student being hired meets the eligibility requirements.
Job Aid: Student Mod Setup
R11 job codes should not be included in the Student Mod and must be processed exclusively through TAE.
Open a ServiceNow ticket using the example campus configuration document, update for your the template with your campus information based on what should be migrated from each pass through MTP.
TFE (Transactional Front End) Configuration
For TFE, all Action/Reason combinations are initially loaded into the table with the “Central Use” flag automatically enabled. Campuses must review these entries, uncheck the flag, and remove any combinations that do not apply to their specific needs.
Job Aid: Pending
In TFE, workflows for both Job and Position are configured by Business Unit, Level, Action, and/or Action/Reason. The process supports up to seven approval levels, excluding the final approver. The final approver is added when the transaction is submitted.
All approvers must have a TFE role and the appropriate Department Level Security. They can be set up using Reports To, Workflow Role, or ASM Manager. Using ASM Manager requires a specific role assignment and corresponding table configuration.
The final approver role is CHRXX_WA_TFE_HR_APPROVERS for all employees, except those in Union Codes R03 and R11. For employees in Union Codes R03 and R11, the final approver role is CHRXX_WA_TFE_FAC_APPROVERS. (Note: "XX" represents the campus identifier.)
Open a ServiceNow ticket using the example campus configuration document, update for your the template with your campus information based on what should be migrated from each pass through MTP.
RTP Configuration
The RTP mod allows for campuses to customize the Campus long and short description to meet their needs and would displayed on the review page.
Job Aid: Pending
Campuses often set up based on the academic year and when the review should occur.
Job Aid: Pending
RTP requires the Department Rollup Process to be used in conjunction with a tree that meets specific requirements. The Department Security tree can be used if it correctly identifies your organization structure and meets the requirements.
The CHRS Hierarchy tree does not meet these requirements.
- Tree can only consist of Nodes – it cannot have Leafs.
- The tree must be a minimum of 4 levels.
- Campus – Level 1
- Division – Level 2
- Campus – Level 1
- College – Level 3
- Department – Level 4 or greater
- Division is always Level 2.
- College is always Level 3.
- Division or College must have been active in Dept Tbl at one time. Current row does not have to be active.
- Dept ID must be active to build the tree but can then be inactivated.
- Division or College cannot be character must be a Dept ID.
- The Departments (level 4 or greater) must be valid/active in Dept Tbl, or the Node/Department will not be processed by program.
- Tree branch’s depth/levels is not limited to 4 levels. Level 4 and below is for Departments.
Open a ServiceNow ticket using the example campus configuration document, update for your the template with your campus information based on what should be migrated from each pass through MTP.
Recommended Review
Updates have been implemented under both the CSU Position Data and CSU COI Position Info tabs to meet systemwide reporting requirements. These modifications include the addition of fields such as MPP Job Family Code, MPP Job Function, MPP Reporting Category, and CSU Working Title.
Job Aid: Complete the CSU Position Data page
The CSU Unit Table is used to capture unit information at the employee level, which is then mapped as PPT Field #121 on the Personnel Payroll Transaction (PPT) form. The ‘unit’ is also used as matching criteria for loading paytape information into PeopleSoft. Because ‘unit’ is one of the four elements that make up the SCO Position Number, it is used in many delivered baseline processes including: PIP, ACES, and Paycheck Creation. Besides on the PPT, ‘unit’ is also used on many Base Benefit forms.
Navigation: Main Menu > Set Up HRMS > CSU Product Related Setup > CSU Position Mgmt Setup > CSU Unit Table
The CSU Primary Fund Table is used to identify the primary source of funding when an employee gets hired into the system. This modification allows campuses a way to conduct compensation pool analysis, thereby meeting bargaining unit requirements to provide such information.
Navigation: Main Menu > Set Up HRMS > CSU Product Related Setup > CSU Position Mgmt Setup > CSU Primary Fund Table
End of Article
You are done. Great job!
0 Comments
Add your comment