 Visit the OFM Service Portal at https://ofmwa.servicenowservices.com/sp to submit a ticket to the OFM Help Desk.
UPDATE: The tables within HRMS that caused the errors in the scenarios outlined below have been fixed. Please process any employees that were impacted by this issue before 8 p.m. on July 20.
Message sent 7/18/23 at 8:15 a.m.
OFM is aware of an issue that is impacting some wage types created for the CBA and Enacted 2023-2025 budgets that are erroring when attempting to be used. These errors may present themselves in any of the infotypes used to enter the new wage types. We were able to identify the scenarios causing the errors.
Prior Department of Printing Employees
If an employee was ever employed with the now-abolished Department of Printing (1300), use of the new wage types will error as processors are attempting to enter the new wage types. The error states “wage type not permitted for pers. Subarea grouping 1”. This error presents itself in multiple infotypes.
If you are uncertain if your employee was previously employed with the Department of Printing, within PA30 select All in the Period selection, highlight the Organizational Assignments (0001) infotype, and select the Overview button. Employees who have prior service with the Department of Printing will have Personnel Area 1300 listed within the PA column.
Daily Employees
If an employee is currently in one of the Daily EE Subgroups, use of the new wage types will error as processors are attempting to enter the new wage types. The error states “wage type not permitted for pers. Subarea grouping 4”. This error presents itself in multiple infotypes.
Next Steps
We have identified tables within the wage type configuration causing the errors and will update the tables as quickly as possible. We ask that you track any employees impacted so you can input the wage types for the employees after this issue is resolved.
For additional guidance on managing lump sum payments please see the 6/22/23 OFM Service News – Lump Sum Payments communication.
OFM will continue to update you on this issue. We apologize for any inconvenience this has caused.
Questions?
|
