7/11/2021 Document 2135984.

1
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

Oracle Payroll 'Retropay Setup for Elements' Frequently Asked Questions (FAQ) (Doc ID
2135984.1)

In this Document

Purpose
Questions and Answers
  Why should I use a different element as the retro element when I do the Retropay setup?
  When is Retropay setup required for existing retro elements?
  Can I use an element as the retro element for itself in the Retropay setup?
  What should I use as input values for the retro element?
  What should I do if I have already used an element as its own retro element?
References

APPLIES TO:

Oracle Payroll - Version 11.5.10.2 and later

Information in this document applies to any
platform.

PURPOSE

 The purpose of this article is provide answers to some frequently asked questions in regards to RetroPay Setup for Elements 

QUESTIONS AND ANSWERS

Why should I use a different element as the retro element when I do the Retropay setup?

When payroll runs are reprocessed in memory, the Retropay (Enhanced) process will not take into account existing retro
element entries, because the existing retro elements are already accounted for by their base element entries in the
original payroll periods.

When is Retropay setup required for existing retro elements?

Retropay setup is required for existing retro elements when, in a specific functional scenario, you need the existing retro
element entries to be processed in the in-memory payroll runs. For example, if Retro Salary is the retro element for the
Salary element, and you need Retro Salary retro entries to be processed in the in-memory payroll runs, then you must
create a new element, Retro Retro Salary, as the retro element for Retro Salary.

This setup must be completely tested for the specific scenario, because the retro element entries will also be accounted
for in the original period by the base element entry.

Can I use an element as the retro element for itself in the Retropay setup?

Yes, but this is not recommended by Oracle.  When you set up Retropay for an element (for example, Salary), you should
always create a new element (for example, Retro Salary) and use it as a retro element.  If you use Salary itself as the
retro element, there are certain scenarios that can result in undesirable results.

When Retropay setup is done for the element that is used for creation of retro element entries, these retro element
entries will be picked up in the in-memory payroll runs.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=nqz5e4j2k_1723&id=2135984.1 1/2
7/11/2021 Document 2135984.1

What should I use as input values for the retro element?

The retro element and the base element should have exactly the same set of input values with the same names and the
same display sequences.

What should I do if I have already used an element as its own retro element?

Create a new retro element and attach it to the base element in the Recalculation > Retro Components form.  This is not
a date-tracked form, so Retropay will always use the new element for retro entries.

For example, add RetroSalary as the retro element for Salary, and use this in place of the Salary element in new periods.

REFERENCES

BUG:19905132 - CORRECTION RETROPAY REVERSES SPECIAL TAX DEDUCTION CASES RETROPAY OVERLAP RUP7
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=nqz5e4j2k_1723&id=2135984.1 2/2