The effective date determines when the system updates an approved action to the HR database.
If the action is for the current date or an earlier retroactive date, the application updates the database and generates a Notification of Personnel Action.
The application applies the data contained in the Notification to the appropriate position and personnel records, replacing existing values with ones you entered or changed on your RPA.
If the RPA is for a future effective date, the application performs edit checks at the time the action is updated and again at the effective date.
This edit check permits the application to take into account any intervening changes, such as a salary change that would affect the pay amounts.
If during the edit check, the RPA data does not pass the edits, the application routes the RPA to the Workflow Inbox of the person who submitted the RPA for update so that he or she can make the necessary corrections. Once the corrections are made, the RPA can be resubmitted for update. The application reapplies the edit checks, and if they pass, updates the data to the database.
The application holds actions with future effective dates until the date is reached. You instruct the application to process future actions by setting up a Concurrent Manager program.
If multiple actions occur on the same future effective date for an employee, for example a Mass Salary adjustment and a Within Grade Increase, the application processes the NOAC with the highest priority and returns the other NOACs to the person who submitted the action for update to the database for review and possible cancellation or correction. For example, if an employee is due a Mass Salary and a promotion on the same effective date, the application would process the Mass Salary (the NOAC with the highest priority), and return the promotion to the person who updated the database.
If multiple actions occur on the same current or retroactive date for an employee, when you update the action, the application displays a message that lists actions that have been updated on that day as well as pending actions. You can then take the necessary steps to cancel or correct the other actions.
Warning: Do not change the NOAC order of processing. The order of processing is predefined so that employee records are properly updated and maintained. Changing the NOAC order of processing may severely impact the database when you update records. For example, if you assign Pay Adjustment NOAC 894 a lower processing number than Promotion NOAC 702, the application may incorrectly calculate the employee's promotion salary.