Common RPCIPE Errors

Before beginning, ensure you understand whether the employee has retroactivity (retro) in the period. RPCIPE errors have multiple causes.

Identify the RPCIPE error numbers provided within the Payroll Cutoff Errors List and match it to the numbers outlined in the guidance below. For example, if the RPCIPE error in the Payroll Cutoff List indicates "Most likely cause: Please see error #5 & 6..." you will focus only on error numbers 5 and 6 below. 

If the employee has retroactivity, the RPCIPE error can be caused in any period within the retro. If the employee should not have retroactivity and the retro does not contain a Difference (/551) within a payroll simulation or stored payroll results, you can email a request to HeretoHelp@ofm.wa.gov to kill the retro for the impacted employee. 

1. Position > Cost Distribution (PO13)

• Active Position Cost Distribution: Ensure that the position has an active Cost Distribution (1018) infotype record with valid funding.
• Valid Funding: Ensure that each of the Cost Distribution (1018) infotype fields contain valid values. None of the fields should be blank. If you are uncertain how the funding should be entered, contact your agency’s accounting department for assistance.
• Effective Date: Check that the effective date of the Cost Distribution (1018) infotype record is valid for the entire time the employee is a holder in the position, not just for the pay period.

2. Position > Relationships > Holder Relationship (PO13)

• Relationships (Holder): Verify that the employee is attached to the position from the exact date the employee is hired into the position and through the end date (or 12/31/9999 if the employee is active).
• Relationships (Holder): Verify that the Staffing Percentage field at the bottom of the Holder relationship is equal to 100%. It must be 100% even if an employee is part-time or a percentage employee.

3. Actions & Organizational Assignment (PA30)

• Review the employee’s Actions (0000) infotype records. An employee should never be hired or rehired into position 99999999. If an active employee is in position 99999999, contact the Personnel Administration Processor and Organizational Assignment Processor to compare and correct the Action or Position Holder data.
• Review the employee’s Organizational Assignment (0001) infotype records. Check that a position 99999999 is not present during an active period. If the employee is separated, compare the Position’s Holder relationship with the Organizational Assignment dates to ensure they start and end on the same dates.

4. Retroactivity Over Separated/Inactive Period or Paying a Separated/Inactive Employee

• Retroactivity Over Separated/Inactive Employee Periods: Review payroll results or a payroll simulation to determine retroactivity that crosses over periods where an employee was separated. If an employee was separated for a period within the retroactivity, create an Employee Cost Distribution (0027) infotype record dated the first day of the period after the separation through the last day of the period prior to the rehire. If there are multiple separations, create an Employee Cost Distribution (0027) infotype record for each separation period.
  Important: If the employee should not have retroactivity and the retro does not contain a Difference (/551) wage type within a payroll simulation or stored payroll results, email a request to HeretoHelp@ofm.wa.gov to kill the retro for the impacted employee.
• Separated Employee: If you are paying a separated or inactive employee, create an Employee Cost Distribution (0027) infotype record dated the first day of the period following the separation through the last day of the current period.
• Leave Buyout Processing: If a separated employee has a leave buyout, ensure the effective date of the buyout is during the active period. If it does not, create an Employee Cost Distribution (0027) infotype record dated the first day of the period following the separation through the last day of the current period.

5. Bank Details (PA30)

• Verify the employee has a valid Bank Details (0009) infotype record and the record is effective through 12/31/9999.

6. Overpayment Recovery Processing

Repayment Plan Deduction wage types are generally created and maintained within Recurring Payment/Deductions (0014) infotype records, but may also be found in Additional Payments (0015) infotype records. Recovery wage types are the actual employee deductions to repay an overpayment. The following wage types are generally used for overpayment recovery: 3223, 3101, and 2993.

Repayment Balance wage types are created and maintained within Additional Payments (0015) infotype records. Balance wage types are the total amount of the overpayment to be collected. The following wage types are generally used for overpayment balances: 3224, 3111, and 3003.

7. Newly Hired or Rehired Employee with Employee Cost Distribution Record (PA30)

• Start date of an employee’s Cost Distribution (0027) infotype record must be equal to the first active day for the employee instead of the first day of the period. (Example: Employee is hired on Jan. 2. The Cost Distribution (0027) infotype start date must be Jan. 2 – NOT Jan. 1). If the record does not start on the same day as the employee, correct the start date of the employee’s Cost Distribution (0027) infotype record.