The purpose of this document is to assist campus users with known issues in the Absence Management module.
Excess Plus/Minus
Excess Plus/Minus involves the tracking of non-exempt, salaried employees on non-standard schedules and the number of hours they work in a pay period versus the expected hours to be worked in a pay period.
Known Issues:
- Current data related to excess plus/minus in CHRS is not calculated correctly. Some examples include:
- Employees with mid-month FTE changes
- Terminated employees and employees on leave with standard schedules
- Part-time employees with the correct schedule assignments
- Employees with multiple part-time positions
- Conversion calendar accruals
- The AM Multi-Reports are only showing calculated values from previous months. The results for the current period are blank.
- Excessive accumulator values of 0 leading to potential data storage/processing issues
Current Workarounds:
- It is currently required that campuses track excess plus/minus outside of the system. An example spreadsheet for tracking is available below.
- Campuses can monitor employees on non-standard schedules using the CSU_TL_ALTERNATE_WORK_SCHEDULE public query.
- Review the calculated values using the CSU_AM_AUDIT_EXCESS_PLUS_MINUS public query.
Absence Forecasting / Unpaid Absences
Known Issues:
When absences are created by timekeepers or administrators on the Create and Maintain Absences or Absence Event Page, the system doesn't stop them from submitting an absence that an employee doesn't have sufficient balance to cover. From the system's perspective, an absence being submitted by an administrator bypasses the forecasting value. Users must check the Forecasting Status before submitting absences and delete a request if the status is "not-eligible". This is delivered Oracle behavior and there are no plans to change this behavior.
Current Workarounds:
Campuses can monitor the CSU_AM_ABSENCE_OVER_USAGE public query for unpaid absences.
Existing absences aren't updated automatically when the employee's schedule changes
Known Issues:
When an employee submits an absence request, the associated absence event calculates the duration of the absence using the employee's schedule for the requested time period. If the employee's schedule for the time period changes after the request is submitted, the duration of the absence event is not updated to match the new schedule for the time period.
Example: A campus uses a 9/80 or 4/10 schedule for the summer. If an employee submits an absence for July before the schedule changes are in place, it will display the original schedule's hours for the day instead of automatically updating to the new scheduled hours for the day.
The calculated values in the AM tables use the new schedule, but the displayed values on the employee self-service and manager self-service pages for the request will show values for the original schedule.
Current Workarounds:
Campuses will have to cancel the absences and resubmit the absences after the schedule updates have been completed in order for the system to update the absence event to use the new schedule information.