When a Job Data row is added for a payee, retro triggers for the payee's country as well as other countries are generated under Global Payroll > Prepare Payroll > Review Triggers.
During the Identification phase of Payroll/Absence Run Control, those retro triggers of the countries other than the payee's country should be deleted, but they are not.
For example, say you have a payee that has been only in FRA and DEU (2 JOB rows). This payee has 5 retro triggers generated. One in each of the following countries: FRA, DEU, USA, MEX, and UK (This is because there are Trigger Definitions setup for all these countries).
Now say that you open a Calendar Run for USA, what the system does is what is stated above. Since the payee is not in the USA and has never been in the USA, the payee will not be identified and the USA trigger will be deleted.
Only for the trigger for the country being processed will be deleted. That is what is meant by 'cleanup'.
If then a FRA calendar run is opened the system will find a match and will identify the payee for FRA and process the FRA trigger, but the remaining triggers for DEU, MEX and UK will not be deleted.
The user must open a calendar run for each of the countries and each calendar run will only delete the triggers for its own country the other triggers stay unprocessed until a calendar run for that country is opened and the system either processes the trigger because the payee is or has been in that country or the system deletes the trigger because the payee has never been in that country.
So, if there are triggers for countries where the user never runs a calendar run, these retro triggers will stay out there forever.
Not Applicable
The development team recognises that this is working as designed. Here is the explanation about this decision :
"A trigger is inserted for every country where a Trigger Definition for that record or record/field combination has been defined regardless of whether a payee has ever been in the country or not."
Next step, just before Identify (in GPPSERVC): "The system cleans up extraneous retro triggers during the Identification phase by searching the Job Table for the country that's associated with the payee's current job and Payee Process Stat (Payee process statistical) records for countries where the payee was formerly employed. If the payee has never been in the country that is being processed, the retro triggers for that country are deleted."
WORKAROUND:
If you do not have operations in some of the countries delivered for a specific GP release, the best solution is to setup the trigger status for these countries to "Inactive". In this way the triggers will not be created, other than for the countries that they really need to process.
KEYWORDS:
Pay Processing, Retro Triggers,Spotlight