This document is to provide campus users with a list of frequently asked questions regarding Jobsets for CHRS.
Scheduling
Who is responsible for scheduling JobSet?
CMS
How was the schedule determined?
For CHRS, a variety of factors were considered when scheduling each job, including frequency, system impact, run duration, whether the data needed to flow to the Datalake, the Jobs purpose, and any related dependencies.
What should a campus do if they believe a JobSet needs to run at a different frequency or time?
If a campus believes that a JobSet should configured differently, they should submit a ServiceNow Ticket. The request should include the proposed change, the reasoning behind it, and any impacts or dependencies the campus has identified.
CSU Employees Refresh
What is the purpose of CSU Employees Refresh?
The CSU Employees Refresh is a cloned/retrofitted extension of the delivered Employee Refresh process to include the populate of custom CSU fields within the PS_EMPLOYEES table.
Can campus users run the CSU Employees Refresh process themselves?
No. Only CMS can schedule and monitor the program. Campus users only have query access based on their security permissions
Can campuses use the CSU Employees Refresh process for real-time reporting?
Not exactly. The table is refreshed during the processed run, so campuses cannot obtain same-day changes from this table. If real-time data is needed, users must query the actual transactional tables instead of PS_EMPLOYEES table.
Primary Job Indicator Update
What is the Primary Job Indicator and why is it important?
The Primary Job Indicator identifies which of an employee’s multiple jobs should be used for Regulatory and University reporting. Because employees may hold more than one job, the indicator ensures consistent reporting across all CSU campuses.
According to the design:
- The goal of the modification is to remove the responsibility from campuses to determine or maintain the Primary Job.
- The nightly automated program evaluates all employee job rows and inserts new PS_JOB rows when a different primary job should be assigned based on the established criteria.
- This logic is applied consistently across all business units, ensuring that campus-made changes do not remain in place if they conflict with the automated rules.
Because of this, any manually set Primary Job value will be replaced the next time the process runs, if the system determines a different job should be primary.
How will the Primary Job be selected when the process runs?
The automated process evaluates active employee job records within the same campus using the following hierarchy:
- HR Status = Active & Per Org = Emp
- Empl Class hierarchy
- Highest FTE
- Earliest hire date
- Lowest employee record number
The job that meets the highest applicable criteria is flagged as the Primary Job.
If a campus manually maintains the Primary Job field will the process override?
Yes — the automated Primary Job Indicator process will override any manual changes made by a campus.
End of Article