If no retro triggers are displayed,
first look for the obvious:
1. Are there any confirmed
paychecks with a pay end date later than the date of the change to JOB or
Additional Pay? You won't get a retro request unless there is pay to be
recalculated.
2. Does the Paygroup Table have Retro Pay Program and Retro Trigger Program specified on ALL effective dated rows? This is not absolutely essential, but it is easy to overlook missing values on earlier effective dated rows that could be pertinent to the JOB or Additional Pay change.
2. Does the Paygroup Table have Retro Pay Program and Retro Trigger Program specified on ALL effective dated rows? This is not absolutely essential, but it is easy to overlook missing values on earlier effective dated rows that could be pertinent to the JOB or Additional Pay change.
3. Is your Retro Pay Trigger
program defined at the FIELD trigger level?
4. Have Retro Pay Trigger
Values been defined for the fields you are changing?
5. Is there something on the
row being inserted/updated/deleted that is different, and does that field/value
match what is on the Retro Trigger Values definition? Again, watch out for
effective dates.
6. Esnure that the earnings codes
that are eligible for retro pay are setup in the retro program tbl.
In 9.1, retro requests are no longer
created through SavePostChange PeopleCode, we use Event Processing to generate
the requests.
1. On your Application Server, have pub/sub transactions been enabled?
2. Has the Integration Broker gateway been configured, and is it running?
1. On your Application Server, have pub/sub transactions been enabled?
2. Has the Integration Broker gateway been configured, and is it running?
