Hi, Im after advice on R12 and Enhanced Retro. The current orgainsation is running on 11.5.10 with a possible of updating to R12, they currently utilise retropay by element/Retro Notifications, they do not wish to upgrade to enhanced retro. Is this possible if they upgrade to R12. Can someone also confirm that enhanced retro does not allow for Retro Pay re-tries.
For info, I am going forth with Retro Ehnanced with Overlap which should (fingers, toes, arms, legs, hair and anything else I can cross, crossed) have a massive improvment on performance. Enhanced is no different to Retro Notifications in that you run Retro Pay againts a small number of assignments. With overlap it uses Balance adjustments in memory to record the balances and will only go back to the Reprocess date, unlike all other versions of retro.
You have to have Parent element feeding into a Retro Element unlike before, especially if a balance is refered to within a formula as this will require every element feeding that balance to have a Retro element too (regardless of being used within retro or not)
I will document all findings and place them up here when complete.
As a heads up, we had serious performance issues with enhanced retro in 188.8.131.52. Numerous performance patches applied. They may have been resolved in R12.
Has the process changed in R12, cos in 11i you have no choice on the assignments you want the process to run for. It just runs for all the assignments that have been detected by the notifications process, unless you have manually removed them.
I am in the early stages of testing and designing Retro elements BUT from my own intial testing in a 12.1.3 environment you can select an assignment that has been marked for retro and deffer the action permenatly. Not go as far to remove the action as I needed it at the time but will make sure that it does as it says in the tin.
According to the white paper for Overlap, the bueaty of it all is it will not reprocess retro all the way back to the start of time so even if all assignments are marked to Retro it will only go back to there earliest reprocess date (this date being the date the trigger was triggered from!)
Get a full Retro environment next week so will update more as I go along :-)
You're right about the overlap but if you defer an assignment, the next time you run the notifications report, it changes the status to awaiting processing so you have to defer it every time if you never want it run.
Thanks Guys, for your update. I await your final results Paul,from your testing.
We are in the process of undertaking a proof of concept on the changes between 11.5.10 and R12, lots of questions being asked around enhanced retropay, and the new overlap facility.
I know what you are stating Delboy, that enhanced retro is like any other payroll process, therefore you should be able to roll-back and retry however many times that you want, but like I said the payroll department that I work for, was informed that you could not do this with enhanced, hence my question.