GPUK - Additional Postponement Rows Added in Case of Rehire (Doc ID 2931632.1)

Scenario: When the pension auto-enrollment process is run multiple times in the same pay period and if rehire(s) are processed, the code cannot identify that the rehire(s) has been processed and therefore a new postponement row will be added.
As a result, when an employee is rehired, additional postponement rows have been added for the same or each subsequent calendar group.

Steps to replicate the issue: 

1. Navigate to Global Payroll and Absence Mgmt > Payee Data > Pension Information > Assign Scheme GBR > Assign Scheme GBR and check the data before rehiring the employee;
2. Navigate to Workforce Administration > Job Information > Job Data and check the employee status before the change;
3. Navigate to Global Payroll and Absence Mgmt> Absence and Payroll Processing> Calculate Absence and Payroll Latest Payroll results before the change;
4. Navigate to Workforce Administration > Job Information > Job Data and add a new row with Reason Code "rehire";
5. Navigate to Global Payroll and Absence Mgmt> Absence and Payroll Processing> Calculate Absence and Payroll Run payroll after rehiring the employee;
    -- First run Application Engine (AE) process by Cal Run ID with process run date as of 24/8/22.

    -- Then run subsequently using process run date 25/8/22.
 6. Navigate to Global Payroll and Absence Mgmt > Payee Data > Pension Information > Assign Scheme GBR > Assign Scheme GBR and notice that there are 2 rows of Postponement added. Only one should be added.