Understanding EBenefits

8/9/2019 Understanding EBenefits

1/65

PeopleBooks eBenefits

Understanding eBenefits..............................................................................................2

eBenefits Transactions.................................................................................................3

eBenefits Integrations..................................................................................................3eBenefits Implementation............................................................................................3

Setting Up eBenefits........................................................................................................5

Using eBenefits Pages.................................................................................................6Setting Up Page Display Information..........................................................................6

Setting Up Uniform Resource ocators......................................................................!

Setting Up Te"t Bloc#s................................................................................................$%nrolling in eBenefits....................................................................................................&2

Understanding %nrollment Pages..............................................................................&2

Defining %'ent Rules.................................................................................................&$

Processing %'ents for ()BR* *dministration.........................................................2!Defining Rules for Benefits Billing...........................................................................2$

+US,- Setting Up ultiple/ (oncurrent )pen Seasons.............................................3&

Setting Up Uniform Resource ocators....................................................................30

Setting Up Te"t Bloc#s..............................................................................................36Setting Up Uniform Resource ocators....................................................................3$

Setting Up Te"t Bloc#s..............................................................................................0&(1anging arital Status............................................................................................05

*dding e Dependents...........................................................................................06

(1anging P1one um4ers.........................................................................................0!

Re'ieing and Updating Personal Information........................................................0!Sending Data to Benefit Pro'iders............................................................................0$

Sending IP** Data to Pro'iders.............................................................................5

+US,- Sending ,%B Data to t1e )P....................................................................52Running t1e %nrollment Reporting Snaps1ot Process...............................................53

Sending Data to Benefit Pro'iders............................................................................6Sending IP** Data to Pro'iders.............................................................................6&+US,- Sending ,%B Data to t1e )P....................................................................63

1 5/11/2015


2/65


Understanding eBenefits

This section discusses:

• eBenefits components.

• eBenefits roles and security.

eBenefits Components

eBenefits comprises self-service e! transactions that interface ith the People"oft #uman$esources system. %mployees use eBenefits to revie& add& and update their !enefitsinformation.

• The "elf "ervice& Benefits pa'e is the startin' place for employees to access their

eBenefits information.

• eBenefits %nrollment pa'es ena!le employees to communicate their !enefit choices to

the or'ani(ation.

• eBenefits #ealth pa'es ena!le employees to revie their health related !enefit

information !y navi'atin' from summary level pa'es to more detailed information.

• eBenefits "avin's pa'es ena!le employees to revie their savin's plan information !y

navi'atin' from summary level savin's plan pa'es to more detailed information.

• eBenefits )nsurances pa'es ena!le employees to revie the life insurance information !y

navi'atin' from summary level pa'es to more detailed information.

• eBenefits *ependents/Beneficiaries pa'es ena!le employees to revie information a!out

their dependents and !eneficiaries !y navi'atin' from summary level pa'es to moredetailed information.

• eBenefits +le,i!le "pendin' ccounts pa'es ena!le employees to revie information

a!out their health or medical spendin' account !y navi'atin' from summary level pa'esto more detailed information.

• eBenefits ife %vent pa'es are desi'ned for employees to enter information a!out a !irth

or adoption of a child or recent marria'e.

eBenefits Roles and Security

"elf-service transactions are tar'eted to specific roles& such as applicant& employee& faculty&mana'er& and optionee. These roles help determine:

• The transactions an employee can access.

• The information an employee can vie.

ser profiles determine default access to transactions. ou create user profiles on the aintain"ecurity pa'e in the ser Profile component. ou assi'n a role to each user profile.

Profiles are linked to permission lists. Permission lists identify the pa'es that users can access.To modify access to specific e! pa'es for each role& you modify the permission list.

ser profiles also control the data each employee can access.

See Also

2 5/11/2015


3/65


Enterprise PeopleTools PeopleBook: Security Administration

eBenefits Transactions

eBenefits transactions include:

• Benefits enrollment.

• #ealth plan information.

• )nsurance information.

• "avin's plan information.

• +le,i!le spendin' account information.

• *ependent and !eneficiary information.

• ife events mana'ement.

eBenefits Integrations

eBenefits inte'rates ith the folloin' People"oft applications:

eBenefits inte'ration flo ith other People"oft applications

eBenefits Implementation

People"oft "etup ana'er ena!les you to 'enerate a list of setup tasks for your or'ani(ation!ased on the features that you are implementin'. The setup tasks include the components thatyou must set up& listed in the order in hich you must enter data into the component ta!les& andlinks to the correspondin' PeopleBook documentation.

Other Sources of Information)n the plannin' phase of your implementation& take advanta'e of all People"oft sources ofinformation& includin' the installation 'uides& ta!le-loadin' seuences& data models& and !usinessprocess maps. complete list of these resources appears in the preface in the PeopleSoftEnterprise Application Fundamentals for HRMS 8. PeopleBook & ith information a!out here tofind the most current version of each.

See Also

People"oft %nterprise eBenefits Preface

3 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hebn/htm/hebn01.htm#i090f42a68010b487https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hebn/htm/hebn01.htm#i090f42a68010b487


4/65


PeopleSoft Setup Mana!er for PeopleSoft Enterprise HRMS and "ampus Solutions 8.PeopleBook

Entering eBenefits Text

ccess the eBenefits Te,t %ntry pa'e.

eBenefits Te,t %ntry pa'e

Text ID This is the uniue code assi'ned to the te,t )*.

Benefit Program This is the !enefit pro'ram that uses this te,t. )f Benefit Pro'ram is left !lank&the te,t ill apply to all !enefit pro'rams.

Plan Type This is the plan type that uses this te,t. )f Plan Type is left !lank& the te,t illapply to all plan types ithin the !enefit pro'ram selected

!entClassification

This is the event classification that uses this te,t. )f %vent 4lassification is left!lank& the te,t ill apply to all event classifications ithin the !enefit pro'ramand plan type selected.

Text ntry "ox This !o, is used to enter the te,t that appears on the eBenefits enrollmentpa'es.

Defining Text for Flexible Keys

"ome pa'e te,t is the same for all situations. "ome of the te,t varies from !enefit pro'ram to!enefit pro'ram. ther te,t varies from plan type to plan type. Te,t can vary !y plan type ithin!enefit pro'ram and can vary !y the type of event. To accommodate this& the system keys thete,t pieces !y !enefit pro'ram& plan type& and event class.

The system uses the folloin' rules hen matchin' te,t to a te,t !lock:

• The system looks for a match on !enefit pro'ram. )t uses only those ros that match the

!enefit pro'ram& or& lackin' any ros that match the !enefit pro'ram& uses the ros thathave a !lank !enefit pro'ram.

• 6ithin this set of ros& the system looks for a match on plan type. )t uses only those ros

that match the plan type& or& lackin' any ros that match the plan type& uses the rosthat have a !lank plan type.

• 6ithin this set of ros& the system looks for a match on event class. )t uses only the ro

that matches the event class& or& lackin' a match on event class& uses the ro that has a!lank event class.

Identifying Field Lists

This is a list of the fields on the folloin' ta!les: 63%B7T%8T& 63%B7T%8T7%++*T& and

63%B7T%8T7"9)*

• Te,t )* character field that uniuely identifies the te,t !lock.

• an'ua'e 4ode The lan'ua'e for this te,t !lock.

• *escription description of this te,t !lock.

• %ffective *ate The date this te,t !lock takes effect.

• Benefit Pro'ram distinct !enefit pro'ram or !lank.

; 5/11/2015

http://showpopup%28%27%3Cimg%20src%3D../img/image3.gif%20WIDTH=538%20HEIGHT=413%3E',escape('eBenefits%20Text%20Entry%20page'))


5/65


• Plan Type distinct plan type or !lank.

• %vent 4lass n event class or !lank.

• Te,t lon' field containin' the te,t !lock itself. The te,t may include up to five

su!stitution varia!les.

Setting Up Delivered Text and Effective Dating

This te,t is effective-dated& hich allos it to !e chan'ed from one plan year to the ne,t. Thedelivered te,t has an effective date of 1/1/1


6/65


• "et up uniform resource locators @$sA.

• "et up te,t !locks.

Using eBenefits Pages

The standard menu driven navi'ation path is the traditional People"oft access method users ofPeople"oft applications are familiar ith. The Benefits pa'e presents a simple user interfacedesi'n for end users. )t is accessed !y selectin' "elf-"ervice& Benefits.

The links that appear on the Benefits pa'e depend on hich colla!orative applications have !eenpurchased and hether the application has !een selected on the )nstallation ta!le.

eBenefits pa'e

Setting Up Page Display Information

6ith the e,ception of te,t ta!les used !y Benefits enrollment& all controls for ho and hat the

eBenefits pa'es display have !een added to e,istin' setup ta!les ithin the Base Benefits!usiness process in #uman $esources.

Before implementin' eBenefits you must define the or'ani(ations !enefit pro'rams& plans& andplan types.

The fields that control ho !enefit plan information displays on the eBenefits plan summary anddetail pa'es& and on the enrollment form are located on either the:

• Benefit Pro'ram - Plan Type and ption at the plan level.

• Benefit Plan Ta!le.

• %vent $ules.

See Also

Buildin' Base Benefit Pro'rams

"ettin' p Benefit Plans

4reatin' %vent $ules

Displaying Dependent and Beneficiary Information

The 4ollect *ep/Ben check !o, appears on !oth pa'es:

• Benefit Pro'ram - Plan Type and ption at the plan level.

•

%vent $ules.

Benefit Program # Plan Type and Option

6hen the 4ollect *ep/Ben check !o, is selected on the Benefit Pro'ram-Plan Type and ptionpa'e& the system collects the information pertainin' to dependents and !eneficiaries and displaysthat information on the eBenefit "ummary and the eBenefit *etail )nformation pa'es.

!ent Rules

C 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn04.htm#i090f42a680109001https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860http://showpopup%28%27%3Cimg%20src%3D../img/image2.gif%20WIDTH=787%20HEIGHT=475%3E',escape('eBenefits%20page'))https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn04.htm#i090f42a680109001https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860


7/65


6hen the 4ollect *ep/Ben check !o, is selected on the %vent $ules pa'e& the system displaysthe dependent and !eneficiary information on the eBenefits %nrollment pa'es.

+or health plans on the enrollment form& the system collects elections at the plan level. Theemployee selects hich dependents should !e covered under the plan !y selectin' a check !o,ne,t to each individuals name. The system derives the covera'e code !ased on the dependentsthat are selected.

6hen the check !o, is clear& the system hides the dependent or !eneficiary sections and doesnot collect dependent or !eneficiary elections. +or health plans on the enrollment form& thesystem collects elections at the covera'e code level hen the check !o, is clear.

The 4ollect *ep/Ben field orks ith the event rules )'nore *ep/Ben %dits field. )f the 4ollect*ep/Ben check !o, is selected& the )'nore *ep/Ben %dits check !o, should not !e selected.

See Also



Displaying Savings lan F!nd "llocationsThe 4ollect +unds llocations check !o, appears on three pa'es:

• Benefit Pro'ram Ta!le Pro'ram.

• Benefit Pro'ram Ta!le - Plan Type and ption at the plan level.

• %vent $ules.


6hen the 4ollect +unds llocations check !o, is selected on the Benefit Pro'ram-Plan Type andption pa'e& the system collects the information pertainin' to savin's plans and displays thatinformation on the eBenefit "avin's "ummary and the *etail )nformation pa'es.

!ent Rules

6hen the 4ollect +unds llocations check !o, is selected on the %vent $ules pa'e& the systemdisplays the dependent and !eneficiary information on the eBenefits %nrollment pa'es.

This field orks in concert ith the event rules )'nore )nvestment %dits check !o,. )f the 4ollect+unds llocations check !o, is selected& then the )'nore )nvestment %dits check !o, should !ecleared.

Setting Up Domestic #overage Information

n the enrollment form it may !e necessary to display information a!out to health plans on onepa'e. These can occur in situations here the employee is eli'i!le for a health plan that is linked

to a nonualified health plan.

The *omestic 4overa'e +or field determines hether plan types can !e com!ined on theenrollment form. This field displays on the Benefit Pro'ram - Plan Type and ption pa'e for plantypes 15& 1C& and 1D.

To set up domestic covera'e information:

1. ccess to the Benefit Pro'ram - Plan Type and ption pa'e.

2. *isplay the plan type level information for the nonualified health plan.

D 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860


8/65


3. )n the "elf-"ervice 4onfi'uration section& enter the num!er of the plan type that controlsthe cross-plan validation in the *omestic 4overa'e +or field.

+or e,ample& for plan type 15& hich is the nonualified medical plan& you ould enter 10 in the*omestic 4overa'e +or field. Thats !ecause plan type 10 controls the cross plan validation forplan type 15. +or plan type 10& the *omestic 4overa'e +or field is !lank.

S!ppressing lan Type Information

The "ho if no choice field is located on the Benefit Pro'ram Ta!le - Plan Type and ption pa'efor all plan types.

This check !o, controls hether a plan type is displays on the enrollment hen the employee hasno option to choose and cannot aive out of the option. 'ood e,ample is paid vacation.%mployees receive the !enefit& !ut you dont display it on the enrollment form.

)f the check !o, is selected& the system displays the plan type in the enrollment form summary.6hen the check !o, is cleared& the system ill not display the plan type.

Displaying #osts

The 4ost +re on %nrollment +orm field is located on the Benefit Pro'ram Ta!le - BenefitPro'ram pa'e at the pro'ram level. This check !o, controls hether the annual costs or the per-period costs @deductionsA are displayed on the enrollment form.

Displaying #redits

The "ho 4redits on %nrollment +orm field is located on the Benefit Pro'ram Ta!le - BenefitPro'ram pa'e at the pro'ram level. )f selected& this check !o, indicate for the system to displaytotal cost and credits on the pa'es.

Setting Up the Self$Service lan Descriptions Field

6hen settin' up !enefit plans for health& disa!ility& leave& or retirement !enefit plan types& you

can enter a description a!out the plan on the Benefit Plan Ta!le that displays on the enrollmentpa'es.

Setting Up Uniform Resource $ocators

The enrollment form and other !enefit transaction pa'es are desi'ned to displays links to:

• %mployee hand!ooks.

• Benefit provider e!sites.

• "ervice provider e!sites.

The specific uniform resource locator @$A address& description& and identifier are entered onthe $ ta!le. nce the address& description& and identifier are entered in the $ ta!le& thenonly the identifyin' code is entered in the Benefit Pro'ram ta!le& Eendor ta!le& and Benefit Planta!le.

The "P* $ )* on the Benefit Plan ta!le has priority over the 9eneral Policy $ )* on theEendor ta!le hen displayin' one or the other ne,t to plan provider.

The rules that determine hich $ appears ne,t to plan name on !enefit plan revie pa'es are:

> 5/11/2015


9/65


• )f a $ identifier is connected to the "P* $ )* on the Benefit Plan ta!le& this is the

link that appears on the !enefit plan revie pa'e.

• )f a $ identifier is connected to 9eneral Policy $ )* on the Eendor Policy ta!le and

no "P* $ )* is defined& this is the link that appears on the !enefit plan revie pa'e.

The uthori(ed Providers $ )* on the Eendor Policy ta!le is independent of the links listed

a!ove. )f an $ identifier is connected to the uthori(ed Providers $ )*& then that linkappears on the $evie pa'e ne,t to +ind a #ealth 4are Provider under the dditional )nformationsection. This link is for health plan types only& no link ill appear for the other plan types.

+or the 9eneral Policy $ )*s and uthori(ed Providers $ )* links to ork& a 'roup num!eris reuired on !oth the Eendor and Benefit Plan ta!les.

)t is recommended that you use a prefi, namin' convention& such as the one shon !elo:

• se SP# as a prefi, hen definin' "ummary Plan *escription $ )*s

@"$PF*47$7)*A: "P*7%TFPP.

• se $E% as a prefi, hen definin' the 9eneral Policy $ )* @P)47$7)*A:

9%F7%TF.

• se PR& as a prefi, hen definin' the uthori(ed Providers $ )*@E%F*$7$7)*A: P$E7%TF.

See Also

Enterprise PeopleTools PeopleBook: System and Ser'er Administration(Gsin' PeopleToolstilitiesH

Setting Up %andboo& Lin&s

These $s provide links to the enrollment hand!ook. There can !e a link to the entire hand!ookand a link to each of the plan-type sections.

Because the hand!ooks may vary !y !enefit pro'ram& the keys are !enefit pro'ram and plantype. The $ )dentifiers are on the !enefit pro'ram definition at !oth the pro'ram and plan-typelevels.

There can !e one $ for the entire hand!ook or separate $s for each plan type.

Setting Up 'eneral olicy Lin&s

These $ )dentifiers provide links to the provider home pa'es or to a company intranet site. Thefields are defined on the Eendor ta!le.

Setting Up "!thori(ed rovider Lin&s

These $ identifiers provide links to the providers P4P finder& and are only applica!le for health

plan types. The fields are defined on the Eendor ta!le.

Setting Up SD )S!mmary lan Description* Lin&s

These $ identifiers provide links to the plan "P*s. The fields are defined on the Benefit Planta!le.

Setting Up Text Bloc%s

< 5/11/2015


10/65


The te,t !locks are a collection of para'raphs& sentences& phrases& and ords that are usedhen displayin' the enrollment pa'es. ll ordin' on the pa'es ill come from this collection&ith the e,ception of error and arnin' messa'es& hich use essa'e 4atalo' ;001.

Deli!ered Text and ffecti!e Dating

This te,t is effective-dated& hich allos it to !e chan'ed from one plan year to the ne,t. The

delivered te,t has an effective date of 1/1/1


11/65





This is a list of the fields on the folloin' ta!les: 63%B7T%8T& 63%B7T%8T7%++*T& and63%B7T%8T7"9)*







•

%vent 4lass n event class or !lank.






12/65


The function does not have to supply the !enefit pro'ram or event class !ecause these valuescan !e derived from the event itself and do not chan'e.

Enrolling in eBenefits

This chapter provides an overvie of the enrollment process and the pa'es used in the process.

Understanding nrollment Pages

ou use eBenefits enrollment pa'es to:

•

4ommunicate to employees their !enefit choices.

• Fotify human resources employees !enefit elections.

The enrollment process !e'ins hen the system creates an enrollment event and notifies you ofthe event. ou can link to the Benefits %nrollment pa'e from the Benefits pa'e. +rom the Benefits%nrollment pa'e& you can then access the %nrollment "ummary pa'e& here you can revieeli'i!le !enefit elections& as ell as link to all plan-type pa'es here elections can !e made.

fter any plan-type election has !een made& the employee is returned to the %nrollment"ummary pa'e to continue the selection process& and the process is repeated for each availa!le!enefit. fter completin' all elections& employees su!mit their choices.

Understanding Benefit nrollments

)nformation a!out an individuals current covera'e comes from the !ase !enefit ta!les. Thesystem ill not use the event date hen pullin' current covera'e. )t uses the deduction !e'indate on the B"7P$T)47PF ros. This date has !een adIusted for 'race and aitin'periods. sin' this date 'ives a more accurate current election and more closely matches hatthe !ack'round process ill consider current.

)nformation a!out ne covera'e comes from the employees election or the default covera'e. )fthe B"7P$T)47PF ro has an election& either entered !y the employee or pre-entered !ythe system& the system uses that entry as the !asis for formattin' the ne covera'e. )f there is noentry& the system 'oes to the B"7P$T)47PTF ros to find the default value. )f there is noelection and no default& the system displays the phrase G%o "o'era!e.H

The plan-types @medical& vision& savin's& and so onA display in the top ro of the 4overa'e and%lection "ummary section. There is one multiline entry for every plan type in the event. The plan

types list in order !ased on the display plan seuence value in the !enefit pro'ram definition. Thename of the plan type comes from the lon' name in the Translate ta!le.

+or all plan-types& the system alays shos the plans availa!le and if there is the option ofaivin' covera'e. #oever& the setup ta!les can !e modified so that the system suppresses theplan types if the employees have no choice availa!le.

&ote' 4alculation amounts that display on the !enefit enrollment pa'es are only estimatedamounts.

12 5/11/2015


13/65


See Also

"uppressin' Plan Type )nformation

ages Used to Enroll in Benefits

Page Name Object Name Navigation Usage

BenefitsEnroll&ent

W3EB_E(R_SE)E*T Self Ser!ice, Benefits

*lic" t#e BenefitsEnroll&ent lin" on t#eBenefits pa%e'

T#is pa%e pro!ides enroll&entinfor&ation to t#e e&ployee anddisplays infor&ation a$out anenroll&ent e!ent' T#e enroll&entprocess is initiated +#en eli%i$ility ande!ent rules #a!e $een processed toproduce a list of !alid $enefit c#oices'

pen BenefitsE!ent

W3EB_E(R_-(. *lic" t#e -nfor&ation$utton on t#e BenefitsEnroll&ent pa%e'

T#is pa%e pro!ides enroll&entinfor&ation to t#e e&ployee' /fter yourinitial enroll&ent, t#e only ti&e you

&ay c#an%e your $enefit c#oices isdurin% open enroll&ent or a 0ualifiedfa&ily status c#an%e' T#is pa%epro!ides you +it# additionalinfor&ation a$out your enroll&ent'

BenefitsEnroll&entSu&&ary

W3EB_E(R_SUMM/R1 *lic" t#e Select $utton ont#e Benefits Enroll&entpa%e'

Use t#e Benefits E!ent Su&&ary pa%eto re!ie+ $enefit plan elections' T#eEnroll&ent Su&&ary displays +#ic#$enefit options are open for edits' /ll ofyour $enefit c#an%es are effecti!e asof t#e date of t#e $enefit c#an%e e!ent'1our enroll&ent is not co&plete until

you su$&it your c#oices to t#e Benefits2epart&ent'

BenefitsEnroll&ent Medical

W3EB_E(R_X_E)E*T *lic" t#e 4Medical5 Edit$utton on t#e BenefitEnroll&ent Su&&arypa%e'

E&ployees use t#is pa%e to re!ie+ orelect #ealt# 4&edical5 plantype$enefits'

BenefitsEnroll&ent Medical4su&&ary5

W3EB_E(R_X_SMR1 *lic" t#e!er!ie+ of /llPlans $utton on t#eBenefits Enroll&ent Medical pa%e'

Use t#e condensed Su&&ary pa%e to!ie+ all plans, co!era%e le!els, andcosts condensed into a sin%le %rid'

BenefitsEnroll&ent )ife

BenefitsEnroll&ent Supple&ental)ife

BenefitsEnroll&ent

W3EB_E(R_6X_E)E*T • *lic" t#e 4)ife5

Edit $utton ont#e BenefitEnroll&entSu&&ary pa%e'

• *lic" t#e

4Supple&ental)ife5 Edit $utton

E&ployees use t#e )ife -nsuranceEnroll&ent pa%e to enroll in lifeinsurance $enefits' E&ployees use t#eSupple&ental )ife -nsurance PlanEnroll&ent pa%e to enroll insupple&ental life insurance $enefits'T#e Benefits Enroll&ent 2ependent)ife pa%e is used to enroll dependents

13 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hebn/htm/hebn03.htm#i090f42a68010b4a3https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hebn/htm/hebn03.htm#i090f42a68010b4a3


14/65



2ependent )ife on t#e BenefitEnroll&entSu&&ary pa%e'

•

*lic"42ependent )ife5Edit$utton ont#e BenefitEnroll&entSu&&ary pa%e'

in life insurance plans'

BenefitsEnroll&ent )on% Ter&2isa$ility )ife

BenefitsEnroll&ent

Retire&ent Plan

W3EB_E(R_378X_E)*T • *lic" t#e )on%

Ter& 2isa$ility4Edit5 $utton ont#e BenefitEnroll&entSu&&ary pa%e'

• *lic" t#e Edit$utton on anyretire&ent line oft#e BenefitEnroll&entSu&&ary pa%e'

E&ployees use t#e )on% Ter&2isa$ility Plan Enroll&ent pa%e toenroll in disa$ility $enefits' E&ployeesuse t#e Retire&ent Plan Enroll&entpa%e to enroll in retire&ent plan$enefits'

BenefitsEnroll&ent Sa!in%s Plans

W3EB_E(R_9X *lic" t#e 49:4"55 Edit$utton on t#e BenefitEnroll&ent Su&&arypa%e'

E&ployees use t#e Sa!in%s PlanEnroll&ent pa%e to enroll in sa!in%splan $enefits'

BenefitsEnroll&ent )ea!e Plans

W3EB_E(R_378X_E)E*T *lic" t#e 4Sic"5 Edit $uttonon t#e Benefit Enroll&entSu&&ary pa%e'

E&ployees use t#e )ea!e PlanEnroll&ent pa%e to enroll in lea!e plan$enefits'

.lex Spendin%/ccounts

W3EB_E(R_;X_E)E*T *lic" t#e Edit $utton onany .S/ line of t#e BenefitEnroll&ent Su&&arypa%e'

E&ployees use t#e .S/ Enroll&entpa%e to enroll in .S/ plan $enefits'

.lex Spendin%Healt# U'S'Wor"s#eet

W3EB_E(R_;X_W


15/65



Buy@Sell Su&&ary pa%e'

Su$&it Benefit

*#oices

W3EB_E(R_SUBM-T *lic" t#e Su$&it $utton on

of t#e Benefit Enroll&entSu&&ary pa%e'

E&ployees use t#e Su$&it Benefit

*#oices pa%e to su$&it t#eir $enefitc#oices to t#e syste&'

Su$&it*onfir&ation

W3EB_E(R_*(.-RM *lic" t#e Su$&it $utton onSu$&it Benefit *#oicespa%e'

E&ployees use t#e Su$&it*onfir&ation pa%e to confir& t#at t#eir$enefit c#oices #a!e $een su$&itted tot#e syste&'

People"oft %nterprise eBenefits >.< PeopleBook 4opyri'ht ? 200; People"oft& )nc. ll ri'hts reserved.

Understanding Event Triggers

The system tri''er events throu'h employee data chan'es hen:

• n administrator opens an employee data pa'e& such as the Personal *ata pa'e& and

enters a chan'e to employee information.

• The employee enters a marital status or !irth or adoption chan'e throu'h eBenefits.

To increase the efficiency of the %vent aintenance process& the system tri''ers JIo!J and Jnon- Io!J events from a variety of different ta!les. Ko! events are relevant to employment& such ashires& transfers& and terminations. Fon-Io! events cause chan'es in your employees personal ordemo'raphic information that affect !enefits eli'i!ility or elections.

This ta!le descri!es the delivered non-Io! events tri''ers:

Non-JobEvent

Cause Processing Result

2ate of$irt#

c#an%e

Update to t#e noneffecti!edated $irt#date field on t#e Personal 2ataAEli%i$ility@-dentity pa%e'

enerates a +or"flo+ noticeto t#e $enefits ad&inistrator'

Postal codec#an%e

Update to t#e effecti!edated Postal *ode field of t#e #o&e address ont#e Personal 2ataA /ddress History pa%e' /lso tri%%ered if t#e effecti!edate of t#e current #o&e address is c#an%ed'

enerates a B/S_/*T->-T1tri%%er'

Ser!icedate

Update to t#e noneffecti!edated Ser!ice 2ate field on t#e Co$ 2ataAE&ploy&ent 2ata pa%e'

enerates a +or"flo+ noticeto t#e $enefits ad&inistrator'

15 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/legal_hr89pbr0.htmhttps://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/legal_hr89pbr0.htm


16/65


Non-JobEvent

Cause Processing Result

c#an%e

State codec#an%e

Update to t#e effecti!edated State field of t#e #o&e address on t#ePersonal 2ataA /ddress History pa%e' /lso tri%%ered if t#e effecti!e dateof t#e current #o&e address is c#an%ed'

enerates a B/S_/*T->-T1tri%%er'

&ote' 4han'es to !irth and service dates 'enerate a orkflo notice& !ecause they occur tofields that are not effective-dated under a correction action& and as such must !e handledcarefully. The appropriate action& if applica!le& may !e to reprocess an e,istin' event.

%vent tri''ers !ased on the Ko! ta!le include chan'es to these fields in the Ko! *ata component:

• ction/ction $eason

• Benefits "tatus

• Benefits "ystem +la'

• Benefit $ecord Fum!er

• Business nit/"et)*

• 4ompany

• %mployee 4lass

• %mployee Type

• %li'i!ility 4onfi' +ield 1 - <

• %mployee "tatus

• +" "tatus

• +T%

• +ull/Part-time "tatus

• 9rade

• ocation

• fficer 4ode

• Pay'roup

• $e'ular/Temporary

• $e'ulatory $e'ion

• "alary dministration Plan

• "tandard #ours

• nion 4ode

1C 5/11/2015


17/65


ages Used to Define Trigger Events


Ben/d&in /cti!ity4$enefits

ad&inistrationacti!ity5

B/S_/*T->-T1 Benefits, Mana%e/uto&ated Enroll&ent,

E!ents, Re!ie+ Bas/cti!ity, Ben/d&in/cti!ity

-nsert e!ents into t#e B/S /cti!ity ta$le'1ou &anually insert e!ents to $e

processed accordin% to e!ent rules t#at&ap to t#e B/S action t#at you enter

+#en you run t#e Benefits /d&inistrationprocess' 1ou can also delete un+anted,$ut auto&atically tri%%ered, e!ents'

Passi!e E!ent2efinition

B/S_P/SS->E_E>E(T Set Up HRMS, ProductRelated, /uto&atedBenefits, Eli%i$ility andE!ent Rules, Passi!eE!ent 2efinition, Passi!eE!ent 2efinition

2efine passi!e e!ents t#at are not initiated$y data entry'

Inserting Events into the B"S "ctivity Table

ccess the Bendmin ctivity pa'e.

Bendmin ctivity pa'e

ou can insert into the B" ctivity ta!le only event classes that have the anual %vent lloedcheck !o, selected in the %vent 4lass ta!le.

s delivered& you can insert to event classes manually: +amily "tatus 4han'e andiscellaneous "tatus 4han'e. ou can also revie and delete any type of unprocessed eventith this pa'e.

&ote' The B" ctivity ta!le displays unprocessed events only. s soon as Benefits dministration successfully processes an event& the system deletes it from the B" ctivity ta!le.

Action Source )dentifies hether the event is due to a chan'e in Io! data& personal data& ormultiple Io! fla's& or is a passive event. Possi!le action sources are:

• Manual: anual event.

• PasBirt)#t: Passive event - !irthdate.

• PasS'c#t: Passive event - service date.

• *o+")!: Ko! data chan'e.

• M*")!: ultiple Io! indicator chan'e.

• Address")!: ddress @state and postalA chan'e.

All (o"s "elect if the manual event should tri''er !enefits processin' for all possi!le Io!s and not Iust the specific Io! @employment record num!erA entered for theevent. +or e,ample& a manually entered +"4 could impact !enefits for all Io!s.

&ote' This option is availa!le if the ultiple Ko!s feature is ena!led.

!ent Date *isplays the event date.

)f a Io!& address& or multiple Io! chan'e tri''ers the activity& the event date is

1D 5/11/2015

http://showpopup%28%27%3Cimg%20src%3D../img/image7.gif%20WIDTH=916%20HEIGHT=500%3E',escape('BenAdmin%20Activity%20page'))


18/65


the effective date of the chan'e.

)f a passive event tri''ers the activity& the event date is the date on hich thelimit represented !y the event @a limit related to a'e or years of service& fore,ampleA as reached.

The date for a manually entered event appears !y default hen the activityrecord for the event as inserted into the ta!le throu'h the Bendmin ctivitypa'e. ou can chan'e the event data if reuired.

!ent ffse)@event effectiveseuenceA

)f there is more than one manual event for an employee for the same effectivedate& enter uniue seuence num!ers for each event.

BAS Action )dentifies the Benefits dministration action associated ith this event asdefined in the ction $eason ta!le.

%vents tri''ered !y Io!& address& multiple Io! indicators& and passive eventsare assi'ned codes from the ction $eason ta!le. anual events are 'iven acode that is selected !y the user enterin' the manual event record.

COBRA Action )dentifies the 4B$ action code associated ith this event as defined in the ction $eason ta!le @not entered for a manual eventA.

Defining assive Events

ccess the Passive %vent *efinition pa'e.

Passive %vent *efinition pa'e

&ote' @"+A Passive event processin' functionality is not applica!le to most .". federal'overnment a'encies.

Passi!e !ent Type "elect a passive event type. *elivered event types includeemployee !irthdate and events !ased on an employeeLs service

date.!ent Classification "elect an event classification. f the delivered event classes& ,E

and Snaps)ot are not availa!le.

!ent $imit # *onths and!ent $imit # Days

)ndicate ho lon' after the !irthday or service date the event illtake place.

xample of Passi!e !ent Definition

ou mi'ht set up a passive event to determine hich employees are eli'i!le for certain !enefitsonce theyLve orked for your or'ani(ation for a year. To do this& you define a passive event iththe service date event type and an event limit - months value of -. The event classification forthis e,ample could !e "4& or it could !e a ne event classification created specifically tomana'e this passive event.

fter you set up the passive event& the system calculates the difference !eteen your employeesLservice dates and the process date& and it tri''ers the event for any employees ith a differenceof telve months ithin the date ran'e that you specify on the Benefits dministration processrun control pa'e. The system processes the passive event as an "4 event.

&ote' )nternally& hen the Benefits dministration process runs& it processes passive events !yinsertin' a B" ctivity record for each individual ho meets the passive event criteria. +rom thispoint& the activity record is processed like any other event& hich means that you can e,tend the

1> 5/11/2015

http://showpopup%28%27%3Cimg%20src%3D../img/image8.gif%20WIDTH=528%20HEIGHT=354%3E',escape('Passive%20Event%20Definition%20page'))


19/65


passive event concept !eyond that hich is delivered. *o this !y creatin' your on modifiedprocesses that insert the reuired B" ctivity ros.

Defining !ent Rules

To define event rules& use the Benefits dministration %vent $ules @B"7%E%FT7$%" Acomponent.

This section provides an overvie of event-rule definition and discusses ho to:

• "pecify !asic rules for event classes.

• "et evidence of insura!ility @%)A and level rules.

• *efine start and end dates for covera'e& deductions& and fle, credits.

Understanding Event$+!le Definition

The %vent $ules ta!le components define ho events are mana'ed for !enefit pro'rams and

!enefit plan types. ou link an event rule )* to each !enefit pro'ram and !enefit plan type thatyour or'ani(ation offers throu'h the Benefit/*eduction Pro'ram ta!le.

)n 'eneral& you only link event rules to !enefit pro'rams to determine hen the !enefit pro'ramparticipation takes effect and hen fle,i!le credits !e'in and end.

ou set up more complicated event rules at the plan type level to help the system determine hoto process the various classes of events for each plan type that you offer.

&ote' ou set up event rules at the pro'ram level !y settin' up rules for Plan Type 01 @thepro'ram levelA.

ages Used to Define Event +!les

PageName

Object Name Navigation Usage

E!entRules

B/S_E>E(T_RU)ES Set Up HRMS, Product Related, /uto&atedBenefits, Eli%i$ility and E!ent Rules, E!entRules Ta$le, E!ent Rules

Specify $asic e!ent rules fore!ent classes'

E- and)e!elRules

B/S_E>E(T_RU)ES/ Set Up HRMS, Product Related, /uto&atedBenefits, Eli%i$ility and E!ent Rules, E!entRules Ta$le, E- and )e!el Rules

Set E- and le!el rules fore!ent classes'

2ate Rules B/S_E>E(T_RU)ES6 Set Up HRMS, Product Related, /uto&ated

Benefits, Eli%i$ility and E!ent Rules, E!entRules Ta$le, 2ate Rules

2efine start and end dates

for co!era%e, deductions,and flex credits'

B/S E!entRules Ta$le

RU(*T)_B/S8:3B Set Up HRMS, Product Related, /uto&atedBenefits, Reports, E!ent Rules, B/S E!entRules Ta$le

Print e!ent rule definitions'

1< 5/11/2015


20/65


Specifying Basic +!les for Event #lasses

ccess the %vent $ules pa'e.

%vent $ules pa'e

!ent Class

se this 'roup !o, to define rule information for an event class.

!ent Classification "elect an event classification.

ou can have more than one event classification for an event rule tocover all e,pected contin'encies and usa'es.

&ote' )f the %vent 4lassification field is left !lank& that ro !ecomes aGildcardH and is used to mana'e any event processed !y this rule forhich no specific event classification !ehavior has !een defined. Thisildcard is difficult to trou!leshoot !ecause the system provides noindication as to hen it as invoked& and thus can lead to unanticipatedresults. se the ildcard feature cautiously.

Ignore Plan "elect to make chan'es to plan information ithout restrictions as toho often or hen the chan'es are made. 6hen selected& the plantypes linked to this event rules )* and event classification com!inationare unaffected !y Benefits dministration processin'. ou can use thisoption to arran'e for specific plan types to have automatic eventprocessin' only for maIor event classifications such as hires&terminations& and open enrollment& hile leavin' them unaffected !ylesser event classifications.

6hen you select )'nore Plan& the system selects and locks )'nore*ep/Ben %dits and )'nore )nvestment %dits. The system also sets "elect

lloed to %one( and all participate and aive level values to .

)'nore Plan does not interfere ith eli'i!ility rule processin'. )t does notena!le employees to stay in or enroll in plans for hich they are nolon'er eli'i!le.

)f participant plan eli'i!ility does not chan'e& the system 'ivesemployees their current covera'e. But if participant plan eli'i!ility doeschan'eMthat is& if employees lose eli'i!ility for their current planMyouneed to set a default method of Assi!n "urrent "o'era!e Else ,ption(

Assi!n "urrent "o'era!e Else /o0 ,ption( or Assi!n "urrent "o'era!eElse %one.

6ith )'nore Plan selected& the system i'nores:

• 4han'e level ma,imums and proof reuired for chan'in' levels.

• Plan-specific edits @life insurance settin's& individual +"

ma,imums& vacation limits& and so onA.• %dits on dependent or !eneficiary information.

• %dits on investment elections.

The system continues to:

• +la' errors 'enerated due to invalid setup& such as missin'

ta!le entries or pay calendars.

• $euire that the option code entered throu'h data entry !e a

valid selection from the eli'i!le plans on the pro'ram.

20 5/11/2015

http://showpopup%28%27%3Cimg%20src%3D../img/image9.gif%20WIDTH=695%20HEIGHT=464%3E',escape('Event%20Rules%20page'))


21/65


22/65


ne enrollment elections. )f the participant has lost eli'i!ility for one ormore current elections& he or she can make a ne election.

Default *ethod )ndicates hat happens hen an employee does not select an electionfor a particular plan type. Ealues are:

• Assi!n "ur "o'r! Else ,ption @assi'n current covera'e else

optionA: "elect to assi'n and continue the participants currentcovera'e.

)f participants do not have current covera'e& or have losteli'i!ility to current covera'e& they are assi'ned to the defaultfor the specific plan type& as defined in the Benefit/*eductionPro'ram ta!le. The participant must !e eli'i!le for the currentelection for it to !e used as the default.

• Assi!n "ur "o'r! Else %one @assi'n current covera'e else

noneA: )f the employee loses eli'i!ility for the current plan&another plan is not set up to replace the old one.

• Assi!n "ur "o'r! Else /o0 ,pt @assi'n current covera'e else

lo optionA: "elect to assi'n and continue the participantscurrent covera'e.

)f there is no current covera'e& or if the participant has losteli'i!ility to current covera'e& the system assi'ns the loest-level option availa!le& as defined in the Benefit/*eductionPro'ram ta!le. Fot recommended for "avin's& +"& andEacation Buy/"ell plan types.

• #efault to /o0est Eli! ,ption @default to loest eli'i!le optionA:

"elect to assi'n the loest-level option for hich the employeeis eli'i!le.

Fot recommended for "avin's& +"& and Eacation Buy/"ell plantypes.

• #efault to ,ption and "o'era!e: "elect to assi'n the option

marked for default on the Benefit Pro'ram *efinition pa'e.

The participant must !e eli'i!le for the option for it to !e used asthe default. Fot recommended for "avin's& +"& and EacationBuy/"ell plan types.

• #efault ,ption for E1c "redit: @default option for e,cess creditA

pplica!le only to +" plan types.

)f the employee has indicated that e,cess credits should !edirected to an +" enrollment& this rule assi'ns the optionmarked for default on the Benefit Pro'ram *efinition pa'e andsets the annual pled'e to the amount of the e,cess credits. Theparticipant must !e eli'i!le for the option for it to !e used as thedefault& and e,cess credits must e,ist.

&ote' *urin' enrollment& the system does not create a (ero-dollar annual pled'e enrollment hen e,cess credits do note,ist& and any current +" enrollment is terminated if notreelected !y the employee.

• Terminate "o'era!e: )nserts a termination entry for the plan

type covered !y this event rule.

4ommonly used for +" and Eacation Buy/"ell plan types& asemployees are usually reuired to reenroll in them each year orlose covera'e.

22 5/11/2015


23/65


Allo.a"le ,SA PledgeChanges @alloa!lefle,i!le spendin' accountpled'e chan'esA

"elect a value that indicates ho a rule should process +" pled'echan'es. lloa!le +" pled'e chan'es are !ased on the eventclassification and the !usiness process& and the employee is permittedto increase or decrease the +" pled'e. +or e,ample& if the eventclassification is Birth& employees can increase& !ut not decrease their+" pled'e. This field only applies to C, plan types and should !e set to

F/ for all other plan types."elect 2ncrease to permit increased pled'es to an +" and #ecrease topermit decreases to pled'es.

"elect %A @not applica!leA if +" pled'e chan'es do not affect this rule.)f employees attempt to make chan'es that violate the restrictions of theevent rule& they receive an error messa'e.

"ee %nterin' Benefit %lections.

lecta"le Options

se this 'roup !o, to define !enefit plans to hich employees can make chan'es& and to set upcovera'e codes.

SelectAllo.ed

Provides a means for you to indicate hich plan or plans that an employee canselect from amon' all eli'i!le types of plans. Ealues are:

• All Plans: "elect to ena!le employees to select from any option ithin the

list of eli'i!le options for the event.

• "urrent Plan: "elect to indicate that employees can make chan'es to only

the current plan.

• "urrent Plan 3 4ai'e: "elect to ena!le employees to only chan'e covera'e

levels @eli'i!le optionsA& includin' electin' 4ai'e ithin their currentlyenrolled !enefit plan. #oever& if the employees current election is a aiveof the plan type& she can elect any eli'i!le option ithin any !enefit plan.

+or e,ample& if an employee has sin'le covera'e and 'ets married and the

ne spouse has health covera'e throu'h her employer. They decide thatcoverin' !oth individuals under the spouses !enefit plan is a !etter choice.)n this case& the employee is alloed to aive his current covera'e !ecausethe spouse is addin' the employee to the spouseLs covera'e.

"uppose that the e,ample employee is married& and at the last openenrollment she aived health covera'e !ecause she as covered under thespouses plan. Fo suppose that the spouse terminates employment&there!y losin' eli'i!ility for the plan that covered !oth the spouse and theemployee. )n this situation @hich is also considered an +"4 event !y mostcustomersA& the employee is alloed to enroll in any eli'i!le option in theplan type.

• %one: "elect to disallo employees from makin' any chan'es to their

elected option @unless eli'i!ility for their current option or plan has !een lost&

in hich case the system automatically overrides this settin' and allos AllPlansA.

Co!erageCodeControl

"elect to ena!le employees to only chan'e covera'e levels @eli'i!le optionsA ithintheir currently enrolled !enefit plan @applies only to the 1, series of plansA. 4overa'ecode control rules specify the criteria you use to select a valid covera'e code forpresentation to the employee for election. The rule specifies one set of criteria that isused hen current covera'e is in effect& and another set of criteria to !e used henthere is no current covera'e.

)f an employee loses eli'i!ility for his current !enefit plan& the system automatically

23 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna12.htm#i090f42a6801068f9https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna12.htm#i090f42a6801068f9https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna12.htm#i090f42a6801068f9


24/65


overrides this settin' and allos all options.

6hen you select the 4ovr' 4ode 4ontrol check !o,& the 4overa'e 4ode 4ontrol'roup !o, appears here you can define covera'e types and indicators.

"ee "ettin' p 4overa'e 4odes.

Co!erage Code Control

se this 'roup !o, to define parameters for covera'e codes that help control the 'ain and loss ofeli'i!ility and ho can !e added to or dropped from covera'e. The codes you define are for theevent class.

To increase the num!er of covered person types& the event must !e an increase in the num!er ofeli'i!le dependents such as marria'e& !irth& adoption& or placement for adoption. 4overa'edecrease is only alloed if there is a divorce& annulment& le'al separation& death of spouse ordependent& or loss of dependent eli'i!ility.

Co!eredPersonType

"elect a person cate'ory that determines ho the person is to !e processed !y thesystem. )n usin' covered person types& each relationship type that is eli'i!le to enrollin Benefits must !e mapped to a covered person type. 'iven relationship code can

map to (ero or one covera'e person type code& hile a particular covera'e persontype code can map to one or more relationship codes.

These values are defined in the Benefits *ependent "tatus ta!le. This ta!le make ispossi!le to !e consistent across all types of covered persons& hile alloin' for netypes of covered persons to !e added in the future. The ta!le is used as a child ta!leof the 4overa'e 4odes ta!le.

• ")ild

• #om Partner @domestic partnerA

• Employee

• %5 #ependent @nonualifyin' dependentA

• ,t) 5 #ependent @other ualifyin' dependentA

• Spouse

Same "elect to keep the same num!er of covered persons in the plan. ou can enrollmore& less& or the same of a particular covered person type. n e,ample of usin' the"ame& ore& and ess check !o,es to define covered person type mi'ht !e in thecase of a divorce event class. )n a divorce& it is possi!le to have more& the same& orless children enrolled dependin' on the situation. "o& you ould select all threecheck !o,es for the ")ild person type option.

4ontinuin' ith the divorce event class e,ample& you ould add a ro& and selectthe Spouse person type in the 4overa'e Person Type field and select the ess check!o,& since the spouse ill no lon'er !e covered. +inally& you ould select the

Employee person type and select the "ame covera'e. The covera'e code ruleallos for all variations of a particular event class so it ould !e possi!le to allomore and less in the same event classification. )n addition the same& more or lessapplies if the employee is already enrolled in a plan& the 4overa'e indicator on theri'ht applies if the employee is nely enrolled in the plan.

*ore "elect if the event class allos more covered persons to !e added to the plan.

$ess "elect if the event class allos less covered persons to !e alloed in the plan.

Co!erage )ndicate the status of the covered person type enrollment if there asnLt covera'e

2; 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecfhttps://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecfhttps://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecf


25/65


Indicator previously in effect.

• Allo0ed: "elect to indicate that enrollment for the covered person type is

alloed.

• %ot Allo0ed: "elect to indicate that enrollment for the covered person type is

not alloed.

• Re6uired: "elect to indicate that enrollment for the covered person type isreuired.

"ee "ettin' p 4overa'e 4odes.

Self#Ser!ice Configuration

se this 'roup !o, to define rules for the information that appears on the eBenefits applicationpa'es. Ealues are:

Collect Dep+Ben @collect dependent or!eneficiary covera'eA

"elect to display dependent or !eneficiary 'rids and collect dependent or!eneficiary elections. +or 1, #ealth plans on the enrollment form& thesystem collects elections at the plan level. The system then derives thecovera'e code !ased on the dependents covered. 6hen cleared& the

system collects elections at the covera'e code level for 1, plans on theenrollment form.

Allo. Dep+BenAdditions @allodependent or!eneficiary additionsA

"elect to indicate than an employee can add ne dependents throu'h theeBenefits enrollment process.

Collect ,undAllocations

"elect to display investments and collect fund allocations for savin'splans.

Applying Defaults

The system applies defaults durin' the Benefits dministration process as it validates& loads& or

finali(es participant elections. 6hen you post a participants election information for openenrollment and other events& you mi'ht not have elections for all plan types. Plan type defaultsare used as su!stitutes for a participants election hen you finali(e the event.

)f you select Finali7e for the participant& election defaults are validated and loaded for the plantypes ithout elections and the plan types that are still in error.

Participants ho have reached a process status of at least Prepared are finali(ed unless Benefits dministration encounters maIor errors in the final preparation. The finali(in' of the processould !e prevented& for e,ample& if Benefits dministration encounters pay calendar issues hileattemptin' to determine deduction end dates.

Setting Evidence of Ins!rability )E,I* and Level +!les

ccess the %) and evel $ules pa'e.

%) and evel $ules pa'e

se the %vent 4lassification field to select the event class for hich you ant to define rules.

If currently nrolled/ or not participating

25 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecfhttps://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecfhttp://showpopup%28%27%3Cimg%20src%3D../img/image10.gif%20WIDTH=638%20HEIGHT=392%3E',escape('EOI%20and%20Level%20Rules%20page'))https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn03.htm#i090f42a680108ecf


26/65


se this 'roup !o, to define rules that apply to an employees participation in a !enefit optionfolloin' an event hen the employee is currently participatin' in a plan or is ne to a plan.These rules commonly apply to life& accidental death and dismem!erment& and disa!ility plantypes& and are used to indicate the types of chan'es that employees can make.

*ax &um"er of Change $e!els @ma,imum num!er of chan'e levelsA

)ndicates ho many levels a participant can chan'e or Iump.

$e!els of Change .+o Proof @levels ofchan'e ithout proofA

)ndicates ho many levels a participant can chan'eithout proof of 'ood health or insura!ility.

Proof Re)uired at Plan $e!el )ndicates the initial level at hich proof of 'ood healthor insura!ility is reuired.

Amt' Proof Re)uired @amount at hichproof is reuiredA

%nter the amount of covera'e a!ove hich proof of'ood health or insura!ility is reuired.

If currently 0ai!ed

se this 'roup !o, to define rules that apply to an employees participation in a !enefit optionfolloin' an event if the employee is currently opted out of the pro'ram.

*ax &um"er of Change $e!els @ma,imum num!er of chan'e levelsA

)ndicates ho many levels a participant can chan'e.

Proof Re)uired at Plan $e!el )ndicates the initial level at hich proof of 'ood healthor insura!ility is reuired.

Amt' Proof Re)uired @amount at hichproof is reuiredA

%nter the amount of covera'e a!ove hich proof of'ood health or insura!ility is reuired.

Defining Start and End Dates for #overage- Ded!ctions- and Flex

#redits

ccess the *ate $ules pa'e.

*ate $ules pa'e

se this pa'e to set up date information for !enefits.

Co!erage Begins

)ndicate hen covera'e !e'ins folloin' an event.

Ealues are:

• Mont)Be!in After E'ent #t @month !e'in after event dateA: 4overa'e !e'ins on the first

day of the folloin' month.

)f the event date is eual to the first of the month& covera'e still !e'ins on the first day ofthe folloin' month.

• Mont)Be!in ,n9Aft E'ent #t @month !e'in on or after event dateA: )f the event date

euals the first of the month& covera'e !e'ins on the event dateN otherise& covera'e!e'ins on the first day of the folloin' month.

• ,n Pay Pd Be!in after E'ent #t @on pay period !e'in after event dateA: 4overa'e !e'ins

on the first day of the pay period folloin' the event date.

2C 5/11/2015

http://showpopup%28%27%3Cimg%20src%3D../img/image11.gif%20WIDTH=631%20HEIGHT=359%3E',escape('Date%20Rules%20page'))


27/65


)f the event date euals the first day of the pay period& covera'e !e'ins on the eventdate.

• ,n t)e E'ent #ate: 4overa'e !e'ins on the day of the event.

0aitingPeriod

To calculate the date that covera'e !e'ins hen there is a aitin' period& the system:

1. Be'ins ith the event date.

2. dds the num!er of months.

3. dds the num!er of days.

;. pplies the 4overa'e Be'ins rule to the resultin' date.

Usexist1

"elect to ena!le the system to search for any aitin' periods on prior events. )fselected& and a aitin' period is found& the system honors the prior eventLs aitin'period if the prior eventLs covera'e !e'ins date is later than the covera'e !e'ins datenormally associated ith the current event.

+or e,ample& ne hires have a three-month period !efore their !enefits !ecomeeffective. nder this rule& an employee hired on Fovem!er 1 has a health !enefitelection ith a covera'e !e'in date and deduction !e'in date of +e!ruary 1.

Fo& letLs say that youLve scheduled an open enrollment for Kanuary 1. *urin' that

time& the employee as processed for an open enrollment event. )f the event rules forthe open enrollment specify that the covera'e !e'in date euals the event date&Kanuary 1& the employee ould have a health !enefit election posted ith a covera'eand deduction !e'in date that is earlier than the health !enefit covera'e and deduction!e'in date that the employee ori'inally received hen hired.

"electin' se %,istO for the % event rule ould prevent this from happenin' as thesystem ould preserve the aitin' period from the employeeLs previous #)$ event.

Days and*onths

%nter the num!er of days and months the system should use as a aitin' period to!e'in covera'e.

Co!erage nds

"elect hen covera'e ends. The covera'e end date is used only hen an e,istin' election ithin

a plan type is truly terminatin' and not simply !ein' superseded !y another election @!enefitoptionA. )n this case& the system inserts a ne election ro ith 4overa'e %lection set toTerminated .

)f you select either ,n Mont) End After E'ent #ate or ,n Pay Pd End After E'ent #ate rules( the covera'e !e'in date of this ne ro is one day after the calculated covera'e end date for thecurrent election. This occurs !ecause this is the first date for hich covera'e no lon'er e,ists.

2race Period Days and 2race Period*onths

To esta!lish a 'race period !efore covera'e is terminated& enter theappropriate num!er of days or months that the system uses to calculate theresultin' end date in a manner similar to 6aitin' Period.

Deduction 3 ,lex Credits Begin

se this 'roup !o, to indicate hen deductions and fle,i!le !enefit credits should !e taken.Ealues are:

• -st Full PayPd After "o'! B!#t @first full pay period after covera'e !e'in dateA: 4redits

and deductions !e'in on the first day of the pay period folloin' the covera'e !e'in date&re'ardless of hen the covera'e !e'in day occurs ithin the pay period.

• ,n "o'!Be!in #ate @on covera'e !e'in dateA: 4redits and deductions !e'in on the date

that !enefit covera'e for the plan type !e'ins.

2D 5/11/2015


28/65


• Pay Pd "ontainin! "o'! B!#t @pay period containin' covera'e !e'in dateA: 4redits and

deductions !e'in on the first day of the pay period containin' the covera'e !e'in date&re'ardless of hen the covera'e !e'in date occurs ithin the pay period.

• Pay Pd Precedin! "o'! B!#t @pay period precedin' covera'e !e'in dateA: 4redits and

deductions !e'in on the first day of the full pay period that precedes the covera'e !e'indate.

Deduction 3 ,lex Credits nd

se this 'roup !o, to indicate hen deductions and fle,i!le !enefit credits should !e taken. Ealueare:

• -st Full PayPd After "o'! B!#t @first full pay period after covera'e !e'in dateA: 4redits

and deductions !e'in on the first day of the pay period folloin' the covera'e !e'in date&re'ardless of hen the covera'e !e'in day occurs ithin the pay period.

• ,n "o'!Be!in #ate @on covera'e !e'in dateA: 4redits and deductions !e'in on the date

that !enefit covera'e for the plan type !e'ins.

• Pay Pd "ontainin! "o'! B!#t @pay period containin' covera'e !e'in dateA: 4redits and

deductions !e'in on the first day of the pay period containin' the covera'e !e'in date&re'ardless of hen the covera'e !e'in date occurs ithin the pay period.

• Pay Pd Precedin! "o'! B!#t @pay period precedin' covera'e !e'in dateA: 4redits and

deductions !e'in on the first day of the full pay period that precedes the covera'e !e'indate.

Processing !ents for COBRA Administration

4onsolidated mni!us Bud'et $econciliation ct @4B$A administration uses Benefits dministration processes to identify and process:

• )nitial 4B$ events& hich provide initial 4B$ covera'e to ualified 4B$

participants and their dependents.

• "econdary 4B$ events& hich e1tend co'era!e for 4B$ participants and their

dependents.

The initiation of a 4B$ event differs accordin' to your current implementation:

• )f you are currently orkin' only ith the Base Benefits !usiness process& the 4B$

event is initiated !y online People4ode.

• 6ith Benefits dministration& the 4B$ event is initiated !y Benefits dministration

hen a reco'ni(ed 4B$ action event is finali(ed.

The only e,ception to this rule is the vera'e *ependent event& hich is initiated !y the 4B$process for !oth the Base Benefits !usiness process and Benefits dministration.

This ta!le descri!es ualified 4B$ events delivered !y People"oft& actions that tri''erBenefits dministration to reco'ni(e these events as ualified 4B$ events& and potential4B$ !eneficiaries of the events:

2> 5/11/2015


29/65


Qualifying COBRAEvent

User Action rigger Potential COBRABeneficiaries

)oss of eli%i$ility due toter&ination'

E&ployee status c#an%es to ter&inated or suspended' E&ployee anddependents'

)oss of eli%i$ility due toreduction in #ours'

E&ployee status re&ains acti!eD Standard #ours decrease' E&ployee anddependents'

)oss of eli%i$ility due toretire&ent'

E&ployee status c#an%es to retired' E&ployee anddependents'

)oss of eli%i$ility due to&ilitary lea!e'

)ea!e of /$sence@Military )ea!e action@action reason entered fore&ployee'

E&ployee anddependents'

2eat# of e&ployee' E&ployee status c#an%es to deceased or .S*@2E/ entered asaction@reason code in t#e Co$ ta$le'

/ll dependents'

2i!orce' *#an%e in &arital status of e&ployee to di!orcedD c#an%e in statusof spouse to exspouse'

.a&ily Status *#an%e@2i!orce action@action reason entered fore&ployee'

Spouse'

Marria%e of dependent' Marital status of dependent c#an%es to &arried'

.a&ily Status *#an%e@Married 2ependents action@action reasonentered for e&ployee'

-ndi!idualdependent'

2ependent reac#esco!era%e a%e li&it

4o!era%e dependent5'

(ot identified $y Benefits /d&inistration' 4Benefits /d&inistrationdoes not auto&ate passa%e of ti&eF e!ents for dependents'5 1ou

&ust run t#e *BR/ process to identify o!era%e dependents'

-ndi!idualdependent'

E&ployee $eco&esentitled to recei!eMedicare'

Medicare entitle&ent date is reac#ed'

.a&ily Status *#an%e@Medicare Entitle&ent action@action reason isentered'

/ll dependents'

See Also

nderstandin' the Benefits dministration Process

Defining Rules for Benefits Billing

To define !enefit !illin' parameters& use the Benefits Billin' Parameters@B))F97P$%T%$"A component.

This section provides an overvie of event processin' for Benefits Billin' and removin'participants from Benefits Billin' and discusses ho to set up Benefits Billin' enrollments.

Understanding Event rocessing for Benefits Billing

The application of event rules for Benefits Billin' enrollment is overridden in certain situations:

2< 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna12.htm#i090f42a6801068a4https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna12.htm#i090f42a6801068a4


30/65


• The system does not start !illin' if the employee is not enrolled in a plan or has aived

covera'e.

• The system does not insert a !illin' termination if the employee is not actively enrolled in

!illin'.

• The system terminates active !illin' if the employee loses or aives covera'e&

re'ardless of the settin's on this pa'e.

)f none of these situations applies& the system inserts a record into the Billin' %nrollment ta!leand sets the:

• %mpl)* field to the employees )*.

• %mployee $ecord Fum!er field to the employees employment record num!er.

• Plan Type field to the plan type to !ill.

• 4B$ %vent )* field to (ero.

• Billin' "tatus field to Acti'e.

• Billin' $eason field to Ben Admin.

The system overlays e,istin' !illin' enrollments if it encounters duplicate effective dates andinserts ne active !illin' records& even if the employee is already !ein' !illed. The system carriesforard a hold status from a previous !illin' enrollment.

Billin' records are inserted durin' the close and finali(ation of the event. The system !acks out!illin' records if Benefits dministration reprocesses an event to a point prior to the insertion ofthe !illin' enrollments. Billin' records are not inserted for 'eneral deductions& !enefit pro'rams&leave plans& or vacation !uy or sell plans @plan types 00& 01& 5,& and


31/65


ages Used to Define +!les for Benefits Billing


Billin% Rules B/S_E>E(T_RU)ES3 Set Up HRMS, Product Related,/uto&ated Benefits, Eli%i$ility and

E!ent Rules, E!ent Rules Ta$le,Billin% Rules

2efine rules for Benefits Billin%enroll&ents'

Billin% E!entR)s 4$illin%e!ent rules5

RU(*T)_B/S8:3B Set Up HRMS, Product Related,/uto&ated Benefits, Reports,E!ent Rules Billin%, Billin% E!entR)s

)ist t#e para&eters in +#ic# $illin%enroll&ents are created or updateddurin% t#e Benefits /d&inistrationprocess'

Setting Up Benefits Billing Enrollments

ccess the Billin' $ules pa'e.

Billin' $ules pa'e

ou can define a different set of Benefits Billin' enrollment event rules for each eventclassification.

Rate 4ualifier

*etermines ho to modify the deduction calculation for !illin' purposes.

)f you enter !oth a percent calculation and a flat amount& the system adds them to'ether todetermine the total char'e.

"ee %nrollin' Participants.

Billing Ta%es ffect

)f you selected "tart Billin' or %nd Billin'& select an option to indicate hen the !illin' action takeseffect.

See Also

ana'in' Benefits Billin'

5US,6 Setting Up *ultiple/ Concurrent Open Seasons

)n the federal 'overnment& open seasons for various plan types are usually scheduledindependently of each other& and their solicitation periods often overlap. )n other ords& a +%9)@federal employees 'roup life insurance codeA open season may !e'in after a +%#B @federalemployee health !enefitsA open season solicitation period has started.

)n Benefits dministration for .". +ederal 9overnment& the a!ility to successfully run multiple&concurrent open enrollment processes depends upon to fields: %vent 4lass and %vent $ules )*.

To set up multiple& concurrent open seasons:

1. *efine open enrollment event classes for each open season scheduled for youremployees on the Bendmin %vent 4lass Ta!le pa'e.

31 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a6801092f1https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a6801092f1https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a6801092f1https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a68010937ahttp://showpopup%28%27%3Cimg%20src%3D../img/image12.gif%20WIDTH=622%20HEIGHT=362%3E',escape('Billing%20Rules%20page'))https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a6801092f1https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn15.htm#i090f42a68010937a


32/65


2. *efine open enrollment processes for each scheduled open season& and link to them theappropriate open season event classes.

se the pen %nrollment *efinitions pa'e.

3. *efine individual event rule )*s for each plan type availa!le to your employees.

se the %vent $ules pa'e.

;. To each event rule )*& associate the entire set of open enrollment event classes that youdefined in step 1& !y usin' the *ate $ules pa'e.

5. +or each event rule )*& use )'nore Plan and *efault ethod functionality to disa!leBenefits dministration processin' for all event classes linked to open seasons for plantypes other than the one linked to the event rule )*.

+or e,ample& if an event rule )* is associated ith the +%#B plan type& select )'nore Planfor all event classes not associated ith +%#B open season events.

se the proper default method to ensure that your employees are not automaticallymoved in and out of plans that are not part of the open season. The su''ested defaultmethod is Assi!n "urrent "o'era!e Else %one.

C. nce youLve finished definin' your event rule )*s& link them to their correspondin' plantypes !y usin' the Benefit Pro'ram pa'e.

Place +%#B event rule )*s ith +%#B plan types& T"P @Thrift "avin's PlansA event rule)*s ith T"P plan types& and so on.

D. $un open enrollment processes as planned for your various open season events.

)f you set up the system correctly& open enrollment for a +%9) open season processesonly plan types linked to the +%9) event rule )*& open enrollment for a T"P openseason processes only plan types linked to a T"P event rule )*& and so on. our openenrollment processes can run concurrently as lon' as each process is associated ith adifferent plan type or set of plan types.

People"oft %nterprise Benefits dministration >.< PeopleBook 4opyri'ht ? 200; People"oft& )nc. ll ri'hts reserved.

Displaying Dependent and Beneficiary Information

The 4ollect *ep/Ben check !o, appears on !oth pa'es:

•

Benefit Pro'ram - Plan Type and ption at the plan level.

• %vent $ules.


6hen the 4ollect *ep/Ben check !o, is selected on the Benefit Pro'ram-Plan Type and ptionpa'e& the system collects the information pertainin' to dependents and !eneficiaries and displaysthat information on the eBenefit "ummary and the eBenefit *etail )nformation pa'es.

32 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/legal_hr89pbr0.htmhttps://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/legal_hr89pbr0.htm


33/65


!ent Rules

6hen the 4ollect *ep/Ben check !o, is selected on the %vent $ules pa'e& the system displaysthe dependent and !eneficiary information on the eBenefits %nrollment pa'es.

+or health plans on the enrollment form& the system collects elections at the plan level. Theemployee selects hich dependents should !e covered under the plan !y selectin' a check !o,

ne,t to each individuals name. The system derives the covera'e code !ased on the dependentsthat are selected.

6hen the check !o, is clear& the system hides the dependent or !eneficiary sections and doesnot collect dependent or !eneficiary elections. +or health plans on the enrollment form& thesystem collects elections at the covera'e code level hen the check !o, is clear.

The 4ollect *ep/Ben field orks ith the event rules )'nore *ep/Ben %dits field. )f the 4ollect*ep/Ben check !o, is selected& the )'nore *ep/Ben %dits check !o, should not !e selected.

See Also



Displaying Savings lan F!nd "llocations

The 4ollect +unds llocations check !o, appears on three pa'es:



• %vent $ules.


6hen the 4ollect +unds llocations check !o, is selected on the Benefit Pro'ram-Plan Type and

ption pa'e& the system collects the information pertainin' to savin's plans and displays thatinformation on the eBenefit "avin's "ummary and the *etail )nformation pa'es.

!ent Rules

6hen the 4ollect +unds llocations check !o, is selected on the %vent $ules pa'e& the systemdisplays the dependent and !eneficiary information on the eBenefits %nrollment pa'es.

This field orks in concert ith the event rules )'nore )nvestment %dits check !o,. )f the 4ollect+unds llocations check !o, is selected& then the )'nore )nvestment %dits check !o, should !ecleared.

Setting Up Domestic #overage Information

n the enrollment form it may !e necessary to display information a!out to health plans on onepa'e. These can occur in situations here the employee is eli'i!le for a health plan that is linkedto a nonualified health plan.

The *omestic 4overa'e +or field determines hether plan types can !e com!ined on theenrollment form. This field displays on the Benefit Pro'ram - Plan Type and ption pa'e for plantypes 15& 1C& and 1D.

To set up domestic covera'e information:

1. ccess to the Benefit Pro'ram - Plan Type and ption pa'e.

33 5/11/2015

https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbbn/htm/hbbn05.htm#i090f42a680109038https://psbooks.mycmsc.com/PSOL/sahr89_846/eng/psbooks/hbna/htm/hbna06.htm#i090f42a680106860


34/65


2. *isplay the plan type level information for the nonualified health plan.

3. )n the "elf-"ervice 4onfi'uration section& enter the num!er of the plan type that controlsthe cross-plan validation in the *omestic 4overa'e +or field.

+or e,ample& for plan type 15& hich is the nonualified medical plan& you ould enter 10 in the*omestic 4overa'e +or field. Thats !ecause plan type 10 controls the cross plan validation for

plan type 15. +or plan type 10& the *omestic 4overa'e +or field is !lank.

S!ppressing lan Type Information

The "ho if no choice field is located on the Benefit Pro'ram Ta!le - Plan Type and ption pa'efor all plan types.

This check !o, controls hether a plan type is displays on the enrollment hen the employee hasno option to choose and cannot aive out of the option. 'ood e,ample is paid vacation.%mployees receive the !enefit& !ut you dont display it on the enrollment form.

)f the check !o, is selected& the system displays the plan type in the enrollment form summary.6hen the check !o, is cleared& the system ill not display the plan type.

Displaying #ostsThe 4ost +re on %nrollment +orm field is located on the Benefit Pro'ram Ta!le - BenefitPro'ram pa'e at the pro'ram level. This check !o, controls hether the annual costs or the per-period costs @deductionsA are displayed on the enrollment form.

Displaying #redits

The "ho 4redits on %nrollment +orm field is located on the Benefit Pro'ram Ta!le - BenefitPro'ram pa'e at the pro'ram level. )f selected& this check !o, indicate for the system to displaytotal cost and credits on the pa'es.

Setting Up the Self$Service lan Descriptions Field

6hen settin' up !enefit plans for health& disa!ility& leave& or retirement !enefit plan types& youcan enter a description a!out the plan on the Benefit Plan Ta!le that displays on the enrollmentpa'es.

Setting Up Uniform Resource $ocators

The enrollment form and other !enefit transaction pa'es are desi'ned to displays links to:

• %mployee hand!ooks.

• Benefit provider e!sites.

• "ervice provider e!sites.

The specific uniform resource locator @$A address& description& and identifier are entered onthe $ ta!le. nce the address& description& and identifier are entered in the $ ta!le& thenonly the identifyin' code is entered in the Benefit Pro'ram ta!le& Eendor ta!le& and Benefit Planta!le.

The "P* $ )* on the Benefit Plan ta!le has priority over the 9eneral Policy $ )* on theEendor ta!le hen displayin' one or the other ne,t to plan provider.

The rules that determine hich $ appears ne,t to plan name on !enefit plan revie pa'es are:

3; 5/11/2015


35/65


• )f a $ identifier is connected to the "P* $ )* on the Benefit Plan ta!le& this is the

link that appears on the !enefit plan revie pa'e.

• )f a $ identifier is connected to 9eneral Policy $ )* on the Eendor Policy ta!le and

no "P* $ )* is defined& this is the link that appears on the !enefit plan revie pa'e.

The uthori(ed Providers $ )* on the Eendor Policy ta!le is independent of the links listed

a!ove. )f an $ identifier is connected to the uthori(ed Providers $ )*& then that linkappears on the $evie pa'e ne,t to +ind a #ealth 4are Provider under the dditional )nformationsection. This link is for health plan types only& no link ill appear for the other plan types.

+or the 9eneral Policy $ )*s and uthori(ed Providers $ )* links to ork& a 'roup num!eris reuired on !oth the Eendor and Benefit Plan ta!les.

)t is recommended that you use a prefi, namin' convention& such as the one shon !elo:

• se SP# as a prefi, hen definin' "ummary Plan *escription $ )*s

@"$PF*47$7)*A: "P*7%TFPP.

• se $E% as a prefi, hen definin' the 9eneral Policy $ )* @P)47$7)*A:

9%F7%TF.

• se PR& as a prefi, hen definin' the uthori(ed Providers $ )*@E%F*$7$7)*A: P$E7%TF.

See Also

Enterprise PeopleTools PeopleBook: System and Ser'er Administration(Gsin' PeopleToolstilitiesH

Setting Up %andboo& Lin&s

These $s provide links to the enrollment hand!ook. There can !e a link to the entire hand!ookand a link to each of the plan-type sections.

Because the hand!ooks may vary !y !enefit pro'ram& the keys are !enefit pro'ram and plantype. The $ )dentifiers are on the !enefit pro'ram definition at !oth the pro'ram and plan-typelevels.

There can !e one $ for the entire hand!ook or separate $s for each plan type.

Setting Up 'eneral olicy Lin&s

These $ )dentifiers provide links to the provider home pa'es or to a company intranet site. Thefields are defined on the Eendor ta!le.

Setting Up "!thori(ed rovider Lin&s

These $ identifiers provide links to the providers P4P finder& and are only applica!le for health

plan types. The fields are defined on the Eendor ta!le.

Setting Up SD )S!mmary lan Description* Lin&s

These $ identifiers provide links to the plan "P*s. The fields are defined on the Benefit Planta!le.

Setting Up Text Bloc%s

35 5/11/2015


36/65


The te,t !locks are a collection of para'raphs& sentences& phrases& and ords that are usedhen displayin' the enrollment pa'es. ll ordin' on the pa'es ill come from this collection&ith the e,ception of error and arnin' messa'es& hich use essa'e 4atalo' ;001.

Deli!ered Text and ffecti!e Dating

This te,t is effective-dated& hich allos it to !e chan'ed from one plan year to the ne,t. The

delivered te,t has an effective date of 1/1/1


37/65





This is a list of the fields on the folloin' ta!les: 63%B7T%8T& 63%B7T%8T7%++*T& and63%B7T%8T7"9)*







•

%vent 4lass n event class or !lank.






38/65


The function does not have to supply the !enefit pro'ram or event class !ecause these valuescan !e derived from the event itself and do not chan'e.

People"oft %nterprise eBenefits >.< PeopleBook 4opyri'ht ? 200; People"oft& )nc. ll ri'hts reserved.

Displaying Savings lan F!nd "llocations

The 4ollect +unds llocations check !o, appears on three pa'es:



• %vent $ules.

Benefit Program # Plan

Documents

Understanding EBenefits