Collapsing Life Events

7/26/2019 Collapsing Life Events

1/12

Creating a New Life Event using Collapsing

RulesO R A C L E W H I T E P A P E R | J U N E 2 0 1 5


2/12

COLLAPSING LIFE EVENTS

Disclaimer

The following is intended to outline our general product direction. It is intended for information

purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any

material, code, or functionality, and should not be relied upon in making purchasing decisions. The

development, release, and timing of any features or functionality described for Oracles products

remains at the sole discretion of Oracle.


3/12

COLLAPSING LIFE EVENTS

Table of Contents

Disclaimer 1

Collapsing Life Events 2

Collapsing Life Events Example 8


4/12

2 | COLLAPSING LIFE EVENTS

Collapsing Life Events

When configuring a typical Benefits program there is usually a need to collapse several life events

into a single life event. In this paper we show one method to use without the need for a formula.

This same design can be leveraged for various rules that require the collapsing of life events into a

single event.

This is an example of How to create an Add Dependent Life Event that has multiple Person Changes

by using a Collapsing Rule.

Collapsing Rule Setup

Navigator: Benefits > Plan Configuration > Manage Benefits Life Events

Click on Create


5/12


Change the Session Dateto the date you have selected for the start of your setups. For Example: 01/01/2001.

All of the choices selected below may defer based on client requests. This is meant to just be a typical setup and

variations maybe needed per the requirements.

Name:Add Dependent (Or any name requested by the client)

Type:Personal

Occurred Date Determination: Event occurred date

Timeliness Evaluation: Process potential life event manually

Timeliness Days:90

Save and Close


6/12


Create the Add Spouse Life Event

Click Create

Click Create Person Change


7/12


Add any person changes that should trigger the Life Event. For Add Dependent Life Event this could be Child,

Adopted Child, Spouse and Domestic Partner.

Name:Add Spouse

Table Name: PER_CONTACT_RELSHIPS_F

Column Name: CONTACT_TYPE

Old Value: No Value (May want to consider Any Value if you have contacts changing from one contact

type to another. For example, Emergency Contact to Spouse.)

New Value: Spouse

Save and Close


8/12


Add the newly created Person Change to the Add Spouse Life Event

Save and Close.

Now continue to create the Life Events and add the Person Changes

Create Add Domestic Partner Life Event

The Life Event is setup the same as the Add Spouse Life Event except the Person Changes are reflective of the

Contact Type.

Name:Add Domestic Partner



Old Value: No Value

New Value: Domestic Partner

Save and Close.

Below are additional examples of Person Changes that you would associate with a new life event for each ContactType

Name:Add Child



Old Value: No Value

New Value: Child

Save and Create Another

Name:Add Adopted Child



Old Value: No Value

New Value:Adopted Child


9/12


Once all of the Life Events and Person Changes associated with the Life Events are created you are now ready to

create the Collapsing Rules.

Navigator: Benefits > Plan Configuration > Manage Benefits Life Events

Click on the Collapsing Rules Tab

Click on Create

Create the Collapsing Rule

Name: Add Dependent

Add the Life Events in the Selectedarea you wish to collapse into the Add Dependent.

Resulting Event Name: Add Dependent


10/12


Collapsing Life Events Example

On the Manage Person Screen add the contacts to trigger the Add Child and Add Spouse Life Events.

Navigator: Benefits > Enrollment > Benefits Enrollment > Person Life Events

Now you will see the two life events triggered. Add Spouse and Add Child were triggered. To collapse the life

events into the Add Dependent life event you press the Collapse Life Events button.


11/12


On the Person Life Events window you will see the life event Add Dependent Triggered. The Add Spouse and Add

Child life events are voided. This allows for only one Life Event to be needed throughout the rest of the Plan

Design.


12/12

Oracle Corporation, World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065, USA

Worldwide Inquiries

Phone: +1.650.506.7000

Fax: +1.650.506.7200

Copyright 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and thecontents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any otherwarranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability orfitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations areformed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by anymeans, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license andare trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo aretrademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.0115

White Paper TitleJanuary 2015Author: Todd Wall

C O N N E C T W I T H U S

blogs.oracle.com/oracle

facebook.com/oracle

twitter.com/oracle

oracle.com

Documents

Collapsing Life Events