Hi Guys,

Does anyone know how to identify if the Element is being processed by Retropay and not Payroll?

I have created a Formula Function to query PAY_PAYROLL_ACTIONS using Payroll_Action_ID context; however this returns the Payroll Action which initially processed the Element, not the Retropay which is re-processing...

Any help would be great!
Cheers,
Gavin

Hi Gavin,

Can I firstly ask why you are trying to identify this. If the element definition is set up for retropay then if the assignment has been triggered for retro it will get re-processed.

Cheers,

Delboy

Hi Gav la,

Please run the Retro-Notifications Report (Enhanced) - PDF report, which will show you the element is marked to be processed in retropay process and subsequently run the retropay process, if the process didnot create any retro entries,please check the retropay logs including slave processes logs, which will show you the reason for the elemnt not being processed or the reasons of the issue.

Hope this helps you.
Cheers mate
Sudhir

Hay sudhir! The issue we have is when the element is being run in retro... I am trying to get the formula to do something slightly different when processes by retropay...

Cheers for commenting mate! And always good to hear from you!
Gav

The reason appears to be due to update recurring not playing nice. We basically want to exclude the return value if run in retro.

Hope this makes sense! Will look too at the requirement again to see of there is another way... Must be!

Hmmm,

So you are changing the formula retrospectively, then running retropay. I try to steer clear of update recurring's. Seem to remember there being a problem with rollbacks.

Delboy

Hello Chaps,

I also remember there being an issue when using Update Recurring from our DWP days. John Hicks made me aware of this issue but it was many years ago.

Obvious suggestion is Metastink but I never can find anything there of any help at times.


Paul

Cheers Paul! I do remember seeing a Function when I was at DWP to do pretty much this; cannot however remember how it worked, and as Del said above why you would need to worry about it!

Metastink! Love it!! Haha! Have had a good look around there, with no joy...

Cheers guys!
Gavin

Hi Gav,

Would like to re-iterate Delboys question, why would you want to do something different in Retro to Payroll, that goes againt the core concept really, if you don't want a value then do not set element up for retro

Or what are we missing in your somewhat unusual requirement

Cheers

Gus