Peoplesoft Benefits Documentation[

TABLE OF CONTENTS

1 Introduction...............................................................................................................................................................4

PURPOSE.................................................................................................................................................................................4REFERENCES...........................................................................................................................................................................4STRUCTURE OF THE DOCUMENT.............................................................................................................................................4

2 System Overview....................................................................................................................................................5

3 Base Benefits Setups............................................................................................................................................6

4 Benefit Administration Setups.....................................................................................................................17

5 Benefits Pre Processor......................................................................................................................................43

6 Changes to EE data..............................................................................................................................................47

7 Reports........................................................................................................................................................................48

8 Appendix....................................................................................................................................................................51

APPENDIX – A GLOSSARY..........................................................................................................................................51APPENDIX – B QUICK NAVIGATIONS......................................................................................................................51APPENDIX – C TABLE REFERENCES.........................................................................................................................51APPENDIX – D Review Details............................................................................................................................52

Report Title PublicationPeopleSoft Benefits Documentation PeopleSoft Benefits Module

1 Introduction

Purpose

Peoplesoft Benefits Documentation is an evolving document that provides information about the Benefits module implemented at Albertsons. It also facilitates as reference for those who are new to the system and for getting a quick start by providing high level understanding of the module’s functionality.

References

Reference Manuals Wipro PeopleSoft COE documentation Peoplesoft online library Discussions/Interactions with the Application specialist

Structure of the Document

Chapter 1 IntroductionChapter 2 System OverviewChapter 3 Base Benefits SetupsChapter 4 Benefit Administration SetupsChapter 5 Benefits Pre ProcessorChapter 6 Changes to EE data, Processes to be runChapter 7 ReportsChapter 8 Appendix

Page 2 of 70


2 System Overview

This diagram illustrates the interlinkages between Base Benefits and other PS HRMS modules

PeopleSoft HRMS

1. Employee data flows from Core HR tables to Benefits tables. Employee Benefit Program

details flow from Benefits tables to Core HR2. Deductions for availing benefits are passed on to the payroll module. These will be

included while calculating employee’s pay

Page 3 of 70


3 Base Benefits Setups

This section details what are the setups required for Base Benefits module and how they all are interlinked

Before we start, let’s get familiar with few frequently used table references/terminologies and their meanings

Table PS Table name DefinitionVendor/Provider ps_vendor Organization that provides or services a benefit offering.Rate Tables ps_age_rate_tbl

ps_flat_rate_tblps_salary_rate_tblps_svc_rate_tbl

There are four types of rate tables: Age, Salary, Service, and Flat. These tables are used to calculate the cost of a benefit.

Calculation Rules

ps_calc_rules_tbl Defines the rules for calculating benefit deductions, such as as-of dates for age, service, premium, and coverage calculations; rounding rules; and minimum/maximum coverage amounts.

Coverage Codes ps_covrg_cd_tbl Defines who can be covered by the benefit. Eg: Only Spouse, Spouse and children, Only children

Deduction Code ps_deduction_tbl Defines the rules for calculating the amount of the deduction and how payroll should process the deduction.

Benefit Plan Type

XLAT Values Any benefit category, such as health, life, or savings.

Benefit Plan ps_benef_plan_tbl A specific benefit offering within a plan type. For example, Basic Dental or Enhanced DentalTo define a benefit plan, identify the benefit plan type and name the benefit plan. You can link a benefit plan to many benefit programs; you don’t need to reenter the same benefit plan information, no matter how many benefit programs include the plan.Is defined through multiple components such as rate tables and calculation rules

Benefit Program ps_ben_defn_pgm A collection of benefit plans. Differs by group of employees like hourly, salaried, and executive employees. We can defined as many programs as necessary based on the business rules.

Pictorial representation of how the Benefit Plans and Employee data are linked

Page 4 of 70


Only one benefit program an Employee.

Sample Chosen :

Benefit Program : 132 (PT Chicagoland 881 Clerks)Benefit Plan Type : 10 (Medical)Benefit Plan : BPOS1BRate: UA11 (Flat Rate Type)

Benefit Program

Navigation: Setup HRMS > Product Related > Base Benefits > Program Structure > Benefit Program Table

o While searching for the Benefit Program, sometimes we get to see muultiple rows for a benefit program. These are tagged to different effective dates usually

Page 5 of 70


Same program can be assigned to more than one employees.Different effective dates for one benefit program:

program with new effective date provides additional benefits compare to same program with previous effective date.

Page 6 of 70


Benefit Plan Table

Navigation: SetUP HRMS > Product Releated> Base Benefits> Plans and Providers> Benefit Plan Table

o A specific benefit offering within a plan type. For example, Basic Dental or Enhanced Dental for a ‘Dental’ plan type

Rate Table

Page 7 of 70


Navigation: Setup HRMS > Product Related > Base Benefits > Rates and Rules > Flat Rate Table

o The cost of benefits chosen is calculated based on the rates definedo These are defined based upon:

Age Salary Service Flat amounts

Calculation Rules table

Navigation: Set Up HRMS > Product Related > Base Benefits > Rates and Rules > Calculation Rules Table

o Define the rules for calculating the benefits deductions

Eg: Benefit Program 132, plan type 20

Page 8 of 70


Calc Rule definition page

Employee Job Data Page – Benefit Program Participation Tab. This tab is used to assign Program to the employee.

Page 9 of 70


Few other setups to note

Vendor/Provider Table

Navigation: Setup HRMS > Product Releated > Base Benefits > Plans and Providers > Provider/Vendor Table

Coverage Code Table

Navigation: Set Up HRMS > Product Related > Base Benefits > Plan Attributes > Health Coverage Codes

Most commonly used Coverage Codes and their description

Coverage Code

Description

1 Employee only covered2 Employee and Spouse covered3 Employee and Dependants(Children) covered4 Family coverage

(Employee+Spouse+Children)covered8 Employee and one child covered

Page 10 of 70


Plan Types

o These are two character, alphanumeric codeso Stored in Translate Table

Category Numbering SequenceHealth 10 – 19, 1A – 1ZLife and Accidental Death 20 – 29, 2A – 2ZDisability 30 – 39, 3A – 3ZSavings 40 – 49, 4A – 4ZLeave 50 – 59, 5A – 5ZFlexible Spending Accounts 60 – 69, 6A – 6ZRetirement 70 – 79, 7A – 7ZPension 80 – 89, 8A– 8ZVacation Buy/Sell 90 – 99, 9A – 9Z

Deduction Table

Navigation: Home > Setup HRMS > Product Related > North American Payroll > Deductions > Deduction Table

o Here we define the payroll processing rules for Benefits to which Employee is enrolled

Page 11 of 70


Page 12 of 70


Assign Benefit Program to an associate

Navigation: Benefits > Enroll in Benefits > Assign to Benefit Program

o Page where we can assign benefit program to an associate

Page 13 of 70


4 Benefit Administration Setups

Once Base Benefits setups are done, we have to setup Benefit Administration related tables. This section detailes the same

To start with, activate PeopleSoft Benefits Administration on the installation table.

Installation Table

Navigation: Setup HRMS -> Install -> Installation Table

Other setups required are listed below

Step ReferenceDefine eligibility rules. Setting Up Eligibility Rules Define geographic eligibility rules. Setting Up Eligibility Rules Define event rules. Setting Up Eligibility Rules Define flexible credits. Setting Up Eligibility Rules

Note : Not covered in this documentation(As per peoplebooks: (USF) Flexible credits are not generally used in the U.S. federal government)

Build your automated benefit programs.

Building Automated Benefit Programs

For Canadian users, define Canadian credit allocation rules.

(CAN) Handling Canadian Credit Allocations

Note: Not covered in this documentation

Page 14 of 70


Before we go through each of these setups, here are few terminologies to get familiar with:

o Bas Group ID: Group Employees based on geographical or other means of company structure for ease of Benefit records handling.

o Eligibility Rules Table: To enroll employee into a benefit program the field values should match with the list of fields selected and defined in rules table. This acts as a matrix table for selecting benefit program to each employee by meeting required field values.

o Event Class ID: This will prioritize the benefit records on each employee based on the action. (i.e HIR, FSC, etc.,)

o Event Rules Table: Each Event rule is defined for each plan such as Medical, Dental etc., that will process the election on each plan based on event class or a collection of event class.

o Event Rules table IDs are assigned to the Benefit Program.o Snap shot, Open enrollment & Event Maintenance definition: Snapshot: Used once first time

implementing Ben Admin. Open Enrollment: Every year once at the benefit enrollment period. Event Maintenance: Day to day use of Ben Admin to process various employee events.

o Schedule Table: Assign Create snapshot, Event Maintenance & Open enrollment definition & Bas Group Id for processing Ben Admin.

Define Eligibility Rules

Navigation: Setup HRMS > Product Related > Automated Benefits > Eligibility and Event Rules > Eligibility Rules Table

o To determine the benefit program for which each employee is eligible o To determine eligibility for each plan option within a benefit programo To set up the system so that a participant can be eligible for only one benefit program at a

time o To define eligibility based on a wide range of personal and job information, as well as

geographic location

Sample Chosen: (Example referred above)

Benefit Program : 132 (PT Chicagoland 881 Clerks)Benefit Plan Type : 10 (Medical)Benefit Plan : BPOS1B

o Plan Type Tab in the Benefit Program Definition Page

Page 15 of 70


o Eligibility ID’s are defined as below in the ‘Eligibility Rules’ definition page. Eg: ‘SB’ Elig ID

Page 16 of 70


Eligibility Criteria fields

Page 17 of 70


PeopleSoft provides 27 different criteria fields (plus 2 federal-specific fields) that can be used to determine employee benefit eligibility. Nine of these criteria fields can be defined to meet organization specific needs. The criteria fields are:

Field Name Field NameAge Officer CodeBenefit Status Pay GroupEligibility Config 1– 9 Regular and TemporaryEmplID Override Regulatory RegionEmployee Class Retirement Plan (Federal)Employee Type Salary GradeFEHB Indicator Service MonthsFLSA Status Standard HoursFTE StateFull/Part Time Union CodeLocation

Define Geographic Location Eligibility Rules

Navigation: Set Up HRMS > Product Related > Automated Benefits > Eligibility and Event Rules > Geographic Location Elig (Eligibility)Table

o To define postal code ranges for employee home or work locations.

Possible scenarios

If the employee The employee will

Lives within the postal range and works within the postal range.

Pass

Lives within the postal range but works outside the postal range.

Pass

Lives outside the postal range but works within the postal range.

Pass

Lives outside the postal range and works outside the postal range.

Fail

Sample Chosen: (Example referred above)

Benefit Program : 132 (PT Chicagoland 881 Clerks)Benefit Plan Type : 10 (Medical)Benefit Plan : BPOS1B

o Plan Type Tab in the Benefit Program Definition Page

Page 18 of 70


o Geog Locn Eligibilities are defined as below in the ‘Geog Locn Elig Table’ definition page. Eg: ‘BCBS’ Geog Locn

Page 19 of 70


Define Event Rules

Navigation: Set Up HRMS > Product Related > Automated Benefits > Eligibility and Event Rules > Event Class Table

o Event rules are not the same as eligibility rules. Eligibility rules help determine what benefit program and benefit plan options an employee can have. They tell the system that because of changes to employee data, Employee X is no longer eligible for certain plan options, but is eligible for others.

o Event rules determine which eligible options Employee X can actually choose, based on the type of event that has occurred and when new coverage begins. The event rules also determine when the plans that Employee X is now ineligible for will be terminated and which plan options Employee X will be enrolled into if new enrollments are not specified.

o Event Rules are attached to a benefit program on the Benefit Program page. We can have a different event rule for each plan type in a benefit program.

To set up event rules:o Use the Action Reason Table to link personal action/action reason combinations that affect

benefits eligibility. Personnel actions, such as promotions, transfers, terminations, salary increases, and leaves of absence are attached to action reasons that explain why the action took place. Each defined action/reason combination enables the system to classify and track the events that cause changes to employees’ employment and benefit coverage status.

Page 20 of 70


Eg: Hire transaction. Navigation: Setup HRMS > Product Related > Workforce Administration > Action Reasons > ‘HIR’ action

o Use the Event Class Table to assign the types or classes of events you want the system to recognize, and to control how the system processes event classes.

o Use the Event Rules Table to define the specific behavior that the system takes for each event classification.

Event Class Table. Eg: ‘ADR’ event (Address Change Event)

Event Rules Table. Eg: ‘Dental’ Event Rules ID for ‘ADR’ Event Class

Page 21 of 70


Date Rules Tab - Defining Start and End Dates for Coverage, Deductions, and Flex Credits

Define Trigger Events

Page 22 of 70


1. Manually insert events into the BAS Activity Table

Navigation: Benefits > Manage Automated Enrollment > Events > Review Bas Activity

o Manually insert events to be processed according to event rules that map to the BAS action you enter when you run the Ben Admin process.

o We can only insert event classes into the BAS Activity table that have the ‘Manual Event Allowed’ check box selected in the Event Class Table.

o As delivered, we can insert two event classes manually: Family Status Change (FSC) and Miscellaneous Status Change (MSC).

2. Define passive events

Navigation: SetUp HRMS > Product Related > Automated Benefits > Eligibility and Event Rules > Passive Event Definition

o Define events that are not initiated by data entry.

o For Eg: Set up a passive event to determine which employees are eligible for certain benefits once they've worked in the organization for a year. To do this, define a passive event with the service date event type and an Event Limit - Months value of 12.

After setting up the passive event, the system calculates the difference between employees' service dates and the process date, and it triggers the event for any employees with a difference of twelve months within the date range we specify on the Ben Admin process run control page. The system then processes the passive event.

Page 23 of 70


3. Automatically trigger events through employee data changes

o An administrator opens an employee data page, such as the Personal Data page, and enters a change to employee information or The employee enters a marital status or birth or adoption change through eBenefits. (self service)

o To increase the efficiency of the Event Maintenance process, the system triggers "job" and "non-job" events from a variety of different tables. Job events are relevant to employment, such as hires, transfers and terminations. Non-job events cause changes in employees’ personal or demographic information that affect benefits eligibility or elections. Possible non job events could be ‘DOB Change’, ‘Postal Code Change’, ‘Service Date Change’, ‘State Code Change’.

To summarise the Base Benefits and Ben Admin setups detailed above:

Build the foundation by setting up Base Benefit information:o Define benefit deductions using the Deduction Table. o Identify benefit plans using the Benefit Plan Table page. o Identify benefit providers using the Provider and Vendor Table o Define benefit coverage using the Coverage Codes o Establish rate tables using the Age-Graded Rate Table page, the Salary Rate Table page, the

Service Rate Table page and the Flat Rate Table page.o Establish calculation rules using the Calculation Rules Table.

Page 24 of 70


Build the Automated Benefits program:o Define the benefit program.o Link the plan types and options.o Attach event and eligibility rules.o Define costs and credits.

Setups for Open Enrollment and Event Maintenance

Define Open Enrollment Ids

Navigation: Set Up HRMS > Product Related > Automated Benefits > Processing Controls > Open Enrollment Definition

o Set up the parameters of the open enrollmentoo List of Benefit Programs to be covered under this ‘Open Enrollment’ event

Period end date and period begin date are used by ben admin. Enrollment begin date and enrollment end date are used by Employee. Define SnapShot Ids

Navigation: Set Up HRMS > Product Related > Automated Benefits > Processing Controls > Snapshot Definition

o Use snapshot if you are going for event maintenance and not for Open Enrollment.Snapshot definition : used by employee for online election.

Page 25 of 70


Establishing Process Schedular for running Ben Admin Process

Navigation: Setup HRMS > Product Related > Automated Benefits > Processing Controls > Schedule Table

o Ben Admin processes are grouped and identified by schedules. This includes the Run Control process, enrollment statements, data entry, and confirmation statements.

o We need to define at least one schedule for open enrollment and another for event maintenance

Event Maintenance Schedule Id

Open Enrollment Scehdule Id

Page 26 of 70


Ben Admin Run Control Page

Navigation: Benefits > Manage Automated Enrollment > Events > Run Automated Event Processing‘Schedule and Chkpt Restart’ Tab

Page 27 of 70


o Identify the Open Enrollment, Event Maintenance, or Snapshot schedule for which you're planning to run the Ben Admin process

‘Participant Lists’ Tab

o Add a specific set of employees under ‘Schedule Only Employee(s)’ grid to the schedule you're processing or under ‘Process Only Participant(s)’ to process a specific set of employees.

‘OE/Snapshot’ Tab

o These will be enabled when Schedule ID selected in the first tab is for OE/Snapshoto Enter reprocessing information for Open Enrollment or Snapshot schedules. Capture new

participants for a specific Open Enrollment or Snapshot schedule already in progress. Finalize and apply defaults for participants in the schedule who have been processed with errors.

Page 28 of 70


‘Passive Event Processing’ Tab

For Event Maintenance schedules, identify the passive events that have occurred in a defined period of time and create an entry of the events in the BAS_ACTIVITY table.

List of possible Process Statuses when Ben Admin is run

Process Status Description Next Processing Steps

AE - Program Eligibility Assigned Error

Participant event is assigned to multiple programs.

The system cannot process the participant event through the next stage (Option Preparation) until the errors are corrected. Most likely need to make corrections to participant personal/employment/job information or to program eligibility information. Each time Ben Admin is run, the system reevaluates AE events.

AN - Program Eligibility Assigned None

Participant event is not assigned to a benefit program.

During the Option Election phase of the process, the system determines if the AN participant associated with the event has current elections that require termination due to loss of program eligibility. If not, the event is assigned to FA (Finalized - Assigned None) status and processing ends. If the participant does have elections, the system updates process status to PR (prepared). Before the system can terminate this event, you have to acknowledge it on the data entry pages.The Find Terminations workflow process locates participant events at PR status that require termination.

AS - Program Eligibility Assigned

Participant event is assigned to a benefit program.

The event continues on to a process status of FP (Finalized - Prepared None), PE (Prepare Error), or PR, depending on the associated participant's eligibility for benefit options.

FA - Finalized - Benefit Program None

Participant event has no program assignment and no current elections. Used for events assigned an AN process status during the Scheduling and Program Assignment and whose associated participants do not have current benefit elections.

There is no further processing for this event. The online page description for this process status (on the Schedule Summary page, for example) is Program None.

FP - Finalized - Prepared None

System has assigned the participant event to a benefit program, but the associated participant is not allowed to elect any

No further processing occurs for this participant event. The online page description for this process status (on the Schedule Summary page, for example) is Prepare None.

Page 29 of 70


new options.PE - Prepare Error The system has

encountered an error. Events are given a PE process status during option eligibility determination or calculation of credits.

To correct, make corrections to the personal/employment/job information of the associated participant or to plan and option eligibility information. Each time Ben Admin in run, the system reevaluates PE events.

PR - Prepared The system has calculated eligible options, credits, rates. AN events that have current elections can also be brought to a status of PR.

> For PE or AS events, processing stops. Enrollment forms should be created for and delivered to the participant associated with the event to bring the event to a process status of NT (notified).> For AN events, processing also stops. Review the event (a pending termination of benefits), confirm it by marking it for finalization, and then run the second phase of Ben Admin. The event is brought to a process status of ET (Entered. The system brings the event to a process status of FE (Finalized - Enrolled) and automatically inserts termination rows for each of the associated participant's current elections.

NT - Notified Election enrollment form has been distributed to the participant associated with the event. The system updates the event's process status to NT when election forms are generated for that participant via report BAS004.Participants can only advance to NT if their previous process status was PR.

Participants need to complete their election forms and return them to the HR/Benefits department. When the elections are entered into the system with the data entry pages, the system will advance the events to an ET (entered) process status.

o Any processing errors are typically caused by problems with:• Eligibility rules. • Event rules.• The benefit program involved.• The participant’s HR information.

o When an error occurs, we need to: • Evaluate the error.• Correct it.• Reprocess the event.

A quick look at the flow of the above process statuses

Page 30 of 70


Entering, Validating and Loading Elections

Page 31 of 70


Process Status Description Next Processing Steps

ET - Entered A benefits administrator (or the employee via PS eBenefits) has entered the participant's new elections into the system, and they are ready for validation by Ben Admin process. Participant events with a process status of ET can have a prior process status of PR, NT, or RE (Reentered).

> If there are no errors with the elections, the elections are posted to the appropriate benefit and payroll tables and the system updates the process status to FE.> If there are errors, the status becomes EE. > If we run the Ben Admin process with Finalize selected, EE participant events are brought to FE status, and the system goes through the normal validation. If any of the employee's choices are invalid, event rules are to be refered to determine whether current elections or defaults should be loaded.

EE - Election Error The system encountered an error in processing the elections for the participant associated with the event. No elections are posted to the Base Benefits business process tables. Errors are posted to the Message Table and are identified by participant and event.The previous process status was either ET or EE.

No further processing occurs for this participant event. We need to correct the errors by reentering employee elections and run the Ben Admin process again.Alternatively, we can "force finalize" this participant event to finalize it with errors. The system loads the default values for the associated participant's erroneous benefit option elections. If a dependent/beneficiary or investment choice is in error, the system loads the employee's option choice but does not load the dependent/beneficiary or investment choice. We can generate confirmation statements for participants whose events have an EE process status; the form indicates the plan information in error along with the valid plan choices.

FE - Finalized - Enrolled

Ben Admin processing is complete for the participant event. All elections have been validated and loaded to the appropriate Base Benefits business process and Payroll tables.Events reach this status either from a process status of ET, EE or PR, or if we "force finalize" a participant.If the participant came from a process status of PR due to a loss of all eligibility, the system inserts a termination row for each of the participant's current elections.

We need to generate and deliver a confirmation form to the participant associated with the event. To change a participant's elections after they've been finalized (for example, if a participant wants to correct information on the confirmation statement), we can reprocess them by giving the associated event a process status of RE (re-entered) in the Event Status Update page and rerunning the Ben Admin process.

RE – Re-Entered Enables elections associated with processing for the participant event to be reentered after the participant event has been brought to a process status of FE.Events are updated to RE status through the Event Status Update page

After we update the elections in the data entry pages, the system updates the process status from RE to ET.

A quick look at the flow of the above process statuses

Page 32 of 70


Ben Admin Process Results

Navigation: Benefits > Manage Automated Enrollment > Review Processing Results

o Using this, we can Review error messages. Review process results for schedules.

Page 33 of 70


Enter search criteria to review process results for participant events Review process results for participant events Review event information for participants Review plan type details for participant events. Review cost and credit information for plan types Review passive event processing history

Navigation: Benefits > Manage Automated Enrollment > Investigate Exceptions

o Using this, we can Review eligibility results Run various Ben Admin related reports like process status of participants, eligibility to a

benefit program details for a participant, invalid elections etc

Page 34 of 70


5 Benefits Pre Processor

Benefits preprocessor which is also called as an Eligibility processor is a customised process to take care of Albertsons specific benefit rules and calculations. It identifies the associates’ initial eligibility for a Health and Welfare plans or Retirements plans. Also looks at associates Hire date, Benefit program, their Elig Config values. Accordingly, the process inserts a corresponding row into Job CI staging table ps_a_ca_jobci_stg.

When the Job CI (ALB_CA_JOBCI App Engine) is run, appropriate rows are inserted in the Job Data record for an associate.

Navigation for Pre Processor: Benefits > Manage Automated Enrollments > Events > Run Automated Event Processing > Select appropriate Sched ID > Select list of emplids to schedule > Select ‘ALBCHW01’ Java process to run

Navigation for Job CI: Release 4 interfaces > Contract Admin Job Data Port

To summarize, the Eligibility processor performs the following:1. If the associate is hired new in to the system, looks the benefit program he/she belongs to.2. Based on the Benefit program identifies all the Benefit type he will be eligible for.3. Calculates the wait period before he can enter into the Benefit program and updates the

ADR (associate detail record) record4. If he qualifies for any of the benefit types then inserts a row into the staging table with the

corresponding Eligibility Configuration values.5. If the associate is in the system for a while and if he/she completes the wait period, the

eligibility processor picks the associate and process the associates with all the rules governing the benefit type and inserts a row into the staging table.

6. Then ALBJOBCI process will pick these associates and inserts a row into the Job Table.

Diagram depicting the Eligibility Processor’s flow

Page 35 of 70


At the same time eligibility processor enters data in BAS_action table.Terminologies used

Elig Config Values: There are 9 Elig Config values. These are Elig_config1, 2..,9. Each value represents the associates’ eligibility in benefit type.

Benefit type: There are different benefit types attached to each benefit program. They are:1. 10(NON) – No Benefit2. 20(VMD) – Voluntary Medical/Dental3. 30(Single) – Eligible for Single benefit4. 40(Family) – Eligible for Family Medical/Dental plan5. 45(Requal) – Re-qualification of medical/dental Benefit6. 50(PIP) – Pension Investment Plan7. 60(401K) – ASRE plan8. 70(Catch-up) – ASRE Catch-up plan9. 80(Makeup) – ASRE Makeup Plan10. 90(2DC) – 2DC plan11. 95(RIC) – Shaw RIC plan

Company Benefits page

Page where the eligibility rules are defined and based on which Eligibility Processor identifies associate’s benefit eligibilities

Navigation: Setup HRMS > Product Related > Albertsons Contract Admin > Program Tables > Company Benefits

Eg: Benefit Program 132

Page 36 of 70

Eligibility Processor (Identifies the Eligible associates)

JOBCI (Row inserted with corresponding Elig Config values in this staging table)

Job Data(Job CI inserts a row into the Employee job data)

Associate Detail Record(Inserts a row for each benefit Type for tracking the Eligibility)

ALBCHW01

ALBJOBCI


For each CB Type, required rules are defined here

When we click on ‘Method Items’ hyperlink, we get to view the components of each rule type

Page 37 of 70


Page 38 of 70


6 Changes to EE data

Now that the setups are done, lets look at few day to day transactions which change employee data and how they impact employee benefits enrollment

6.1 Employee choosing benefits through ESS

Sample Chosen: Changes to Medical/Dental/Vision benefit enrolments

These are the existing benefit plans chosen by the associate by name Bruski-Markowitz, Donna

Medical

Dental

Page 39 of 70


Vision

Page 40 of 70


Coverage begin date = event dateElection date = system date

Login as Employee and make changes to the benefits enrolled

Navigation: Home > ESS > Benefits > Benefits Home > Annual Enrollment

Backend Table: W3EB_EVENT_VW

Benefits Main Page. Here the employee needs to choose the benefits

Page 41 of 70


Page 42 of 70


Chose the benefit plans: Click on ‘Edit’ button displayed next to the Benefit Plan Type > Select a benefit plan and any dependant enrolment.

o Here we are choosing ‘Waive’ option for Medical, Dental and Vision plan types

Below is the screenshots of choosing ‘Waive’ for medical plan type

o Perform the above steps for Dental and Vision as wello Selected option appears in the benefits summary page

Page 43 of 70


o When completed with benefits selection, click on ‘Continue’ displayed in the benefit summary page.

o Page summarizing the employee’s benefits chosen > Click on ‘Submit’

Page 44 of 70


Final confirmation page

Page 45 of 70


‘Event Status’ changed from ‘Open’ to ‘Submitted’

o Run Ben Admin through On Demand Event Maintenance (As this is for single emplid)

Navigation: Benefits > Manage Automated Enrollment > Events > On Demand Event Maintenance > Select the emplid

o Bas Process Status is ‘Entered’ and Event Status is ‘Open’

Page 46 of 70


o Select ‘Validate/Finalize’ button > Following message is displayed

o Note that the Bas Process Status is changed to ‘Finalized – Enrolled’ and Event Status is ‘Closed’

Page 47 of 70


Backend table to view the event status: PS_BAS_PARTIC

Above made changes should appear in the Health Benefits Record of the associate

Navigation: Benefits > Enroll in Benefits > Health Benefits

Medical

Dental

Page 48 of 70


Vision

Page 49 of 70


6.2 Hire/Rehire/Termination Transactions

Hire/Rehire Transaction

o Perform Express Hire – ‘Hire’/’Rehire’ Transaction > Run ‘Hire Rehire’ Process

Hire transactionBenefit Program and job code depends on Position no.

Emplid: 3033526

o Verify if a row is inserted in Bas Activity table for ‘HIR’ transaction with Bas_Action as ‘DEF’

ReHire transaction

Page 50 of 70


Emplid: 1010199

o Verify if a row is inserted in Bas Activity table for ‘REH’ transaction with Bas_Action as ‘DEF’

o Run Benefits Pre Processor

Page 51 of 70


Verify the JobCI staging table. Appropriate rows with elig config9 values should be inserted

Elig Value

Run Job CI

Verify if appropriate row is entered in the Job Data page

Page 52 of 70


Emplid: 3033526

Emplid: 1010199

Page 53 of 70


o Check the Bas Activity table for new bas actions inserted

o Run Ben Admin to schedule the emplid > Click on ‘Schedule/Prepare Activity’

Page 54 of 70


We can either run through ‘Run Automated Event Processing’ or ‘On Demand Event Maintenance’

Usually, its more user-friendly to use ‘On Demand Event Maintenance’ while running for a single or few emplids

If there are multiple events, each has to be processed individually

Emplid: 3033526For Event Class ‘DEF’

For Event Class ‘SRE’

Emplid: 1010199For Event Class ‘DEF’


Page 55 of 70


For Event Class ‘PIP’

o Verify if the row still exists in Bas Activity Table. It should not.

o Check if a row is inserted in Bas Partic table

o Click on the ‘Election Entry’ button > It will display all the benefit plans which the associate is eligible to enroll

Page 56 of 70


o Make appropriate electionso Once saved, the process status is changed to ‘ET’o Click on the ‘Validate/Finalize’ button > Save the changeso Note that the event status is ‘Closed’ and Process Status is ‘FE’o Verify if appropriate row is inserted in the respective benefit table

Emplid: 3033526

For Event Class ‘DEF’

Page 57 of 70



Emplid: 1010199

For Event Class ‘PIP’

Page 58 of 70


For Event Class ‘DEF’

Page 59 of 70



Online Page

Page 60 of 70


Backend Table

Note: Overall process is after performing the hire/rehire transactions, Run Benefits Pre Processor > Job CI > Ben Admin to schedule > Perform election entries > Ben Admin to finalize the events. In this scenario, it is not required to run Default Processor. It is required to run this incase of event classes related to other Job Changes.

Termination Transaction

o Perform a termination transaction > Emplid: 1010178

Page 61 of 70


o Verify if a row is inserted in Bas Activity table for ‘TER’ transaction with Bas_Action as ‘TER’

o Run Ben Admin to schedule the emplid > Click on ‘Schedule/Prepare Activity’

o Verify if the row still exists in Bas Activity Table. It should not.

o Check if a row is inserted in Bas Partic table with process status as ‘PR’

Page 62 of 70


o Select the ‘Finalize/Apply Defaults’ > Click on the ‘Validate/Finalize’ button > Save the changes made

o Note that the event status is ‘Closed’ and Process Status is ‘FE’

o Verify if appropriate row is inserted in the benefit tables

Eg: Health Benefits Page

Page 63 of 70


6.3 Few Other Events to note

o ADR EventThis event is triggered when there is an address change to the employee record

o MSC EventThis event is triggered when there are job related changes like position change, transfer, pay rate change, promotion, step down etc

To look at the possible list of actions, we can query the ps_actn_reason_tbl for bas_action as ‘MSC’

o CLS EventThis event is triggered to delete the overage dependents from the benefits enrollment

We can refer to ps_dependent_benef, ps_dep_benef_vw1 for viewing dependant’s details

For all the above events, processes to be run are in this sequence: Ben Admin run (To Schedule) > Default Processor run (To validate and set the finalize flag to ‘Y’) > Ben Admin (To post the changes to benefit and payroll tables)

6.4 Transactions through Core Add dependants

Navigation: Benefits > Employee/Dependent Information > Update Dependent/Beneficiary

o Add a new row > Select ‘Relationship to Employee’ value, ‘Dep/Benef Type’ value > Name Details as shown in the below screen print

o Provide details in all other tabs > Click on save

o To verify the backend table

Page 64 of 70


o Enroll dependant to the existing benefit plan. Eg: ‘Life and ADD/D Benefits’

Existing enrolment to plan type 20

Add a row > Add the new dependant to the benefit plan > Save the changes

Page 65 of 70


To verify the backend table

Page 66 of 70


7 Reports

Here are the list of few benefits related interfaces/reports

Inbound interfaces

o ZITI415

Navigation: Release 4 Interfaces > Ceridian Commuter FSA Inbound

This interface covers processing of Commuter FSA enrollment/initiation file from Ceridian. This file contains enrollement records. This interface will read the data from the inbound file & insert it into the FSA Benefits Table

o ZITI807

Navigation: Release 3 Interfaces >Interfaces > ASRE Deferral Feedback

This interface reads the ASRE enrollment details from the inbound file. This data is required for making appropriate deductions from associate's paychecks

o ZITI808

Navigation: Release 4 interfaces > ASRE Loan Feedback

Loan feedback file is received from Fidelity on a weekly basis and the records are processed accordingly

o ZITI705

Navigation: North American Payroll > Payrol Processing > Albertsons Interfaces > CA-WAGE Lump Sum Update Process

This is an inbound interface that reads an inbound file and inserts data into the time load tables

Outbound interfaces

o ZITO414

Navigation: Release 4 interfaces > COBRA Interface to Telewire

The interface sends COBRA formatted information to Medsoft. Medsoft will use the data to mail COBRA notification letters.

o ZITO413

Navigation: Release 4 interfaces > COBRA Interface to Telewire

The interface sends HIPAA formatted information to Telewire. Telewire will use the data to mail HIPAA letters.

Page 67 of 70


o ZITO404

Navigation: Release 4 Interfaces > Initial Enrollment/Reinstatement

This interface is sent to the fulfillment vendor ADP, to send letters to associates on their eligibility and confirming benefit elections after enrollment

o ZITO419

Navigation: Release 4 Interface > Metlife Eligibility

This interface provides a listing of associates who are eligible for Metlife products

o ZITO410

Navigation: Release 4 Interface > FSA Interface to FH and Ceridian

The output file is to provide Enrollment and Termination information of the associates as required by First Health and Ceridian

o ZITO806

Navigation: Release 3 Interfaces>Interfaces>ASRE Monetary Process

This is the monetory file generated with details of ASRE contributions and loans

o ZITO810

Navigation: Release 4 Interface > ASRE Indicative Data

The interface sends ASRE eligibility data to vendor Fidelity which includes most current indicative information

o ZBEN0584

Navigation: Benefits > Reports > Custom Reports > Medical HMO Comparison Report

This report extracts all active employees enrolled in Medical Plan for a particular HMO. Run control parameter has an option to run either full or changes file

o BN_834_HIPAA

Navigation: Benefits > Interface with Providers > Create HIPAA EDI 834 File

HIPPA Process runs every Thursday of the week after the daily Ben Admin process.

It generates eligibility files in the EDI HIPAA834 format for various vendors like BCBS, FH, Delta Dental etc.The files contain benefit election information to notify of benefit elections and changes. It includes a full load of current benefit elections for the employee and dependent. This interface also includes benefit termination notification records to notify that an individual no longer has benefit coverage under the specified plan.

Note the following:

Page 68 of 70


If run manually, need to run Ben100A (Benefits > Interface with Providers > Refresh Benefit Snapshot before running Hipaa process. Hipaa process reads data from the PS_BN_SNAP_PLAN table and this table gets updated when Ben100A is run)

If run through ESP, need to follow this sequence: ZPAYSTM > Ben100a > Hipaa process To verify the vendor id setup for Hipaa run

Navigation: Setup HRMS > Product Related > Base Benefits > EDI Trading Partners

We can refer to the attached PDF file to understand and read the flat files generated

Page 69 of 70


8 AppendixAPPENDIX – A Glossary

Acronym ExpansionABS AlbertsonsDB DatabasePS PeopleSoftBen Admin Benefit AdministrationADR Record Associate Detail Record

APPENDIX – B Quick Navigations

Page NavigationBenefit Program Setup HRMS > Product Related > Base Benefits > Program Structure >

Benefit Program TableBenefit Plan Setup HRMS > Product Releated > Base Benefits > Plans and Providers >

Benefit Plan TableCoverage Code Setup HRMS > Product Related > Base Benefits > Plan Attributes > Health

Coverage CodesAll Rate Tables Setup HRMS > Product Related > Base Benefits > Rates and RulesCalculation Rules Setup HRMS > Product Related > Base Benefits > Rates and Rules >

Calculation Rules TableDeduction Table Setup HRMS > Product Related > North American Payroll > Deductions >

Deduction TableVarious Eligibility Rules definitions

Setup HRMS > Product Related > Automated Benefits > Eligibility and Event Rules

Associate Detail Record Benefits > Enroll in Benefits > Associate Detail Record

APPENDIX – C Table references

Query for TableBenefit Program ps_ben_defn_pgmBenefit Plan ps_benef_plan_tblDependant Info ps_dependent_benefBas Activity ps_bas_activityBas Partic ps_bas_particHealth Benefits ps_health_benefitLife and ADD/D Benefits ps_life_add_benSavings Plans ps_savings_planFSA Spending Accounts ps_fsa_benefitJob CI Staging Table ps_a_ca_jobci_stg

APPENDIX – D Review DetailsAlbertsons AssociateReview DateReview Comments

Page 70 of 70

Documents

Peoplesoft Benefits Documentation[