Peoplesoft Benefits Documentation (

TABLE OF CONTENTS
1 Introduction........................................................................................................................................................................2
PURPOSE...................................................................................................................................................................................2
REFERENCES..............................................................................................................................................................................2
STRUCTURE OF THE DOCUMENT....................................................................................................................................................2
2 System Overview................................................................................................................................................................3
3 Base Benefits Setups..........................................................................................................................................................4
4 Benefit Administration Setups........................................................................................................................................14
5 Benefits Pre Processor.....................................................................................................................................................36
6 Changes to EE data..........................................................................................................................................................40
6.1 Employee choosing benefits through ESS ................................................................................................................40
6.2 Hire/Rehire/Termination Transactions.....................................................................................................................51
6.3 Few Other Events to note..........................................................................................................................................65
6.4 Transactions through Core ......................................................................................................................................65
7 Reports..............................................................................................................................................................................68
8 Appendix...........................................................................................................................................................................71
APPENDIX – A GLOSSARY...................................................................................................................................................71
APPENDIX – B QUICK NAVIGATIONS.....................................................................................................................................71
APPENDIX – C TABLE REFERENCES.......................................................................................................................................71
APPENDIX – D REVIEW DETAILS..........................................................................................................................................71
Report Title Publication
PeopleSoft 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 Introduction
Chapter 2 System Overview
Chapter 3 Base Benefits Setups
Chapter 4 Benefit Administration Setups
Chapter 5 Benefits Pre Processor
Chapter 6 Changes to EE data, Processes to be run
Chapter 7 Reports
Chapter 8 Appendix
Page 2 of 71
2 System Overview
This diagram illustrates the interlinkages between Base Benefits and other PS
HRMS modules
PeopleSoft HRMS
Core HR Modules
Base Benefits Benefits Administration
Payroll Module
1. Employee data flows from Core HR tables to Benefits tables. Employee Benefit Program
details flow from Benefits tables to Core HR
2. Deductions for availing benefits are passed on to the payroll module. These will be
included while calculating employee’s pay
Page 3 of 71
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 Definition

Vendor/Provider ps_vendor Organization that provides or services a benefit offering.
Rate Tables ps_age_rate_tbl There are four types of rate tables: Age, Salary, Service,
ps_flat_rate_tbl and Flat. These tables are used to calculate the cost of a
ps_salary_rate_tbl benefit.
ps_svc_rate_tbl
Calculation ps_calc_rules_tbl Defines the rules for calculating benefit deductions, such
Rules 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 XLAT Values Any benefit category, such as health, life, or savings.
Type
Benefit Plan ps_benef_plan_tbl A specific benefit offering within a plan type. For example,
Basic Dental or Enhanced Dental
To 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.
Page 4 of 71
Pictorial representation of how the Benefit Plans and Employee data are linked
Employee’s Job
Data (assigned to
the benefit
program)
Benefit Program
Benefit Plan Type
Benefit Plan
Rates defined Calculation Rules
Only one benefit program  an Employee.
Sample Chosen :
Benefit Program : 132 (PT Chicagoland 881 Clerks)

Benefit Plan Type : 10 (Medical)
Benefit Plan : BPOS1B
Rate: 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 71
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 71
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
Page 7 of 71
Rate Table
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 defined

o 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 71
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 71
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 covered
2 Employee and Spouse covered
3 Employee and Dependants(Children) covered
4 Family coverage (Employee+Spouse+Children)covered
8 Employee and one child covered
Page 10 of 71
Plan Types
o These are two character, alphanumeric codes

o Stored in Translate Table
Category Numbering Sequence

Health 10 – 19, 1A – 1Z
Life and Accidental Death 20 – 29, 2A – 2Z
Disability 30 – 39, 3A – 3Z
Savings 40 – 49, 4A – 4Z
Leave 50 – 59, 5A – 5Z
Flexible Spending Accounts 60 – 69, 6A – 6Z
Retirement 70 – 79, 7A – 7Z
Pension 80 – 89, 8A– 8Z
Vacation 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 71
Page 12 of 71
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 71
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 Reference
Define 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 Building Automated Benefit Programs

programs.
For Canadian users, define Canadian (CAN) Handling Canadian Credit Allocations
credit allocation rules.
Note: Not covered in this documentation
Page 14 of 71
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 program
o 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)

o Plan Type Tab in the Benefit Program Definition Page
Page 15 of 71
o Eligibility ID’s are defined as below in the ‘Eligibility Rules’ definition page. Eg: ‘SB’ Elig ID
Page 16 of 71
Page 17 of 71
Eligibility Criteria fields
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 Name

Age Officer Code
Benefit Status Pay Group
Eligibility Config 1– 9 Regular and Temporary
EmplID Override Regulatory Region
Employee Class Retirement Plan (Federal)
Employee Type Salary Grade
FEHB Indicator Service Months
FLSA Status Standard Hours
FTE State
Full/Part Time Union Code
Location
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 Pass
within the postal range.
Lives within the postal range but works Pass
outside the postal range.
Lives outside the postal range but works Pass
within the postal range.
Lives outside the postal range and works Fail
outside the postal range.
Sample Chosen: (Example referred above)

o Plan Type Tab in the Benefit Program Definition Page
Page 18 of 71
o Geog Locn Eligibilities are defined as below in the ‘Geog Locn Elig Table’ definition page. Eg:
‘BCBS’ Geog Locn
Page 19 of 71
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
Page 20 of 71
action/reason combination enables the system to classify and track the events that cause
changes to employees’ employment and benefit coverage status.
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)
Page 21 of 71
Event Rules Table. Eg: ‘Dental’ Event Rules ID for ‘ADR’ Event Class
Date Rules Tab - Defining Start and End Dates for Coverage, Deductions, and Flex Credits
Page 22 of 71
Define Trigger Events
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 71
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
Page 24 of 71
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.
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 enrollment

o
o 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
Page 25 of 71
o Use snapshot if you are going for event maintenance and not for Open Enrollment.
Snapshot definition : used by employee for online election.
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
Page 26 of 71
Open Enrollment Scehdule Id
Ben Admin Run Control Page
Navigation: Benefits > Manage Automated Enrollment > Events > Run Automated Event
Processing
‘Schedule and Chkpt Restart’ Tab
Page 27 of 71
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
Page 28 of 71
o These will be enabled when Schedule ID selected in the first tab is for OE/Snapshot
o 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.
‘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 Participant event is The system cannot process the participant event through
Eligibility Assigned assigned to multiple the next stage (Option Preparation) until the errors are
Error programs. 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 Participant event is not During the Option Election phase of the process, the system
Eligibility Assigned assigned to a benefit determines if the AN participant associated with the event
None program. 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
Page 29 of 71
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 Participant event is The event continues on to a process status of FP (Finalized -
Eligibility Assigned assigned to a benefit Prepared None), PE (Prepare Error), or PR, depending on
program. the associated participant's eligibility for benefit options.
FA - Finalized - Participant event has no There is no further processing for this event. The online
Benefit Program program assignment page description for this process status (on the Schedule
None and no current Summary page, for example) is Program None.
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.
FP - Finalized - System has assigned No further processing occurs for this participant event. The
Prepared None the participant event to online page description for this process status (on the
a benefit program, but Schedule Summary page, for example) is Prepare None.
the associated
participant is not
allowed to elect any
new options.
PE - Prepare Error The system has To correct, make corrections to the
encountered an error. personal/employment/job information of the associated
Events are given a PE participant or to plan and option eligibility information. Each
process status during time Ben Admin in run, the system reevaluates PE events.
option eligibility
determination or
calculation of credits.
PR - Prepared The system has > For PE or AS events, processing stops. Enrollment forms
calculated eligible should be created for and delivered to the participant
options, credits, rates. associated with the event to bring the event to a process
AN events that have status of NT (notified).
current elections can > For AN events, processing also stops. Review the event (a
also be brought to a pending termination of benefits), confirm it by marking it for
status of PR. 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 Participants need to complete their election forms and
form has been return them to the HR/Benefits department. When the
distributed to the elections are entered into the system with the data entry
participant associated pages, the system will advance the events to an ET
with the event. The (entered) process status.
system updates the
event's process status
to NT when election
forms are generated for
that participant via
report BAS004.
Participants can only
Page 30 of 71
advance to NT if their
previous process status
was PR.
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 31 of 71
AS – Assigned
Employee is AN – Assigned None
assigned to a Employee is assigned
Benefit Program to no benefit program
No
FP – Finalized No FA – Finalized –
Is Employee able Prepared None Does the employee Benefit Program
to change options? No additional have current None
processing occurs elections? No additional
processing occurs
Yes
Yes
No
PE – Prepared Error PR – Prepared
Are eligible options No elections are
Error in Option
calculated correctly ? allowed
Preparation
Yes Use Update Event

Status panel to
Make Corrections, review event and
Rerun Ben Admin check the ‘final’ flag
PR - Prepared
Process
Run Ben Admin

Process
Print Enrollment
Forms
FE – Finalized –
Enrolled
No additional
processing occurs
NT - Notified
On to Election
Validation and
Loading Stage of
Second Ben Admin
Run
Page 32 of 71
Entering, Validating and Loading Elections
Process Status Description Next Processing Steps
ET - Entered A benefits administrator > If there are no errors with the elections, the elections are posted
(or the employee via PS to the appropriate benefit and payroll tables and the system
eBenefits) has entered the updates the process status to FE.
participant's new elections > If there are errors, the status becomes EE.
into the system, and they > If we run the Ben Admin process with Finalize selected, EE
are ready for validation by participant events are brought to FE status, and the system goes
Ben Admin process. through the normal validation. If any of the employee's choices are
Participant events with a invalid, event rules are to be refered to determine whether current
process status of ET can elections or defaults should be loaded.
have a prior process status
of PR, NT, or RE
(Reentered).
EE - Election Error The system encountered No further processing occurs for this participant event. We need to
an error in processing the correct the errors by reentering employee elections and run the Ben
elections for the Admin process again.
participant associated with Alternatively, we can "force finalize" this participant event to
the event. No elections are finalize it with errors. The system loads the default values for the
posted to the Base associated participant's erroneous benefit option elections. If a
Benefits business process dependent/beneficiary or investment choice is in error, the system
tables. loads the employee's option choice but does not load the
Errors are posted to the dependent/beneficiary or investment choice.
Message Table and are We can generate confirmation statements for participants whose
identified by participant events have an EE process status; the form indicates the plan
and event. information in error along with the valid plan choices.
The previous process
status was either ET or EE.
FE - Finalized - Ben Admin processing is We need to generate and deliver a confirmation form to the
Enrolled complete for the participant associated with the event.
participant event. All To change a participant's elections after they've been finalized (for
elections have been example, if a participant wants to correct information on the
validated and loaded to the confirmation statement), we can reprocess them by giving the
appropriate Base Benefits associated event a process status of RE (re-entered) in the Event
business process and Status Update page and rerunning the Ben Admin process.
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.
RE – Re-Entered Enables elections After we update the elections in the data entry pages, the system
associated with processing updates the process status from RE to ET.
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
Page 33 of 71
A quick look at the flow of the above process statuses
NT - Notified
Elections entered /
Re entered in data
entry panels
ET – Notified
Elections were entered .
No Ben Admin run prior
to this status
Run Ben Admin

Process
Re re Entered
Re entered participant
elections
No
Were elections EE – Election
entered correctly ? Error
No
Do you want to
Yes force finalize ?
Yes
FE – Finalized
Enrolled Run Ben Admin
No additional process . Turn Finalize
processing occurs on
Finalized event’s process

indicator updated to Re -
Run Ben Admin
enter on Processing
process
Controls update or Event
status update
Ben Admin Process Results
Navigation: Benefits > Manage Automated Enrollment > Review Processing Results
o Using this, we can
Page 34 of 71
 Review error messages.

 Review process results for schedules.
 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 35 of 71
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) record
4. 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 36 of 71
A JOBCI A
Job Data
Eligibility L (Row inserted L
(Job CI
Processor B with B
inserts a row
(Identifies the C corresponding J
into the
Eligible H Elig Config O
Employee
associates) W values in this B
job data)
01 staging table) CI
Associate Detail
Record
(Inserts a row for
each benefit Type for
tracking the
Eligibility)
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 Benefit
2. 20(VMD) – Voluntary Medical/Dental
3. 30(Single) – Eligible for Single benefit
4. 40(Family) – Eligible for Family Medical/Dental plan
5. 45(Requal) – Re-qualification of medical/dental Benefit
6. 50(PIP) – Pension Investment Plan
7. 60(401K) – ASRE plan
8. 70(Catch-up) – ASRE Catch-up plan
9. 80(Makeup) – ASRE Makeup Plan
10. 90(2DC) – 2DC plan
11. 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 37 of 71
For each CB Type, required rules are defined here
Page 38 of 71
When we click on ‘Method Items’ hyperlink, we get to view the components of each rule type
Page 39 of 71
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
Page 40 of 71
Dental
Vision
Page 41 of 71
Coverage begin date = event date

Election 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 42 of 71
Page 43 of 71
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 well

o Selected option appears in the benefits summary page
Page 44 of 71
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 45 of 71
Final confirmation page
Page 46 of 71
‘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 47 of 71
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 48 of 71
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 49 of 71
Vision
Page 50 of 71
6.2 Hire/Rehire/Termination Transactions
Hire/Rehire Transaction
o Perform Express Hire – ‘Hire’/’Rehire’ Transaction > Run ‘Hire Rehire’ Process
Hire transaction
Benefit 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 51 of 71
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 52 of 71
Verify the JobCI staging table. Appropriate rows with elig config9 values should be inserted
Elig Value
Run Job CI
Page 53 of 71
Verify if appropriate row is entered in the Job Data page
Emplid: 3033526
Emplid: 1010199
Page 54 of 71
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 55 of 71
 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: 3033526
For Event Class ‘DEF’
For Event Class ‘SRE’
Emplid: 1010199
Page 56 of 71
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
Page 57 of 71
o Click on the ‘Election Entry’ button > It will display all the benefit plans which the associate is
eligible to enroll
o Make appropriate elections
o Once saved, the process status is changed to ‘ET’
o Click on the ‘Validate/Finalize’ button > Save the changes
o 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
Page 58 of 71
Emplid: 1010199
For Event Class ‘PIP’
Page 59 of 71
Page 60 of 71
Online Page
Page 61 of 71
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 62 of 71
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 63 of 71
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 64 of 71
6.3 Few Other Events to note
o ADR Event
This event is triggered when there is an address change to the employee record
o MSC Event
This 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 Event
This 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
Page 65 of 71
o To verify the backend table
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 66 of 71
To verify the backend table
Page 67 of 71
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
Page 68 of 71
The interface sends HIPAA formatted information to Telewire. Telewire will use the
data to mail HIPAA letters.
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.
Page 69 of 71
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:
 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
Hipaa 834
Layout.pdf
Page 70 of 71
8 Appendix
APPENDIX – A Glossary
Acronym Expansion
ABS Albertsons
DB Database
PS PeopleSoft
Ben Admin Benefit Administration
ADR Record Associate Detail Record
APPENDIX – B Quick Navigations
Page Navigation
Benefit Program Setup HRMS > Product Related > Base Benefits > Program Structure
> Benefit Program Table
Benefit Plan Setup HRMS > Product Releated > Base Benefits > Plans and Providers >
Benefit Plan Table
Coverage Code Setup HRMS > Product Related > Base Benefits > Plan Attributes > Health
Coverage Codes
All Rate Tables Setup HRMS > Product Related > Base Benefits > Rates and Rules
Calculation Rules Setup HRMS > Product Related > Base Benefits > Rates and Rules >
Calculation Rules Table
Deduction Table Setup HRMS > Product Related > North American Payroll > Deductions >
Deduction Table
Various Eligibility Rules Setup HRMS > Product Related > Automated Benefits > Eligibility and
definitions Event Rules
Associate Detail Record Benefits > Enroll in Benefits > Associate Detail Record
APPENDIX – C Table references
Query for Table

Benefit Program ps_ben_defn_pgm
Benefit Plan ps_benef_plan_tbl
Dependant Info ps_dependent_benef
Bas Activity ps_bas_activity
Bas Partic ps_bas_partic
Health Benefits ps_health_benefit
Life and ADD/D Benefits ps_life_add_ben
Savings Plans ps_savings_plan
FSA Spending Accounts ps_fsa_benefit
Job CI Staging Table ps_a_ca_jobci_stg
APPENDIX – D Review Details

Albertsons Associate
Review Date
Review Comments
Page 71 of 71

Peoplesoft Benefits Documentation (

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Peoplesoft Benefits Documentation (

Caricato da

Copyright:

Formati disponibili

TABLE OF CONTENTS

3 Base Benefits Setups..........................................................................................................................................................4

4 Benefit Administration Setups........................................................................................................................................14

5 Benefits Pre Processor.....................................................................................................................................................36

Structure of the Document

Base Benefits Benefits Administration

3 Base Benefits Setups

Table PS Table name Definition

Benefit Plan Type

Rates defined Calculation Rules

Only one benefit program  an Employee.

Benefit Program : 132 (PT Chicagoland 881 Clerks)

Same program can be assigned to more than one employees.

Benefit Plan Table

o The cost of benefits chosen is calculated based on the rates defined

Calculation Rules table

o Define the rules for calculating the benefits deductions

Eg: Benefit Program 132, plan type 20

Calc Rule definition page

Few other setups to note

Coverage Code Table

Most commonly used Coverage Codes and their description

Coverage Code Description

o These are two character, alphanumeric codes

Category Numbering Sequence

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

4 Benefit Administration Setups

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

Navigation: Setup HRMS -> Install -> Installation Table

Other setups required are listed below

Build your automated benefit Building Automated Benefit Programs

Define Eligibility Rules

o To determine the benefit program for which each employee is eligible

Sample Chosen: (Example referred above)

Benefit Program : 132 (PT Chicagoland 881 Clerks)

o Plan Type Tab in the Benefit Program Definition Page

Eligibility Criteria fields

Field Name Field Name

Define Geographic Location Eligibility Rules

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

If the employee The employee

Sample Chosen: (Example referred above)

Benefit Program : 132 (PT Chicagoland 881 Clerks)

o Plan Type Tab in the Benefit Program Definition Page

Define Event Rules

To set up event rules:

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

Define Trigger Events

1. Manually insert events into the BAS Activity Table

2. Define passive events

o Define events that are not initiated by data entry.

3. Automatically trigger events through employee data changes

Build the foundation by setting up Base Benefit information:

Build the Automated Benefits program:

Setups for Open Enrollment and Event Maintenance

Define Open Enrollment Ids

o Set up the parameters of the open enrollment

Establishing Process Schedular for running Ben Admin Process

Event Maintenance Schedule Id

Open Enrollment Scehdule Id

Ben Admin Run Control Page