Last updated on JUNE 20, 2017
Applies to:Oracle HRMS (UK) - Version 12.1 and later
Information in this document applies to any platform.
Checked for currency 11-June-2015
Qn1:Could you confirm that it is only the Opt Out Date which users should ever manually update?
Qn2: Is it correct to think that if the user chooses to update any of the other fields then the process will not look at the update?
Also, what happens if a non eligible job holder or a worker chooses to Opt out - would you expect the user to update the Opt Out Date in this instance too or not?
Qn3: Is it allowed for user enter the postponement type input value at employee level?
Qn4:Where the pension auto enrolment has been run in commit mode then the Opt-Out Date , Qualifying Scheme Exists (as 'NO') and Qualifying Scheme Name(as NULL) should be updated once the employee opts out - this would be done as a correction if the employee never joined or as an update if they opted out a number of months later?
Where the employer has done a manual assessment prior to running the process in commit mode then the following fields would need to be updated:
Pension Classification, Eligible Job Holder Date, Auto Enrolment Date, Opt Out Period End Date, Opt Out Date. (The Qualifying Scheme Exists field will be populated by default to No).
This could be done as either a correction or an update from the staging date (if the element exists prior to the staging date).
Can you confirm this is correct?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms