Payroll Simulation – Correct a RPCIPE Error
Use this report procedure to assist with identifying and correcting an employee’s RPCIPE error after executing a payroll simulation.
RPCIPE errors have multiple causes, most related to organizational assignment relationships, cost coding, banking information, or items in the Deductions Not Taken (DDNT) table. Note the RPCIPE error numbers outlined in the Payroll Error list and match it to the numbers in the RPCIPE Error Guidance. Not all RPCIPE errors will be identified or resolved using a payroll simulation.
A RPCIPE error will not appear as an error or redline on a payroll simulation or SP01 Spool. OFM posts RPCIPE/ALAS Errors on the HRMS Support Site. The only way to ensure RPCIPE errors are corrected is to view the next Payroll Cutoff Errors report.
This procedure shows how to read the payroll simulation results. Refer to other Payroll Simulation procedures for information on completing the report selection screen or other specific tasks.
RPCIPE errors are present when there is a disconnect with funding, an overpayment is processed incorrectly, or there is an issue with bank details. Most RPCIPE errors will not be identified by running a payroll simulation, but it is a tool that can help narrow down the possible cause.
The HRMS Processor Guide recommends running this report at minimum, on Payroll Days 1, 2, and multiple times on day 3, however processors should use this report as soon as the Payroll Cutoff Errors are posted.
To ensure accurate pay results, hourly employees should have accurate time entered in HRMS for the selected pay period.
Identify if an employee has an RPCIPE error by visiting the Payroll Cutoff Errors page and downloading the Payroll Cutoff Errors spreadsheet.
Tips:Once you open the Payroll Cutoff Errors spreadsheet, select the filter in the Error Source column to show RPCIPE errors.
Error reports are posted on Days 1 through 4 for a reporting period of Days 0 through 4 (Locked Employees).
Error reports posted on the afternoon of Day 3 and Day 4 (Locked Employees) will include redline errors, in addition to RPCIPE and ALAS errors.
Open the Common RPCIPE Errors list to identify the most likely cause of the error.
In this example, the spreadsheet shows the following error message: RPCIPE Error (Most Likely cause: Please see error 1-4 &/or 7). The most likely cause of the error can be identified by reviewing numbers 1, 2, 3, 4, and/or 7 on the Common RPCIPE Errors page.
Review the Most Common Solution to the RPCIPE error. We will use RPCIPE Error Cause Number 1: Position > Cost Distribution (PO13) in this example.
Tips:RPCIPE errors can have multiple causes and resolutions.
Complete the steps for Payroll Simulation – Execute a Payroll Simulation.
Click the folder to the left of the following selections to view all payroll periods that were processed during the current period:
- Successful personnel numbers
- Personnel number and employee name
- Payroll period
Tips:If there is retroactivity, you will need to view each pay period impacted by the retro data. To check for costing, navigate to the CO and C1 tables within the simulation for each of the pay periods.
Once you have selected the pay period folder, click the folder to the left of the following selections:
- USPS payroll
- Final processing USA
Click the folder to the left of the following sections to expand:
- EXPRT (Export results to database cluster RU)
- Input
Click C0 and C1 to view costing.
If either Table CO or C1 have entries, click the Plus sign to the left of the folders to open them.
Confirm that the employee is missing costing.
In this example, Table C0 displays no entries due to RPCIPE error number 1: Position (PO13) funding.
The functional area field in Table C1 is also empty due to the RPCIPE error.
Work with your agency’s organizational management, payroll, and personnel administration processors to decide how you should move forward. Since the employee is missing costing in this example, you will need to decide whether to correct the Position Cost Distribution record or create an Employee Cost Distribution override. See the Employee Cost Distribution procedures for more information.
Once you are notified by the organizational management, payroll, or personnel administration processor that the employee’s costing has been corrected, continue to the next step.
Repeat steps 3 through 10 to make sure the RPCIPE error has been corrected.
In this example, Table C0 now shows the correct employee costing.
Table C1 also shows that the RPCIPE error has been corrected.
Tips:Please follow these best practices during payroll cutoff to check for payroll redlines and RPCIPE/ALAS errors.
Days 1, 2, and 3 mornings:
- Agencies view their spool files for payroll redlines using transaction SP01.
- OFM posts RPCIPE/ALAS Errors on the HRMS Support Site. You will find the errors specifically on the Resources page.
Day 3 afternoon:
- Check the Payroll Cutoff Errors at 1:00 p.m. and 4:00 p.m. for your agency's errors. Employees on these lists will be locked out of final payroll processing if left uncorrected.
- The Day 3 afternoon run is the last chance to view errors, so agencies should work from the list to correct all errors prior to HRMS being closed to users after Day 3 processing – Afternoon list. The Day 3 afternoon run begins at approximately 3:00 p.m. and errors are posted at approximately 4:00 p.m.
- Processors have until 8:00 p.m. on Payroll Day 3 to correct errors prior to being locked out of HRMS for final payroll processing.
- If you need assistance to correct a problem, send a ticket to HeretoHelp@ofm.wa.gov so that OFM can assist you as soon as possible. Often the support team is working through a heavy volume of tickets for Days 2 and 3, so it lowers our ability to resolve late requests.
Example Scenarios
Below is an example of running the Payroll Simulation to find a RPCIPE error. It is not a comprehensive example of every scenario.
Example - Review RPCIPE errors for a single employee.
In this scenario, it is Payroll Day 1 and I have reviewed the spreadsheet on the Payroll Cutoff Errors page. I see an employee (40011210) has a RPCIPE error. As a payroll processor, I am going to take the following steps to correct the error:
I first confirm with the employee and/or supervisor that all time has been reported correctly for the pay period.