Reviewing Tips for Retroactive Processing

The following table provides hints on using retroactive processing.

Question	Answer
Can Absence Management calculate retro across countries?	The default retro method, retro process definitions, and trigger event IDs are defined by country. The system does not calculate retro across countries. However, if a payee transfers to another country, and it's later discovered that the payee should have received additional entitlement while employed in the first country, it might be possible to process retro for that payee even though he or she is inactive in the original country. This depends on the forward limits that apply at the pay entity level and other processing rules that determine how long after a payee is inactive he or she remains eligible for retroactive processing.
What happens when multiple triggers are generated and each points to a different retro process definition?	Suppose that multiple retro events occur, causing multiple retro triggers to be written to the trigger tables. If these triggers call for that calendar run to be processed (recalculated) using different process definitions, a conflict will occur. In such a situation, where the events that cause retroactive processing activate the application of more than one process definition for the same payee in the same calendar, the system writes an error message and does not process retro. Only the current period is calculated. Retro triggers are not marked as processed. Note: The retro conflict method that is specified on the Countries page does not apply to the conflict situation described here. In this situation, the retro conflict method will not resolve the conflict. However, you can change the event ID that is associated with the retro trigger, using the Payee Trigger Retro Expanded page. For a payee, you cannot have more than one process definition resulting from the retro events that cause retroactivity for that calendar run. The same process must apply for all calendars in the calendar group.

Question

Answer

Can Absence Management calculate retro across countries?

The default retro method, retro process definitions, and trigger event IDs are defined by country. The system does not calculate retro across countries. However, if a payee transfers to another country, and it's later discovered that the payee should have received additional entitlement while employed in the first country, it might be possible to process retro for that payee even though he or she is inactive in the original country. This depends on the forward limits that apply at the pay entity level and other processing rules that determine how long after a payee is inactive he or she remains eligible for retroactive processing.

What happens when multiple triggers are generated and each points to a different retro process definition?

Suppose that multiple retro events occur, causing multiple retro triggers to be written to the trigger tables. If these triggers call for that calendar run to be processed (recalculated) using different process definitions, a conflict will occur. In such a situation, where the events that cause retroactive processing activate the application of more than one process definition for the same payee in the same calendar, the system writes an error message and does not process retro. Only the current period is calculated. Retro triggers are not marked as processed.

Note: The retro conflict method that is specified on the Countries page does not apply to the conflict situation described here. In this situation, the retro conflict method will not resolve the conflict. However, you can change the event ID that is associated with the retro trigger, using the Payee Trigger Retro Expanded page.

For a payee, you cannot have more than one process definition resulting from the retro events that cause retroactivity for that calendar run. The same process must apply for all calendars in the calendar group.