RTI: Function Get_irregular_payment In Package PAY_GB_RTI_FPS (Doc ID 1539143.1)

Last updated on JANUARY 10, 2017

Applies to:

Oracle HRMS (UK) - Version 12.0.6 and later
Information in this document applies to any platform.

Symptoms

Testing a User Defined Function to automatically set the irregular Employement indicator at FPS run time.

Within the PAY_GB_RTI_FPS.get_irregular_payment function, before it esablishes if it needs to use the UDF attached to this field in the configuration values, if first makes sure that this field is not populated in the assignment EIT, as this will override the function.

The problem however is that the cursor csr_irregular_payment_eit within PAY_GB_RTI_FPS.get_irregular_payment is looking at the wrong AEI_INFORMATION value to see if the irregular payment field is populated in the EIT.

The cursor is looking at AEI_INFORMATION1, which is the wrong field, this field is the 'Number of Pay Periods' so if an employee has the Number of Pay Periods populated in RTI Information EIT, this cursor thinks that the Irregular Payment field has been populated and therefore will not execute the User Defined Function to fetch the value at runtime.

The existing cursor is below: it should look for AEI_INFORMATION3 not AEI_INFORMATION1

cursor csr_irregular_payment_eit is
 select AEI_INFORMATION1 from per_assignment_extra_info
 where assignment_id = p_assignment_id and INFORMATION_TYPE = 'GB_PAY_RTI'
  and AEI_INFORMATION_CATEGORY = 'GB_PAY_RTI';

Workaround: having to remove 'Number of Periods Covered from employees RTI Information EIT as otherwise UDF attached to irregular payments field will not be called

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Attached UDF in Configuration values for RTI Information to UDF is called to set Irregular Payment Flag at FPS Runtime.
2. Populate Number of Periods Covered for an employee in RTI Information EIT.
3. Run FPS
4. UDF attached to Irregular payment field is not run as the code thinks its populated when its not.



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms