Temporal Life Events Not Triggering Through Batch Process
(Doc ID 1950456.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Fusion Benefits - Version 184.108.40.206.0 and later
Oracle Fusion Benefits Cloud Service - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Temporal Life Events such as Age Changed and Length of Service Changed are not getting triggered when the Temporal Batch Process is run.
Note that these are getting triggered when any life event is processed manually with a life event occurred date greater than when the associated derived factor will pass.
Expectation is that the Age Changed seeded temporal life event should trigger as there is Age >=21 years Derived Factor with Min 21 and Max 99 Years configured and attached at the Plan Type In Program (PTIP) level.
Note: When manually run an Admin event with life event occurred date of, for example, 11/1/2015 or greater, the Age Changed Life Event is getting triggered as expected. This confirms that the setups are correct, but it somehow does not trigger when run through the Temporal batch process.
Steps To Reproduce:
1) Take an employee turning 21 years before the date in the example above, before 11/1/2015.
2) Run the 'Evaluate Temporal Event Participation Process' with an effective date of 11/1/2015 or later on the employee turning 21 years.
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