Hello
We set the Cut off date for retro to 28-Nov-2011.( We got the script from oracle via SR to set this date in pay_recorded_requests. )
But the first run which is made on 29-Nov-2011 is picking all back dated changes. Cross checked few employees and found that even the changes on 2010 got picked.

Please let us know where we are going wrong.
Thanks
Ninja

Might be because of overlapping retro runs?

Take a look at this from MOS...

Overview: Overlapping Retropay Runs [ID 72281.1]

We are having R12 instance and we use retro(enhanced). I think the overlapping will not be the case for retro enhanced.

The Problem we are facing here is ,
1) Setup for retro enhance is done
2) As there were some Awaiting records we found which got created in the initial go live period (they tried to setup retro an year back ) , we changed the status to 'C' by script.
3) Set the recorded date to 28-Nov-2011 in pay_recorded_requests as per the oracle's advice.
4) ran retro on 28-Nov-2011.
5) Users deleted back dated non recurring element entries which are not related to retro elements on 28-Nov-2011
6) The MAIN PROBLEM is , the retro notification report is picking all back dated changes (including grade and basic changes) for the above employees even from 2010.

The issue is looking so strange and difficult to debug.

Ninja,

Had a simular issue when I was setting enhanced up for the first time at John Lewis (originally Retropay by Element). We run the Notification process before we opened the system up to users which seems to cement the recalculation date.

Tried the script Oracle suggest to use and it never worked.

Good luck


Cheers


Paul

Check that the legislation rule RETRO_OVERLAP has a value of 'N' in the table PAY_LEGISLATION_RULES. If not, then run the concurrent process Enable Retro Overlap for all UK Business Groups.

Delboy.

If you read the Oracle Docs associated with enhanced retro pay is does explain that it can go back earlier than the 'cutoff?' date

Great. What would be the program to set RETRO_OVERLAP for SA ( Saudi Arabia). I have checked and I found Enable Retro Overlap for all UK , Enable Retro Overlap for all US and Enable Retro Overlap for all US/UK?AU & CA only. Can I do a direct insert in to Pay legislation rules for SA and will it work?

INSERT INTO pay_legislation_rules
( rule_type
,rule_mode
,legislation_code)
VALUES
('RETRO_OVERLAP'
,'N'
,'SA');

I will anyways try this out now, but thought will ask expert opinion as well.

Regards
K