Divorce LE Trigger Detected On Contact Record Start Date And Not On Effective Date Of Change (Doc ID 1618576.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Fusion Benefits Cloud Service - Version 11.1.7.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.7.0.0 version, Manage Benefits

ACTUAL BEHAVIOR
---------------
Divorce life event is being detected by change in the relationship type from "Spouse" to "Ex-Spouse." This change is made with an effective date of the divorce. The life event is being detected, however, the occurred date selected is the start date of the contact record and not the effective date of the change.

No fast formulas are used in the life event detection:
Table Name = "PER_CONTACT_RELSHIPS_F
Column Name = "CONTACT_TYPE"
Old Value = "Spouse"
New Value = "Ex-Spouse"

EXPECTED BEHAVIOR
-----------------------
Life Event occurred date should be the effective date of the change

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Navigator > Workforce Management > Person Management as well as Benefits > Enrollment > Contacts.

Issue occurs regardless of how the contact relationship type is being updated, via Self Service or via Administrator.


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