RetroPay Series - Basics & Evaluation

In a nutshell, RetroPay manages back-dated or late notifications of changes to payroll processing.

Technically, Retropay will bring forward the late adjusted entries of payroll runs.
It make
- Accurate re-calculations
- Bring forward the delta payments or deductions in the current pay period

Examples of RetroPay Scenarios
1) Monthly Bonus declared in middle of the year, for the entire year.
2) RetroActive Promotion, salary increase or absence details

Evaluation of RetroPay Process

• RetroPay (by Aggregate)
• Standard UK process until 11i, now Obsolete
• RetroPay by Run
• Japanese Market Only, now Obsolete
• RetroPay by Element
• Current supporting version by Oracle in R11i, R12.0, R12.1, Obsolete in R12.2.
• Optional RetroNotification Report to view the assignments to be processed.
• Enhanced Features compared to earlier versions (correction/back dated awards)
• Can process one assignment or a group, using an Assignment Set.
• New from HR_PF.H
• "Start date" from which assignments needs to be back-payed should be provided by user and it is based on assignment set. In case of uneven back dates awards, or in case of larger assignment sets, this leads to performance issues.
•  RetroPay (Enhanced)
• A step forward to automatic RetroPay
• Current Supporting versions R11i, R12
• Addresses the main performance problem which exists with RetroPay by Element
• Mandatory to run RetroNotification Report, which picks up the assignments to be processed and also calculate the date from which each assignment to be back-payed.
•  QuickRetroPay 
• Retropay for single assignment, currently supported as concurrent program.
• Inspired by QuickPay
• Available from R12.1 RUP5 and R12.2.
• RetrNotification is automatically run by this process, so no need to run it explicitly.

What is Retro Notification?

1. It is the process which checks, if historical entries have been changed.
2. It will decide, the list of assignments for whom RetroPay should be run
3. Retro Notification works on Event Model in Oracle apps. 
4. List of events to be tracked should be included in event group and attach it to element.
5. For RetroPay by Element, Retro Notification is optional and it works just as reporting tool. But for RetroPay (enhanced), it is mandatory to run Retro Notification.

Following example explains the way RetroPay works.
It shows a sample calculation of, how it internally calculates and populates the results.