Penserver Scheme contribution rate is not producing a complete extract
(Doc ID 1916092.1)
Last updated on AUGUST 20, 2018
Applies to:Oracle HRMS (UK) - Version 12.1 HRMS RUP6 and later
Information in this document applies to any platform.
On : 12.1.3 version, Penserver, production, patched to RUP6
The Oracle PenServer Interface relies on dynamic triggers to identify data changes which need to be reported in the periodic interface files. There are a number of known limitations to this event based model.
For example, the triggers associated with the Allowance History extract fire when a pensionable allowance element entry is created, or when a subsequent date track change is made to the element entry. These triggers therefore miss cases in which allowance rates change as a result of changes to reference data or indirect transactional data. These indirect changes do not result in an element entry update and so there is no event to prompt the new allowance rate to be reported by the interface. The following key scenarios are therefore missed by the standard interface:
1. A change to an Allowance Rate which is held in global value or a user defined table value.
2. A change to an employee’s rate of pay which impacts salary-based allowance rates. This applies to percentage based allowance and other salary based allowances.
3. A change to the rate of one allowance which indirectly affects the rate of another allowance that is dependant on it.
The same kind of "Missed Events" scenario arises for the Scheme Contribution Rate (SCR) extract. There are three scenarios in which an employee can have an SCR change which needs to be reported by the PenServer Interface.
Scenario 1: The employee has a pay change which results in a change in their Additional Contribution Rate mapping. In such cases the employee's “Contractual Pensionable Pay” field (held against their Assignment Extra Details of Service) is updated to show the new rate of pay. This “Contractual Pensionable Pay” field is tracked by the SCR Event Group so the change is picked up by the PenServer Interface and reported correctly.
Scenario 2: The employee has a pay change which coincides with a change to their Additional Contribution Rate percentage (held in the PQP_PCSPS_CLASSIC_SCHEME_CONTRIBUTION_RATES and PQP_PCSPS_OTHER_SCHEMES_CONTRIBUTION_RATES UDTs). In such cases the employee's “Contractual Pensionable Pay field is updated to show the new rate of pay, which results in the change being picked up by the PenServer Interface and reported. The change to the percentage rate value held in the UDT will be reported correctly in this case.
Scenario 3: There is a change to the Additional Contribution Rate percentage held in the UDTs, but the affected employee does not have a pay change in the period. The change to the UDT does not result in an event being generated for the employee assignment and so there is no trigger to tell the PenServer Interface to report a record for the employee showing the new rate.
The issue can be reproduced at will with the following steps:
1. From UK HRMS Manager
2. Make a change to an employee, or global value.
3. Run either of the processes specified.
4. Review the output generated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!