'Detected' Life Events Not Changing to 'Voided' if Employee Not Eligible
(Doc ID 419619.1)
Last updated on JANUARY 16, 2020
Applies to:Oracle Human Resources - Version 18.104.22.168 to 22.214.171.124 [Release 11.5.10]
Information in this document applies to any platform.
Participation Process: Grade Step Progression
On 11.5.10 in Production:
Find that a problem has been occurring since we started running the Participation Process: Grade
Step Progression. The process is run daily to capture and process salary increases for employees
who based on eligibility requirements are eligible for a salary increase. All employees below
range maximum are receiving a Potential Life Event, even though based on eligibility profile are
not eligible for an increase or progression. The increase or step placement does not process (which it shouldn't because ee's are not eligible), but the Life Event remains in Detected status.
Expect that Potential Life Events should be voided rather than remain in Detected status.
The issue can be reproduced at will with the following steps:
1. US Super HRMS Manager > Processes and Reports > Participation Process:
Grade Step Progression > Parameters are populated:
-Effective Date: 11-Nov-2006
- Detect Temporal Events: None
- Validate: Commit
- Plans Not in Program: No
- Only Programs: No
- Potential Life Events to Process Date: 11-Nov-2006
2. Submit Process
3. People > Benefits Service Center >Desktop Activities > View Person Life Event>Potential Life
The issue has the following business impact:
Due to this issue, when changes to a Life Event are needed to be made by the Benefits Analyst the
Analyst has to scroll through numerous lines before finding the Life Event needing to be updated.
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