Potential Life Event not Triggering When Assignment Data is Changed
Last updated on JULY 18, 2016
Applies to:Oracle Advanced Benefits - Version 12.1 HRMS RUP4 and later
Information in this document applies to any platform.
On 12.1.3 HRMS RUP4 version, Oracle Advanced Benefits
After upgrade to 12.1.3 Rup 4, when re-hiring an employee using custom template, the Re-hire potential life event is not triggering. The trigger is based on Assignment Table - 'Change Reason' field.
Note: The same works fine when updating the Assignment Form > Misc > Reason field.
BEN_ASG_IO_JOB_ID, BEN_ASG_IN_JOB_ID, BEN_ASG_IN_EMPLOYMENT_CATEGORY and BEN_ASG_IO_EMPLOYMENT_CATEGORY values are getting interchanged between the Old and New vlaues i.e. BEN_ASG_IO_JOB_ID has the value that BEN_ASG_IN_JOB_ID is supposed to contain and vice versa. Same is the case with BEN_ASG_IO_EMPLOYMENT_CATEGORY and BEN_ASG_IN_EMPLOYMENT_CATEGORY.
This occurs only when using Assignment API call after hiring an employee. The same works fine when creating and updating employee using People > Assignment form.
Steps to Reproduce:
The issue can be reproduced at will with the following steps:
1. Create Person Life Event Change based on assignment Table.
2. Use SSHR/Assignment API/Template to update the employee assignment data.
3. Potential LE not triggered.
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