If you prepare RPAs in advance of the effective date, you can have the application update the actions to the database when the effective date is reached. To have the application process future-dated RPAs, you specify how often the application retrieves and updates to the database those RPAs that have reached the effective date. For example, you might schedule the process to run nightly, and the application would update those RPAs effective that day.

The number of transactions due for update on a given day may run into the thousands, such as a mass salary update. To improve the performance and expedite the number of transactions run, you can specify the number of batches to run simultaneously (number of threads), and the number of transactions in each batch (batch size).

You do not have to belong to the groupbox of the user who initiated the RPA; the responsibility you choose when logging onto the application determines which future-dated RPAs you can schedule. When you log in with a:

• Secure view responsibility, you can schedule the process for future-dated RPAs created in that secure view responsibility

  The application retrieves those RPA records where the business group ID of your current login matches the business group ID of the RPA originator's login.

• Non-secure responsibility, you can schedule the process for all future-dated RPAs

  If you have set up cross-business group functionality, the process runs for RPAs in all business groups. Otherwise, it runs for RPAs in your current login's business group.

Use the Submit Requests window.

   To schedule the process for updating future dated actions:

1. In the Name field, select Process Future Dated RPAs from the list of values.

2. In the Parameters field, enter the:

   • Personnel Office ID

     By specifying the POI, you limit the RPAs processed to those administered by that personnel office.

   • Batch Size, the number of transactions in each batch

     The default batch size is 1000.

   • No. of Threads, the number of batches to run simultaneously

     The default number of threads is 10.

3. To define a schedule, set the Run the Job options to run a request as soon as possible, at a specific time, or repeatedly at specific intervals.

4. Specify the Completion Options.

5. Choose the Submit button.

   If multiple actions occur on the same future 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 action for update. The recipient can then review, and if necessary process a Cancellation or Correction action.

   When the application processes the actions that are effective for that day, the application reapplies CPDF edits to validate the information contained in the RPA. To account for any system down-time, the application also updates any actions with earlier effective dates that might have been skipped when the system was off-line.

   If you have multiple POIs, you can repeat these steps to set up a processing schedule for each appropriate POI.