|
HR Transactions
02/01/22 IX Range Adjustment - PayPath Downtime
Effective February 1, 2022, the UCPath Center will process a range adjustment for the IX population. Per the new bargaining unit agreement, the Unit 18 salary scales have been adjusted by a general range adjustment increase of 7.0% with the minimum starting salary point removed, and transitioned from a salary range to a salary scale with distinct salary points (with 3% increments between points). The new salary scales are available on the APP website.
The UCPath Center will process this range adjustment from 01/29/2022 through 02/04/2022. During that time, there will be a freeze on PayPath transactions for any Job Data records that are part of the IX population. Transactions can resume on 02/05/2022.
If you have any questions about this range adjustment, please contact appolicy@berkeley.edu.
PayPath Defect Found
An issue has been identified in PayPath related to retroactive transactions. Retroactive insertions using PayPath, have resulted in the Salary (i.e., Compensation Rate) being completely BLANKED out on one more more future-dated job data rows from the row being inserted in the PayPath transaction.
Example: PayPath transaction to insert a 07/01/2021 ‘Job Reclassification-Upward’ update shows correctly inserted in Job Data as of 07/01/2021, but an already existing 12/03/2021 row now has a blank salary.
Issue has been raised to the UCPath Center. In the interim, please double-check any retroactive PayPath transactions. As you review updates in Job Data, check the historical entry, but also whether any greater effective-dated rows (including the most current) contain accurate information (especially the Compensation Rate field).
If you would prefer to submit correction requests to UCPath using the Job Data Update form, make sure to mention this defect is the reason you are submitting a correction request through the form (instead of attempting a retro PayPath that might cause an issue that then requires a Job Data Update Form Job Data Update form anyway). This will prevent UCPath Center from pushing your correction request back citing use of PayPath to process your transaction.
HR Template Transaction Defect - Update
Currently, there is a known issue in which, when an employee is being transferred from an Employee Class with an end date to a Career position, the end date is carried forward instead of being removed.
An update was posted to the ticket that the workaround has changed and the issue should be resolved through a project on the UCPath Roadmap.
Previously, the workaround was to remove the end date through a PayPath transaction after the Template transaction was processed. Instead, transactors should enter comments/notes on the Template transaction to ensure that the UCPath center removes the value.
Issue Resolved - Termination Template Approval
Since the UCPath upgrade, the UCPath Center has shared that there was a known issue when a termination template was submitted with an effective date that is less than an existing row in JOB, the system was not giving the ability to approve the transaction. Though no specific cases of this happening locally here at Berkeley have been identified, we wanted to share that the issue has now been resolved.
Multiple CalNet Records
Multiple CalNet records. Duplicate records can be created through typos on transactions or by not checking the Person Org Summary or the Person Search Match section to see if a person currently exists before creating a new employee ID.
To help prevent this, please review the Person Org Summary and the Person Search Match pages before creating a new employee ID. Furthermore, transactions should be carefully entered/approved to help mitigate transposed numbers, names, and DOBs in DD/MM/YYYY format, which all cause multiple CalNet records to be created for existing CalNet users.
What is the impact on the employee? The employee will not be able to log in to UCPath or CalTime; employees will not be able to record hours or get paid. Often these users do not know where to go for help, so help tickets get bounced around for days, or weeks, or even months before the issue is resolved. In some cases, users with multiple records end up not being able to register for classes or miss school-related deadlines.
CalNet - Employee Impact of Late Terminations
Employees and Affiliates who are terminated in UCPath well after their end date do not get a grace period notification, and could have their CalNet and email accounts expire with no notice. This causes stress and anger among users who are impacted, and who have no chance to transition off of campus services.
Example: A volunteer in your department has an appointment in UCPath and will leave on 1/2/22. The affiliate should get a 30-day grace period, and have a CalNet expiration date of 2/1/22 . If their termination is entered after 1/2/22, their grace period will be shortened or eliminated altogether. Suppose the termination is entered on 3/1/22: the volunteer will lose access immediately to their CalNet account, with no warning, because their expiration date is still 2/1/22.
|
