Common RPCIPE Errors
RPCIPE errors are present when there is a disconnect with funding, an overpayment processed incorrectly, or an issue with bank details.
Walk through the error codes listed below to determine which issue is causing the RPCIPE error. The error report will indicate if the RPCIPE error is caused from reason codes 5 or 6. In these cases, you will want to focus your attention in those areas only.
1. Position (PO13) funding
- Ensure that the position has a cost distribution record.
- Check the effective date of the cost distribution. It must be valid for the entire time the employee is in the position, not just for the pay period.
- Ensure that each of the cost distribution fields contain values (fund, functional area, cost object, project structure, etc).
2. Position (PO13) relationship information
- 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).
- Verify that the staffing percentage field at the bottom of the relationship is equal to 100%. It must be 100% whether a full time or part time employee.
3. Employee (PA30) position information
- Review the employee’s Organizational Assignment (0001) infotype. Check that a position 99999999 is not present during an active period. If the employee is withdrawn, check to make sure the position is not changed 1 day too early.
- If an employee has had an Appointment Change, ensure that both the old and the new position are checked using 1 and 2 above. This includes positions that were active during a retro in the period.
- Review the employee’s Actions (0000) infotype records. An employee should never be hired or rehired into position 99999999.
4. Terminated employee (PA30) errors (Payroll Results)
- Ensure that the employee’s buyout information occurs during the active period. If it does not, a Cost Distribution (0027) infotype record must be created for the period that the payout occurs.
- Check the terminated employee’s Payroll Results to see if Employer Health is being paid for a terminated period. Delimit Health Plans (0167) accordingly.
- Review Payroll Results for any other pay during a terminated period. If paying a separated employee, a Cost Distribution (0027) infotype record must be created for the period that the payout occurs.
5. Employee (PA30) Bank Details
- Verify that the employee has a valid Bank Details (0009) infotype record effective through 12/31/9999.
6. Employee (PA30) with an overpayment recovery processing
- 3223 – Repay Plan Deduction found in Recurring Payment/Deductions (0014) infotype
- 3224 – Repay Balance found in Additional Payments (0015) infotype
- Verify that if you have a record along with a corresponding 3224.
- Verify that the start date for the 3223 and 3224 are the same. (Do not use 12/31/9999 as an end date).
- If the is an odd amount, make sure that two 3223s are setup to accommodate for the different amounts.
- Verify that if the balance of the 3223 has been paid, that the Recurring payments/deductions record has been appropriately end dated.
- Verify that if the employee is hourly, that time has been entered for the period. Recipe will be out of balance for an hourly employee with no pay in a period that is attempting to process a 3223.
- Verify that the 3223/3224 records are created and effective only for the current or future periods. Wage Type 3223/3224 records that are created in a retroactive period will cause an error. Look in Deductions Not Taken (DDNTK) for each period; any WT3223 in DDNTK will cause an error.
- Check for WT3223/3224 entries that have been changed or removed in prior periods. Look in Deductions Not Taken (DDNTK) for each period; any WT3223 in DDNTK will cause an error.
7. Employee (PA30) new hire or rehire action
- 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 Jan 2 – NOT Jan 1)