When a pay table ends or no longer covers the employee's pay plan, grade, step, and Duty Station location, you can update the pay table, pay rate determinant, and the salary fields of the affected position and employee records using a mass process. The mass process generates RPAs that document the resulting changes to the person records.
Use the Mass Salary Pay Table Identifier Change window to update employee and vacant position records from the deleted or changed special rate table to a default Oracle US Federal pay table.
In the Find Mass Salary window, choose New to start a Mass Salary Pay Table Identifier Change action, or query an existing action.
Enter the criteria: a unique name, the Pay Table ID, the Effective Date, and the Locality Area.
The first time that you process the pay table identifier change, set the effective date of the action to May 1, 2005 to ensure that you update all applicable employees and retained grade employee records.
As Additional Criteria, choose the Organization, Agency Code, Personnel Office ID, and Duty Station from the list of values for each field.
Note: The volume of records affects the amount of time it takes to display the Preview run results. You can shorten this time by processing employees in batches. Enter Additional Criteria to restrict the selection.
Enter the Pay Plans and Pay Rate Determinant codes (PRDs) that apply to the pay table and the salary adjustment.
If you are terminating the special rate table, to process all affect PRD records, choose All from the PRD list.
If the termination or change does not apply to each grade for the Pay Plan/Pay Rate Determinant, you can specify the applicable grade. Click Grade/Level to display the grade details, and enter a different grade.
Save your results.
The Status field indicates the phase of the process. The status is Unprocessed until you execute the action (Submitted) and the application creates an RPA (Processed). If there is an error in executing the action, the Status field changes to Error.
See: Error Handling
If you require additional LACs/Remarks, other than those specified, click LACs/Remarks, and select the applicable Legal Authority Codes and Remarks from the list of values.
Choose Preview to view the run results.
The Preview window lists all employees who meet the criteria as of the effective date, displaying old and new pay information for them. The application also lists employees on Retained Grade, determining their eligibility based on the PRD and Retained Grade Pay Plan.
Deselect the employees to exclude from the mass action.
You can select and deselect multiple records at a time:
To select all the employee records, choose All from the Selection list. You can then manually deselect the records that you do not want the application to process.
To deselect all the employee records, choose None from the Selection list. You can then manually select the records that you want the application to process.
To have the application select a few records from the list of retrieved employee records, deselect the records you want processed. Choose Invert from the Selection list. The application selects the previously deselected records, and deselects the remaining records.
The application displays the comments field where you can enter a reason for excluding that person or position.
Save your results.
When you are ready to run the final results, click Execute from the Final Pay Table Change window.
The mass process initiates a:
NOAC 800 Change in Data Element action if the PRD changed but not the basic pay values
NOAC 894 Pay Adjustment if the basic pay values changed
The mass process updates the:
Position's US Federal Valid Grade
Person's Retained Grade extra information
Locality or SR Supplement element with the applicable locality or special supplement amounts
If more than one salary action occurs on the same effective date for an employee, the application processes the NOAC with the highest priority and returns the other NOACs to the person who submitted the RPA for update to the database.
See: Order of Processing
For current and retroactive actions, you may wish to update the RPAs to the database before your normally scheduled Process Future Dated RPA concurrent manager process runs, so that users can begin processing actions based on the new values in the employee records.