My Oracle Support Banner

Penserver: After Employee Is Moved To Another Scheme Name And Category Are Not From Same Scheme (Doc ID 2206795.1)

Last updated on SEPTEMBER 06, 2019

Applies to:

Oracle HRMS (UK) - Version 12.1 HRMS RUP8 to 12.2.6 [Release 12.1 to 12.2]
Information in this document applies to any platform.



1 - Apply patch 21060739
2 - Enter a new test employee from 01-JUL-2016 > on Nuvos Pension scheme (PCS)
3 - Ran Penserver History to check that the employee is picked up and all is fine (shows N for new record on the 01-JUL-16 as it should).
4 - Entered a sickness absence from 20-JUL-16 to 15-AUG-16 (the employee will be on Full Pay for this sickness)
5 - Date tracked to 01-AUG-16 and transferred them to Alpha pension scheme (CSO)
6 - Ran the Penserver service history extract again and you can now see 3 x extract results for the employee
        a - first is the new employee record, showing Nuvos as the scheme, Scheme category = C) - This is fine and correct
        b - second is the change to Alpha, showing as T for transition. Alpha is the scheme name and scheme category = A (from 01-AUG-2016) - this is correct
        c - the third row shows the return from sickness break (RB) on the 16-Aug, Scheme Name = Alpha, but the scheme category is C where it should be A.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.