CHRS Knowledge Base

Benefits Daily Review and Troubleshooting Process Guide

Updated on

CHRS logo
Revision Date Revised By Summary of Revisions Section(s) Revised
08/11/21 Sande Meith Initial draft All
08/08/22 Sande Meith Updated for PTools 8.59 All
11/30/22 Sande Meith Added Why Did a Benefit Terminate or Isn’t Correct Troubleshooting Checklist 10

Review / Approval History

Review Date Reviewed By Action (Reviewed, Recommended or Approved)
Click here to enter Review Date Click here to enter Reviewer Click here to enter Reviewed, Recommended or Approved
Table of Contents

1.0  Process Overview 

6.0  CSU Process Status Report
6.1  Description       
6.2 Criteria
6.3 Recommended Use and Follow-up
6.4 Things to Look For
6.5 Navigation
6.6 Sample Report
6.7  Process Statuses           
8.0 CSU Benefits Termination Report
8.1  Description 
8.2  Criteria
8.3  Recommend Use and Follow-up
8.4  Navigation
8.5  Sample Report


2.0   Related Documentation             Program Assignment   9.0 CSU Job Change Prior to Ben Admin
9.1  Description       
9.2  Criteria 
9.3  Recommended Use for Follow-Up         
9.4  Navigation         
9.5  Sample Report
3.0  Daily Benefits Review - Job Aids      Prepare Options 10.0  Why Did a Benefit Terminate or Isn’t Correct Troubleshooting Checklist   
4.0  Invalid Elections Report
4.1  Report Description    
4.2 Recommended Use and Follow-up 
4.3 Things to Look For 
4.4 Online Processing Messages Page 
4.5 Navigation
Entering Elections      11.0  Appendix A – Ben Admin Error Messages    
5.0  Report on Flagged Items
5.1 Report Description
5.2 Recommended Use and Follow-up
5.3 Things to Look For 
5.4 Navigation 
5.5 Sample Report 
7.0  Benefits Transaction Report              
7.1  Description       
7.2 Criteria
7.3 Recommended Use and Follow-up
7.4 Navigation
7.5  Sample Report

1.0 Process Overview

The CHRS Daily Review and Troubleshooting User Guide details daily processing tasks for Campus Benefits Officers, which includes reviewing daily and nightly Benefits Administration (Ben Admin) CSUBAS process logs, reviewing delivered and custom processing reports, identifying and resolving issues or facilitate resolving issues, and running CHRS Baseline Benefits queries ad-hoc to manage eBenefits self-service processing and identifying employees with missing data.

This guide also provides information for resolving problems on certain reports. The reports in this document provide detailed and summary information about the nightly Benefits Administration processing outcome.

This document provides the following for each report; a report description, report selection criteria, use instruction, navigation, output sample, and, for some reports, examples of use scenarios specific to the report for reviewing and/or resolving issues. The reports are listed in the recommended order of review based on campus input.

Although every possible scenario is not listed, this guide provides examples of common situations to look for while troubleshooting and recommendations for handling the errors encountered. The Benefits Officer responsible for reviewing the reports should conduct a thorough review each time Ben Admin is processed.

Use the troubleshooting checklists in this guide to help review and resolve issues.

In addition to this business process guide, the following CMS-CHRS documents should be referenced and reviewed daily and/or as needed:

  • Daily Review CSUBAS Logs and Reports
  • Daily Review BA Baseline Queries
  • Event Class Cheat Sheet
  • Reprocessing a CHRS Event Cheat Sheet
  • eBenefits OK to Reprocess Cheat Sheet
  • CHRS Benefits Audit Table User Guide
  • CHRS Benefits Manual Events and Election Entry Business Process Guide
  • CHRS Benefits Employee Self Service Business Process Guide
  • Action Reason with PIMS Mapping
  • PSR Error Clean Up Position Paper
  • Benefits Event Troubleshooting Position Paper

3.0 Daily Benefits Review - Job Aids

The following job aids show Benefits Officers what and how to review daily campus-specific CSUBAS logs from the nightly Ben Admin processing, daily CHRS baseline queries and daily campus specific reports.

Use the information listed in this document if you require more details on what to review on the daily reports and how to resolve issues found on the daily reports.

4.0 BAS003.SQR - Invalid Elections Report

Report Description

BAS003.SQR - Invalid Elections Report is a PeopleSoft delivered report which produces, by BAS Schedule ID, a detailed listing of all Ben Admin error and warning situations resulting from running the Benefits Administration process (PSPBARUN). This report lists the schedule ID, the Emplid, the error message description, and the cause of the error. Review all errors/warnings and resolve daily.

Review and resolve issues that are on this report daily. Note that resolved issues on the report will not drop off the report until PSPBARUN (the delivered Ben Admin process) runs again for the applicable BAS Schedule ID.

Things to Look For

  • Assign None (AN) errors occur when the system Ben Admin configuration is not configured to determine the employee’s benefit program. Theoretically, there should never be BAS events with the Assign None (AN) process status.
    • To resolve BAS events with the Assign None (AN) process status, review the employee’s Job Data record(s) to verify that all Job Data values are correct. If you find incorrect Job Data values, have the incorrect values corrected and then go to the On Demand Event Maintenance page, enter the value of A in the field to the right of the Reprocess button, then click on the Reprocess button to re-prepare the election options. If this does not resolve the issue, you may need to submit a Service Now ticket for CMS to review.
    • Note that Assign None (AN) BAS events become Finalized None (FN) process status after the next delivered Ben Admin run (PSPBARUN).
  • To resolve Assign Errors (AE), determine if incorrect Job Data values require correction. If there are no incorrect Job Data values for the employee, there may be a configuration issue that requires research and resolution. Once the incorrect Job Data value is corrected and/or the configuration issue is corrected:
    • If the Assign Error is not for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, enter the value of A in the field to the right of the Reprocess button, then click on the Reprocess button to re-prepare the election options.
    • If the Assign Error is for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, enter the value of A in the field to the right of the Reprocess button, then click on the Reprocess button to re-prepare the election options. Verify that the BAS event is at a Process Status of Prepared. Then advise the employee that they can continue with their life event transaction. If the employee cannot access the corrected BAS event, ask the employee to Cancel their life event transaction in eBenefits and create a new life event transaction.
  • To resolve Prep Errors (PE), determine if incorrect Job Data values require correction. If there are no incorrect Job Data values for the employee, there may be a configuration issue that requires research and resolution. Once the incorrect Job Data value is corrected and/or the configuration issue is corrected:
    • If the Prep Error is not for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, enter the value of A in the field to the right of the Reprocess button, then click on the Reprocess button to re-prepare the election options.
    • If the Prep Error is for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, enter the value of A in the field to the right of the Reprocess button, then click on the Reprocess button to re-prepare the election options. Verify that the BAS event is at a Process Status of Prepared. Then advise the employee that they can continue with their life event transaction. If the employee cannot access the corrected BAS event, ask the employee to Cancel their life event transaction in eBenefits and create a new life event transaction.
  • To resolve Election Errors (EE) first determine what needs to be corrected for the related data entry.
    • If the Election Error is not for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, click on the Election Entry button and correct the election error. Verify that the correct permitting event codes are entered. Save the transaction.
    • If the Election Error is for an eBenefits Self Service transaction, go to the On Demand Event Maintenance page, click on the Election Entry button and correct the election error. You’ll then need to enter the permitting event codes for the BAS event.
      • Do not reprocess the eBenefits Self Service BAS event to a Process Status prior to Re-enter, i.e., do not reprocess to Assign Benefit Program or Prepare Options as you'll lose the employee's submission date (Election Received Date). Election Received Date is used for the eSignature date on forms, the Perm Event HBO Received Date, and is used by the nightly process CSU_BA_EVT_DT to change the event class event date for submission date processing. Refer to the eBenefits OK to Reprocess Cheat Sheet for more information.
  • There is no need to set anything on the Event Status Update page to resolve the above errors unless the AN error went to a FN error and you are reprocessing the BAS event back to an Assign Process Status in order to resolve.
  • This report does not show details for error messages that correspond to disconnected events.

Appendix A lists error messages that may appear on the report with the error message meaning and suggested resolutions. Refer to Appendix A if needed.

Online Processing Messages Page

The BAS003 report information can also be viewed online in CHRS via the Processing Messages page. Messages on this page are not cleared once resolved but instead are cleared once Ben Admin runs again for the applicable Schedule ID.

Navigation: Benefits > Manage Automated Enrollment > Review Processing Results > Processing Messages

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

Navigation icon

then go to Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Invalid Elections Rpt

Example of Run Control Page

Example of Run Control Page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
1.he Invalid Elections Rpt page appears.
  1. The Invalid Elections Rpt page appears.
1.he Invalid Elections Rpt page appears.
  1. Enter the Schedule ID. Do not leave this field blank.
  2. Click on the Run button.
  3. The Process Scheduler Request page appears.
process scheduler request
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the BAS003 process is selected (i.e., check marked), then click on the OK button.
  3. The Invalid Elections Rpt page appears, along with the Process Instance number. Write down this number in case you need it later.
  4. Click on the Process Monitor link to monitor the status of the report generation.
  5. The Process List page appears.
process list
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
process detail
  1. The Process Detail page appears. Click on the View Log/Trace link.
  2. The View Log/Trace page appears. Click on the link that ends in .PDF as this is the report.
vie and log trace page

Sample Report

example of report

BAS008.SQR - Report on Flagged Items

Report Description

The Report on Flagged Items is a report that lists flagged BAS events that require daily review and resolution. Flagged BAS events listed on the report:

  1. have had Job, Address, or Union eligibility information changes that may impact benefits eligibility and warrant BAS event class review and possible reprocessing.
  2. have been processed Out of Sequence and warrant BAS event class reprocessing or voiding based on the BAS event that’s out of sequence.
  3. have been disconnected during processing and require review and resolution.

BAS008.SQR - Report on Flagged Items is a PeopleSoft delivered report which produces, by BAS Schedule ID, a detailed listing of all Ben Admin BAS events that have one of more of the BAS flags enabled:

  • Address Eligibility Changed
  • MultiJob Indicator Changed
  • Job Eligibility Changed
  • Event Out of Sequence
  • Event Disconnected

This report lists the schedule ID, the Emplid, the error message description, and the cause of the error. Review and resolve all items on the report.

Review and resolve issues that are on this report daily.

  • Audit the flags and re-process BAS events as needed.
    • Use the Reprocessing a CHRS BAS Event cheat sheet every time you need to reprocess a BAS event in CHRS.
    • Also use the eBenefits ESS OK to Reprocess Cheat Sheet every time you are trying to clear a flag for an eBenefits ESS event, as you may not be able to reprocess the eBenefits ESS event. The eBenefits ESS OK to Reprocess Cheat Sheet advises when it is ok to reprocess an eBenefits ESS BAS event based on the BAS event Process Status. The Reprocessing a CHRS BAS Event cheat sheet provides the next steps to take when the scenario dictates that you cannot reprocess a particular BAS event.
  • If the Address Eligibility Change flag is checked, go to Modify a Person and see if the employee’s home state and/or home zip code changed, then go to Job Data and review the Job Data rows equal to and prior to the reprocess BAS event date to see if the employee’s work location changed that resulted in a zip code or state change. Note that mailing addresses do not impact benefit eligibility.
    • If the home or work location address change did not include a zip code or state change, you can uncheck the Address Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
    • If the home or work location address zip code or state changed, you must reprocess the BAS event to see if the employee’s benefit eligibility changed. The employee may need to or have the option to elect a new benefit plan for certain zip code eligibility changes.
      • Before you reprocess any BAS event in CHRS, refer to the Reprocessing a CHRS BAS Event and the eBenefits ESS OK to Reprocess Cheat Sheet to see if it’s OK to reprocess that particular BAS event. The Reprocessing a CHRS BAS Event cheat sheet provides the next steps to take when the scenario dictates that you cannot reprocess a particular BAS event.
  • If the Job Eligibility Change flag is checked, go to Job Data and review the following fields on the Job Data rows equal to and prior to the reprocess BAS event date to see if changes occurred that would impact the employee’s benefits: Location, Empl_Class, Employee Type, FLSA Status, Salary Plan, Grade, Full/Part Time, Regular/Temporary, Service Months, Standard Hours, Union Code, Pay Group, Officer Code, FTE, Combined FTE, ACA Eligibility Status, Elig Feld 1, Elig Fld 2, Elig Fld 3, Elig Fld 4, Elig Fld 5, Elig Fld 6, Elig Fld 7, Elig Fld 8 and Elig Fld 9. Also check to see if the BAS Group ID changed. The BAS Group ID value is critical for OE BAS events.
    • If the Job Data change did not update a field that would impact the employee’s benefits eligibility, you can uncheck the Job Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
    • If the Job Data change did update a field that would impact the employee’s benefits eligibility, you must reprocess the BAS event to see if the employee’s benefit eligibility changed.
      • Before you reprocess any BAS event in CHRS, refer to the Reprocessing a CHRS BAS Event and the eBenefits ESS OK to Reprocess Cheat Sheet to see if it’s OK to reprocess that particular BAS event. The Reprocessing a CHRS BAS Event cheat sheet provides the next steps to take when the scenario dictates that you cannot reprocess a particular BAS event.
  • If the MultiJob Eligibility Change flag is checked, go to Job Data and review the following fields for all active jobs for the employee on Job Data rows equal to and prior to the reprocess BAS event date to see if changes occurred that would impact the employee’s benefits: Location, Empl_Class, Employee Type, FLSA Status, Salary Plan, Grade, Full/Part Time, Regular/Temporary, Service Months, Standard Hours, Union Code, Pay Group, Officer Code, FTE, Combined FTE, ACA Eligibility Status, Elig Fld 1, Elig Fld 2, Elig Fld 3, Elig Fld 4, Elig Fld 5, Elig Fld 6, Elig Fld 7, Elig Fld 8 and Elig Fld 9. Also check to see if BAS Group ID changed or needs to change for the employee’s Primary Benefit Job. The BAS Group ID value is critical for OE BAS events.
    • If the Job Data change did not update a field that would impact the employee’s benefits, you can uncheck the Job Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
    • If the Job Data change did update a field that would impact the employee’s benefits eligibility, you must reprocess the BAS event to see if the employee’s benefit eligibility changed.
      • Before you reprocess any BAS event in CHRS, refer to the Reprocessing a CHRS BAS Event and the eBenefits ESS OK to Reprocess Cheat Sheet to see if it’s OK to reprocess that particular BAS event. The Reprocessing a CHRS BAS Event cheat sheet provides the next steps to take when the scenario dictates that you cannot reprocess a particular BAS event.

Things to Look For

  • Address Eligibility Changed Flag – This flag will be checked if there is a change in address that affects the job row. If there is a 9/1/2003 event created from a Job row, and there is an 8/15/2003 change of address entered, the Address Eligibility Changed flag will appear on the 9/1/2003 event in Event Status Update and on this report. The existing event may need to be reprocessed if the address change affects Benefits eligibility.
  • MultiJob Indicator Changed Flag – This flag will be checked if Multiple Jobs functionality is being used and information affecting eligibility was changed, inserted, or deleted after the event had begun processing. The event may need to be reprocessed if the change made affects more than one of the employee’s jobs.
  • Job Eligibility Changed Flag – This flag will be checked if there is a correction to an existing Job row where one of the fields listed below is changed. The existing event may need to be reprocessed if the Job change affects Benefits eligibility.
  • Event Disconnected Flag – Disconnected events represent a broken BAS event. This means information that the system used to track and/or process the BAS event was deleted or changed after the BAS event was created. If a BAS event is disconnected, it can no longer be processed by the Ben Admin system, except to be voided*. There are two ways a BAS event can become disconnected:
    • The HR record that previously triggered the event changes. For example, the Job Data row Effective Date was changed, or the Action code was changed, or the Action/Reason code was changed.
    • The Job Data row was deleted.
    • Disconnected BAS events need to be analyzed one by one to determine the impact on benefit processing. If a BAS event is disconnected after it is finalized, first void the event through reprocessing. Be aware that voiding the BAS event for finalized-enrolled benefit elections may not roll back elections from the Base Benefits tables. In this case, Correction mode is required to remove the finalized-enrolled benefit elections from the applicable Base Benefits tables.
    • When the effective date of a particular address or Job Data row is corrected, the system simultaneously creates a new BAS event and disconnects any BAS events that were initially triggered by the address or job record change.
    • *Note: If a disconnected event has an Event Status of Closed and the Event Status box is greyed out, the BAS event cannot be reprocessed. This also means that the finalized disconnected event cannot be reprocessed to a status of Void.
  • Event Out of Sequence Flag – This flag will be checked on events that were processed out of order. This happens when a participant event is in process within Benefits Administration and then another event associated with the same participant is triggered with an event date that precedes the first event. The system closes the first event and opens/processes the second event because Benefits Administration will only process one event per participant at a time.
    • An example Out of Sequence scenario is the employee has a future-dated OE BAS event in a Prepared status, and then creates a BIR Life Event to add their newborn child with an event date that precedes the OE event date. In this example, after the BIR event is finalized, the OE event requires reprocessing to pick up the newly added dependent and benefit plan changes.

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

report on flagged items page

then go to Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Report on Flagged Items

Example of Run Control Page

report on flagged items page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
report on flagged items page
  1. The Report On Flagged Items page appears.
report on flagged items page
  1. Verify that the Language is English.
  2. Enter the Schedule ID. Do not leave this field blank.
  3. Enter a From Date and Thru Date range.
  4. Select the flags to include on the report in the Report Participants Flagged for section, and then click on the Run button.
  5. The Process Scheduler Request page appears.
process scheduler request page
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the BAS008 process is selected (i.e., check marked), then click on the OK button.
  3. The Report On Flagged Items page appears, along with the Process Instance number. Write down this number in case you need it later.
  4. Click on the Process Monitor link to monitor the status of the report generation.
  5. The Process List page appears.
process list page
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
process detail page
  1. The Process Detail page appears. Click on the View Log/Trace link.
  2. The View Log/Trace page appears. Click on the link that ends in .PDF as this is the report.
view log and trace page

Sample Report

image of Sample Report

CSUBAS27.SQR – CSU Process Status Report

Description

This report includes a listing of all open BAS events for a particular BAS Schedule ID. This SQR was cloned from the delivered BAS27.sqr and customized to exclude events in Void, Closed, or Disconnected statuses.

Criteria

This report selects all participants in a particular process status or set of status levels. It does not display the transaction if:

  • Process Indicator is Void and Event Status is Closed

OR

  • Event Status is Closed, Disconnected or Void.

Use to monitor BAS processing.

Identify BAS events that are not moving forward and finalizing in a timely manner.

Remember that eBenefits ESS BAS events automatically expire after 1, 30 or 60 days based on the eBenefits BAS Event.

  • For eBenefits ESS BAS events also use the CSU_BAS_SS_EVENTS and CSU_BAS_SS_NT queries (these queries are also discussed on the Daily Review BA Baseline Queries job aid).

Note that some eBenefits BAS events require reaching out the employee to move the process along.

Things to Look For

  • Open events with an Election Error (EE) or Prep Error (PE) Benefits Administration Processing Status - These events are in an error status and should also appear on the BAS003 report.
  • Open events with an Assigned (AS) Benefits Administration Processing Status - These events are fine and occur because an event was started while another event for the employee was still in process. When this happens, the new event closes when it gets to Assigned (i.e., the benefit program was assigned) and waits there until the current event finishes processing. It will then “open up” for processing.

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

,then go to Menu > Benefits > Reports > CSU Benefits Reports > CSU Process Status Rpt

Example of Run Control Page

csu process status report page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
csu process status report page
  1. The CSU Process Status Rpt page appears.
csu process status report time
  1. Verify that the Language is English.
  2. Enter the Schedule ID. Do not leave this field blank.
  3. Select the Process Statuses to include on the report in the Process Status to Include section. and then click on the Run button.
  4. The Process Scheduler Request page appears.
process scheduler request page
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the CSUBAS27 process is selected (i.e., check marked), then click on the OK button.
  3. The CSU Process Status Rpt page appears, along with the Process Instance number. Write down this number in case you need it later.
  4. Click on the Process Monitor link to monitor the status of the report generation.
  5. The Process List page appears.
process list page
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
process detail page
  1. The View Log/Trace page appears. Click on the link that ends in .PDF as this is the report.
view log and trace page

Sample Report

image of Sample Report

Process Statuses

As Ben Admin executes, various process statuses are assigned. After the events are assigned to a schedule and the open event is identified, the system uses Eligibility Rules to assign the employee to a Benefit Program. Typically, an event will move through Program Assignment, and continue through prepare options and then be finalized. Events will receive different process statuses along the way.

The following are Process Status descriptions for the process status values that may be assigned and the steps to enable the event to continue through the process toward finalization.

Program Assignment

Process Status
Description

Troubleshooting Steps

Next Processing Steps

AS - Program Eligibility Assigned
BAS event is assigned to a benefit program. – Process Successful Typically, events don’t stay in an AS status for long as they generally move right along to the next process status. However, if you see an event at the AS process status after CSUBAS processing, it means that the employee has another BAS event being processed. The event will stay in AS status until the open event has finalized. Once able, the event continues in Ben Admin processing to the prepare options step.
AN - Program Eligibility Assigned None BAS event is not assigned to a benefit program. You should not see events in a status of AN. Run the Eligible Participants Report to evaluate employees who are eligible but not being assigned to a program. Events with an AN status will continue on through the process and end at a finalized – Assigned None (FA) status. All employees should receive a benefit program assignment.
AE - Program Eligibility Assigned Error BAS event is assigned to multiple programs. Employee is eligible for more than one Benefit Program. You'll most likely need to make corrections to participant personal, employment or job information or to program eligibility information. Evaluate Job Data for cross bargaining unit instances. If the employee is qualified for more than one benefit program, EmplID override is necessary. The system cannot process the BAS event through the next stage (Option Preparation) until you correct the errors. Each time you run Benefits Administration, the system will reevaluate events with an AE designation and (try to) move them along in the process.

Prepare Options

Process Status
Description

Troubleshooting Steps

Next Processing Steps

PR - Prepared
The system has determined eligible benefit plan options for the participant associated with the event. Event requires Election Entry or finalization. The batch process will force finalize prepared events so that default benefits can be written to base benefits (for example, the HIR BAS event is customized to finalize and enroll the employee into Life, Vision, and LTD if applicable). The system will bring the event to a process status of FE (Finalized - Enrolled)
The BAS event remains at the PR status until benefit elections are entered or, in the case of eBenefits ESS BAS events, expires.
FA - Finalized - Benefit Program None BAS event has no program assignment and no current elections. Benefit Program assignment should occur for all employees. Program eligibility should be reviewed.
PeopleBooks suggests running the eligibility reports to determine eligibility issues for this status.
There is no further processing for this event, other than reprocessing the BAS event once the issue has been identified and resolved. 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 participant event to a benefit program, but the associated participant is ineligible to elect any new options. Event did not change eligibility. Prepared none should indicate no change in benefits. No further action required. No further processing occurs for this BAS event. The online page description for this process status (on the Schedule Summary page, for example) is Prepare None.
PE - Prepare Error The system has encountered an error during option preparation for the participant associated with the event. Events are given a PE process status during option eligibility determination or calculation of credits. To correct, you should make corrections to the personal/employment/job information of the associated participant or to plan and option eligibility information. Each time you run Benefits Administration, the system will reevaluate events with a PE designation and (attempt to) move them along in the Benefits Administration process.

Entering Elections

Process Status
Description

Troubleshooting Steps

Next Processing Steps

ET – Entered
The employee or a benefits administrator has entered the participant's new elections into the system and they are ready for validation by the Benefits Administration process.
Note: eBenefits ESS BAS events move to a RE-Re-entered process status automatically during the nightly CSUBAS processing to await review of supporting documentation by the campus Benefits Office.
Event needs finalization. If the validation process finds no errors with the elections, the elections will be posted to the appropriate benefit and payroll tables, and the system will update the process status to FE (Finalized - Enrolled).
On the other hand, if there are errors with the elections, if any of the employee's choices are invalid, event rules are used to determine whether current elections or defaults should be loaded. The system will set the process status to EE (Election Error).
EE - Election Error System encountered an error when processing the elections for the BAS event. No elections are posted to the Base Benefits tables.
Errors are posted to the BAS Message table and are identified by participant and event.
The previous process status was either ET (entered) or EE (election error).
You need to correct the errors by reviewing and possibly reentering employee elections. No further processing occurs for this BAS event until resolved. When the Benefits Administration process runs again it will try to carry the event's process status forward to FE (Finalized - Enrolled).
Alternatively, you can arrange to "force finalize" this BAS event (or the entire set of BAS events in the Benefits Administration Open Enrollment schedule) to finalize it with errors. The system loads the default value(s) for the associated participant's erroneous benefit option election(s). If a dependent/beneficiary is in error, the system loads the employee's benefit plan choice but will not load the dependent/beneficiary.

Example of a Prep Error

example of a prep error

The Process Status shows Prepare Error.

Process Status shows Prepare Error.

Review the Ben Admin processing message(s) in the Processing Messages page (click on the NavBar Icon

navigation icon

then go to Menu > Benefits > Manage Automated Events > Review Processing Results > Processing Messages) via the On Demand Event Maintenance page, or on the BAS003 report and then resolve the issue. The example above requires pay calendars to be created, so for the above issues you would create a Service Now ticket to have pay calendars created in CHRS.

Once pay calendars are created, you can process the person through Ben Admin.

CSUBB010.SQR – Benefits Transaction Report

Description

This report includes employee data when the following items changed for the employee for the report run criteria:

  • Benefit Primary Job
  • Benefits Status
  • Employee Class
  • Employee Type
  • FTE
  • Pay Group
  • Union Code
  • Duration (eligibility config 1)
  • Job Code (eligibility config 2)
  • ACA Status (eligibility config 3)
  • AY Duration of Appt (on CSU Job).

Criteria

The CSU Benefits Transaction Rpt includes data when the items listed above changed for an employee. This report includes BAS transactions that have occurred within the last 30 days from the current system date or within a specified date range where the specified employee data in the Description section changed. Benefit items included on the report if applicable are Medical Plan, Medical Covg Cd, Med FlexCash, Dental Plan, Dental Covg Cd, Dental FlexCash, Vision Plan, Life (20) and Life ADD (23), LTD, HCRA and DCRA.

The report also includes:

  • Employee ID
  • Employee Name
  • SSN
  • Last Name
  • First Name
  • Home Address
  • City
  • State
  • Postal Code
  • Empl Rec #
  • Benefit Rec #
  • Action Date
  • Effective Date
  • Action
  • Action/Reason
  • Effective Sequence Number
  • Current Position Description
  • Previous Position Description
  • Current Job Code
  • Previous Job Code
  • Current Employee Class
  • Previous Employee Class
  • Current Employee Type
  • Previous Employee Type
  • Current Paygroup
  • Previous Paygroup
  • Current Duration Met
  • Previous Duration Met
  • Current ACA Eligible
  • Previous ACA Eligible
  • Current Benefits Status
  • Previous Benefits Status
  • Current FTE
  • Previous FTE
  • Current Total FTE
  • Previous Total FTE
  • Current Union Code
  • Previous Union Code
  • Current Benefit Program
  • Previous Benefit Program
  • Appointment End Date
  • Appointment Duration
  • CSU Unit
  • Current Benefits Primary Job
  • Previous Benefits Primary Job

The CSU Benefits Transaction Rpt is sorted by Employee ID, Employee Record Number, Effective Date, and Effective Sequence.

Use this report to verify that, if applicable, the appropriate benefit changes occurred for the employee.

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

Navigation icon

, then go to Menu > Benefits > Reports > CSU Benefits Reports > CSU Benefits Transaction Rpt

Example of Run Control Page

Example of Run Control Page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
CSU Benefits Transaction Rpt
  1. The CSU Benefits Transaction Rpt page appears.
CSU Benefits Transaction Rpt
  1. Enter your Business Unit.
  2. Select the Default – 30 Days checkbox if you want to run the report to check for transactions that occurred within the last 30 days from the current system date. You can select this checkbox or you can enter a From Date and Thru Date range, but you cannot use both.
  3. If you did not select the Default – 30 Days checkbox, enter a From Date and Thru Date range.
  4. Click on the Run button.
  5. The Process Scheduler Request page appears.
process scheduler request page
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the CSUBB010 process is selected (i.e., check marked), then click on the OK button.
  3. The CSU Benefits Transaction Rpt page appears, along with the Process Instance number. Write down this number in case you need it later.
  4. Click on the Process Monitor link to monitor the status of the report generation.
  5. The Process List page appears.
Process List page
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
Click on the View Log/Trace link.
  1. The View Log/Trace page appears. Click on the link that ends in .CSV as this is the report.
View Log/Trace page

Sample Report

image of Sample Report

CSUBAS30.SQR – CSU Benefits Termination Report

Description

This report identifies employees with benefits in plan types 10, 11, 14, 20, 23, 31, 60, 61, 1Y and 1Z that have or will be terminated during a specified time period.

Criteria

Inclusion in the report is determined by one of two dates: Coverage Begin Date or Coverage Elect Date. This report includes terminated records for each Plan Type if the coverage is Term and the previous coverage was Elect. Future dated Terminations are included in the report if the COVERAGE_ELECT_DT is within the date range on the run control.

Rehires are included on the termination report if there is a termination row in the previous 30 days and the employee has benefit enrollments in benefits eligible job codes. This report also includes FERP rehires for vision-only coverage. Benefit ineligible job codes are excluded (this report does not include jobs in the CSU Exclude or ACA Exclude lists). The report does identify if the employee has at least one active job as of the report run date.

The following items appear on the report:

  • First Name
  • Last Name
  • Empl ID
  • Job Code
  • Job Code Description
  • DeptID
  • Department Description
  • FTE
  • Empl Class
  • Active Job Y/N
  • Rehire <30 days
  • Current Ben Prog
  • Event Date
  • Event ID
  • Event Class
  • Medical Status
  • Dental Status
  • Vision Status
  • MedFlex Status
  • DenFlex Status
  • Life Status
  • Life ADD Status
  • Disability Status
  • HCRA Status
  • DCRA Status

Recommend Use and Follow-up

Use this report to audit job terminations with regards to benefit plan participation.

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

Navigation icon

, then go to Menu > Benefits > Reports > CSU Benefits Reports > CSU Benefits Termination Rpt

Example of Run Control Page

Example of Run Control Page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
CSU Benefits Termination Rpt page
  1. The CSU Benefits Termination Rpt page appears.
CSU Benefits Termination Rpt page
  1. Enter your Business Unit.
  2. Select the Default – 30 Days checkbox if you want to run the report to check for transactions that occurred within the last 30 days from the current system date. You can select this checkbox or you can enter a From Date and Thru Date range, but you cannot use both.
  3. If you did not select the Default – 30 Days checkbox, enter a From Date and Thru Date range.
  4. Click on the Run button.
  5. The Process Scheduler Request page appears.
Process Scheduler Request page
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the CSUBAS030 process is selected (i.e., check marked), then click on the OK button.
  3. The CSU Benefits Termination Rpt page appears, along with the Process Instance number. Write down this number in case you need it later.
  4. Click on the Process Monitor link to monitor the status of the report generation.
  5. The Process List page appears.
process list page
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
process detail page
  1. The View Log/Trace page appears. Click on the link that ends in .CSV as this is the report.
view log and trace page

Sample Report

image of Sample Report

CSUBAS30.SQR – CSU Job Change Prior to Ben Admin

Description

This report details any changes in a Job Data row where the Job Data Effective Date pre-dates the Benefits Administration Start Date where specific fields are updated.

Criteria

A compare occurs for the following fields on the previous and subsequent Job Data rows to determine if there was an impact to benefits enrollment or eligibility:

  • Benefit Primary Job
    • PRIMARY_JOBS.EMPL_RCD where PRIMARY_JOBS.PRIMARY_JOB_IND = Y
  • Benefits Status
  • Employee Class
  • Employee Type
  • Full Time Equivalent
  • Pay Group
  • Union Code
  • Duration (eligibility config 1)
  • Job Code (eligibility config 2)
  • ACA (eligibility config 3)
  • AY Duration of Appt.

Use this report to determine if you need to modify the Base Benefit rows for the employee and then reprocess the employee’s BAS events.

This report is not included in the nightly CSUBAS job schedule in CHRS. Run this report ad-hoc daily to review and resolve Ben Admin processing errors.

Navigation: Click on the NavBar Icon

Navigation icon

then go to Menu > Benefits > Reports > CSU Benefits Reports > CSU Job Changes Prior BenAdmin

Example of Run Control Page

Example of Run Control Page
  1. If you have a run control ID for this process, enter the Run Control ID on the Find an Existing Value page and then click the Search button.
  2. If you do not have a run control ID, click on the Add a New Value tab, enter your initials in the Run Control ID field, and then click on the Add button.
CSU Job Changes Prior BenAdmin page

The CSU Job Changes Prior BenAdmin page appears.

CSU Job Changes Prior BenAdmin page
  1. Enter your Business Unit.
  2. Select the Default – 30 Days checkbox if you want to run the report to check for transactions that occurred within the last 30 days from the current system date. You can select this checkbox or you can enter a From Date and Thru Date range, but you cannot use both.
  3. If you did not select the Default – 30 Days checkbox, enter a From Date and Thru Date range.
  4. Click on the Run button.
  5. The Process Scheduler Request page appears.
process scheduler request
  1. Select PSUNX in the Server Name field if able. Otherwise, leave this field blank.
  2. Verify that the CSUBAS030 process is selected (i.e., check marked). Note that the description says CSU Benefits Termination Rpt, but the CSU Job Changes Prior BenAdmin will generate.
  3. Click on the OK button.
  4. The CSU Job Changes Prior BenAdmin page appears, along with the Process Instance number. Write down this number in case you need it later.
  5. Click on the Process Monitor link to monitor the status of the report generation.
  6. The Process List page appears.
process list page
  1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success.
  2. Click on the Details link.
  3. The Process Detail page appears. Click on the View Log/Trace link.
process detail page
  1. The View Log/Trace page appears. Click on the link that ends in .CSV as this is the report.
view, log and trace page

Sample Report

image of Sample Report

Why Did a Benefit Terminate or Isn’t Correct Troubleshooting Checklist

Use the following checklist to troubleshoot and to help determine why a benefit or benefits are incorrect or why a benefit or benefits terminated for an employee and/or dependent. When researching the issue, do not assume that the Base Benefit tables for the employee are correct, especially when the employee has flagged BAS events that haven’t been reviewed and resolved.

Flagged BAS events are the result of retroactive changes keyed or processed into CHRS (late paperwork processing for new hires, rehires, transfers, terminations, life events, etc.), future-dated benefit enrollments, current, future-dated and historic corrections keyed into Job Data, Benefits Officers picking and choosing what to process and not process (i.e., not processing all BAS events for all employees), and daily processing of new BAS events for employees who already have flagged BAS events that haven’t been reviewed and resolved. Base Benefit tables may be incorrect for employees with flagged BAS events, especially for Out of Sequence BAS events. If BAS events are processed or reprocessed in the incorrect order, the employee’s benefits enrollments will be incorrect in the Base Benefit tables (see # 8 in the following checklist).

#
Task

Questions to Ask/Answer

1
Employee and dependent missing from interface file - determine why the employee or dependent is missing from the interface file for the applicable time period. If the employee or dependent is not on the interface file, one of these possibilities may exist:
  • The employee’s benefits terminated due to a terminated job, or the employee waived (i.e., cancelled) their benefits due to an unpaid leave of absence or short work break, benefits perhaps terminated due to a life event change for the employee like a marriage, or the employee dropped the dependent from the benefit plan in the life event due to the dependent gaining other coverage, or the employee dropped the benefit due to gaining other coverage.
  • The dependent aged out (18 years of age for a recognized child, 26 years of age for a qualified child). Go to Benefits > Employee/Dependent Information > Update Dependent/Beneficiary to review and determine. Note that adult dependents are not currently configured to age out in CHRS.
  • The benefit change(s) were entered one day at a time to support the multiple permitting event code workaround for medical and dental plans, and this particular change was not keyed until a later day. Go to Benefits > Enroll in Benefits > Health Benefits to review and determine. Note that the Election Date is the date that the enrollment is last processed via Ben Admin in CHRS. If using the multiple permitting event code workaround for medical, the enrollments will overwrite the Ben Admin and Base Benefit tables in CHRS each day. Use the applicable Ben Admin and the Base Benefit Audit table baseline queries in the CSU Benefits Administrator Tile or via Query Viewer to review and determine if the workaround was used and if it is an interface timing issue. Refer to the CHRS Benefits Audit Table User Guide for more information. Note that if the interface file date is prior to the Health Benefits Election Date, that may be the reason why the employee and/or dependent was not on the interface file.
  • The interface did not select the employee and/or dependent due to an interface selection criterion not met, such as gender missing, out of state address, etc. Refer to the PSR Error Clean Up Position Paper for PSR errors and resolution next steps.
2 Check the employee’s Payroll Status in Job Data>Work Location page for the applicable time period.
  • Is the employee’s Payroll Status Leave of Absence, Short Work Break, Terminated, Retired or Deceased? If so, their benefits may be waived (i.e., cancelled) or terminated. There might be some cases where an employee with a Suspended Payroll Status may have benefits cancelled (i.e., waived in CHRS). Go to Benefits > Manage Automated Enrollment > Employee Event Details to see what BAS events were processed, the processing Status Date, and the Plan Type page to see the Ben Admin changes that occurred (see the Employee BAS Event Details Cheat Sheet).
  • Go to Benefits > Review Employee Benefits > CSU Benefits Summary to review and determine benefit enrollment changes at a high level, and go to the Base Benefit tables i.e., Health Benefits, Disability Benefits, Life and AD/D Benefits, Spending Accounts to see benefit enrollment details.
  • Did the employee voluntarily waive benefits (i.e., cancel benefits) while on an unpaid leave, short work break, or due to a life event change? Go to Benefits > Manage Automated Enrollment > Employee Event Details to see what BAS events were processed, the processing Status Date, and the Plan Type page to see the Ben Admin changes that occurred (see the Employee BAS Event Details Cheat Sheet).
3 Check the employee’s Benefits Employee Status in Job Data>Benefits Program Participation page for the applicable time period.
  • Some benefits terminate based on the Benefits Employee Status. Is the employee’s Benefits Employee Status Leave of Absence, Terminated, Retired or Deceased? If so, their benefits may be waived (i.e., cancelled) or terminated.
  • Did the employee voluntarily waive benefits (i.e., cancel benefits) while on an unpaid leave, short work break, or due to a life event change? Go to Benefits > Manage Automated Enrollment > Employee Event Details to see what BAS events were processed, the processing Status Date, and the Plan Type page to see the Ben Admin changes that occurred (see the Employee BAS Event Details Cheat Sheet).
4 Did the employee lose benefits eligibility for the applicable time period?
  • Did the employee lose benefits eligibility due to ACA (Affordable Healthcare Act)?
  • Did the employee end another CSU job?
  • Did the employee’s Benefits Primary Job change? Go to Benefits > Maintain Primary Jobs > Maintain Flags and review the effective-dated rows listing the employee’s Benefits Primary Job.
  • Did the employee waive benefits (i.e., cancel benefits) while on an unpaid leave, short work break, or due to a life event change? Go to Benefits > Manage Automated Enrollment > Review Processing Results > Employee Event Details to see what BAS events were processed, the processing Status Date, and the Plan Type page to see the Ben Admin changes that occurred (see the Employee BAS Event Details Cheat Sheet).
  • Did the employee have a work location or home address zip code and/or state change that fell outside of a geographic benefit eligibility area? Go to Workforce Administration > Personal Information > Modify a Person > Contact Information page and Workforce Administration > Job Information > Job Data > Work Location page to determine. The Geographic Location Elig Table stores zip code configurations for regional benefit plans (Set Up HCM > Product Related > Automated Benefits > Eligibility and Event Rules). Review this configuration table to see if the employee’s work location or home address zip code are in the applicable regional benefit plan table for the applicable effective date.
  • Did the Elig Fld 1, 2, 3 or 5 values in Benefits Program Participation change for the employee’s Benefits Primary Job? Go to Job Data > Benefits Program Participation page to review as this can impact benefits eligibility.
5 Did the dependent lose benefit eligibility for the applicable time period?
  • Did the dependent age out (18 years of age for a recognized child, 26 years of age for a qualified child)? Go to Benefits > Employee/Dependent Information > Update Dependent/Beneficiary to review and determine. Note that adult dependents are not currently configured to age out in CHRS.
  • Was this a conversion issue from HR9.0 where the dependent was missing in HR9.0 or was dropped in the HR9.0 to CHRS conversion process? Compare against the old HR9.0 database, your campus conversion database and CHRS to determine.
  • Is the dependent disabled but not selected as a disabled dependent for the applicable time period? Go to Benefits > Employee/Dependent Information > Update Dependent/Beneficiary to review and determine.
  • Did the dependent’s relationship to the employee change, such as spouse to ex-spouse, domestic partner to ex-domestic partner? Go to Benefits > Employee/Dependent Information > Update Dependent/Beneficiary to review and determine.
  • Did the Elig Fld 1, 2, 3 or 5 values in Benefits Program Participation change for the employee’s Benefits Primary Job? Go to Job Data > Benefits Program Participation page to review as this can impact benefits eligibility.
6 Did the employee recently transfer between CSU campuses? For example, the employee terminated from Fullerton and transferred to Stanislaus?
  • Review Job Data. Note the action/action-reason combinations that were used to process the termination and the hire rows. Some benefits may have terminated in error due to certain action/action-reason rows that were keyed into Job Data by the terminating and hiring campuses, or some benefits may have terminated in error due to CSU business processes or lack of CSU business processes. If this is the case, work with CMS-Benefits and System Wide Human Resources (SWHR) to determine if there need to be CHRS configuration and/or CSU business process changes.
  • If the employee transferred between CSU locations, also review the Employee Event Detail > Plan Type page to see the Ben Admin changes that occurred (see the Employee BAS Event Details Cheat Sheet to learn how to use the Employee Event Detail component).
7 Are there flagged BAS events for the applicable time period? Flagged BAS events are the result of retroactive changes keyed or processed in CHRS (late paperwork processing for new hired, rehires, transfers, terminations, etc.), corrections keyed into Job Data, Benefits Officers picking and choosing what to process for employees and not processing all BAS events that may impact benefit eligibility for employees, and daily processing of new BAS events for employees who already have flagged BAS events that haven’t been resolved.
  • Go to Benefits > Manage Automated Enrollment > Events > Update Event Status or Review Processing Results > Employee Event Detail pages and look for flagged BAS events. Look for Out of Sequence, Address Eligibility Changed (work location or home address changed), Multi Job Indicator Changed (added or ended a concurrent job) and Job Eligibility Changed (key benefit fields changed in Job Data).
  • If the Address Eligibility Change flag is selected, go to Workforce Administration > Personal Information > Modify a Person and see if the employee’s home state and/or home zip code changed, then go to Job Data and review the Job Data rows equal to and prior to the BAS event date to see if the employee’s work location changed that resulted in a zip code and/or state change. Zip code and state changes may impact benefit plan participation eligibility if the employee is enrolled in a region-based benefit plan or plans. For example, if an employee moves out of a benefit plan service area, the employee is no longer eligible to participate in that benefit plan.
  • If the Job Eligibility flag is selected, go to Job Data and review the following fields on Job Data rows equal to and prior to the BAS event date to see if changes occurred for the following fields (note that the Job Eligibility flag is selected when the delivered PSPBARUN (Ben Admin) process runs when the following fields change in Job Data, regardless if CSU uses the fields in benefit eligibility processing or not): Benefits Employee Status, Location, Empl_Class, Employee Type, FLSA Status, Salary Plan, Grade, Full/Part Time, Regular/Temporary, Service Months, Standard Hours, Union Code, Pay Group, Officer Code, FTE, Combined FTE, ACA Eligibility Status, Elig Fld 1, Elig Fld 2, Elig Fld 3, Elig Fld 4, Elig Fld 5, Elig Fld 6, Elig Fld 7, Elig Fld 8 and Elig Fld 9. Also see if the BAS GROUP ID changed.
  • If the Multi Job Eligibility flag is selected, go to Job Data and review the following fields for all active jobs for the employee on Job Data rows equal to and prior to the BAS event date to see if changes occurred for the following fields (note that the Multi Job Eligibility flag is selected when the delivered PSPBARUN (Ben Admin) process runs when the following fields change in Job Data, regardless if CSU uses the fields in benefit eligibility processing or not): Benefits Employee Status, Location, Empl_Class, Employee Type, FLSA Status, Salary Plan, Grade, Full/Part Time, Regular/Temporary, Service Months, Standard Hours, Union Code, Pay Group, Officer Code, FTE, Combined FTE, ACA Eligibility Status, Elig Fld 1, Elig Fld 2, Elig Fld 3, Elig Fld 4, Elig Fld 5, Elig Fld 6, Elig Fld 7, Elig Fld 8 and Elig Fld 9. Also see if the BAS GROUP ID changed.
  • Note that CSU uses the following Job Data fields in benefit eligibility rules: Benefits Employee Status, Location, Empl_Class, Employee Type, FTE, Company Code, Pay Group, Union Code, Elig Fld 1 indicates if the employee met Duration of Appointment, Elig Fld 2 is the employee’s Job Code, Elig Fld 3 indicates if the employee is ACA eligible and Elig Fld 5 (AFTERTAX) is used to reveal after-tax Medical plans for employee benefit plan enrollment.
  • Also note that Base Benefit tables (i.e., Health Benefits, Disability Benefits, Life and AD/D Benefits, Spending Accounts) may be incorrect for employees with flagged BAS events, especially for Out of Sequence BAS events. If BAS events are processed or reprocessed in the incorrect order, the employee’s benefits enrollments will be incorrect in the Base Benefit tables.
  • If the Out of Sequence flag is selected, you will need to reprocess the employee’s BAS events in the correct reprocessing order (see #8). Refer to and follow the instructions on the Reprocessing a CHRS Event Cheat Sheet and the eBenefits OK to Reprocess Cheat Sheet. In some instances, eBenefits BAS events may require voiding and re-entry using the HBE BAS event.
8 Were BAS events processed or reprocess in the incorrect order for the applicable time period? Processing or reprocessing BAS events out of order will erroneously terminate an employee’s benefits. There is not a way to determine the order BAS events were originally manually processed or reprocessed in delivered PeopleSoft. You can use the applicable Ben Admin and the Base Benefit Audit table baseline queries in the CSU Benefits Administrator Tile or via Query Viewer to review and determine if BAS event processing order to a certain point, but it won’t provide the entire answer. If interested in using audit tables, refer to the CHRS Benefits Audit Table User Guidefor more information. The best solution is to reprocess an employee’s BAS event using the correct processing/reprocessing rules as follows to correct an employee’s benefit enrollments.
  1. First, always process in Event Date order from the oldest flagged BAS event to the newest flagged BAS event (i.e., process the 1/1/2022 BAS event first, then process the 2/1/2022 BAS event second, and so on). Use the Update Event Status page to see the Event Date (Benefits > Manage Automated Enrollment > Events). You can also click on the Event Status Update button in the On Demand Event Maintenance page.
  2. If you have multiple BAS events for the same Event Date, process those BAS events in Event Priority order for the event date from the lowest to the highest (i.e., process Event Priority 35 first, then Event Priority 45, then Event Priority 200, then Event Priority 375, and so on). Go to Benefits > Manage Automated Enrollment > Events > Update Event Status page to see the Event Priority. You can also click on the Event Status Update button in the On Demand Event Maintenance page.
  3. If you have multiple BAS events for the same Event Date and same Event Priority, process those BAS events by Event ID order from lowest to highest (process Event ID 1 first, then Event 2, then Event 3, and so on). Go to Benefits > Manage Automated Enrollment > Events > Update Event Status page to see the Event ID. You can also click on the Event Status Update button in the On Demand Event Maintenance page.
9 Possible CSU Benefit configuration issue? There are many delivered and CSU-custom eBenefits, Ben Admin and Base Benefit configuration pages. If you suspect that there is a CHRS Benefits configuration issue, create a Service Now ticket for CMS-Benefits to review.

Appendix A – Ben Admin Error Messages

The items in bold are Ben Admin error messages have the possibility of showing up most frequently. This is not a complete list as Ben Admin error messages that are not possible (such as messages for credits, group coverage errors, pension table errors, rollovers for savings plans) have not been included. A complete message listing may be viewed within the application in: PS_PAY_MESSAGE_TBL. (Note: This table will display ALL messages-not just Benefits related messages). Note that CMS involvement is required in order to resolve configuration (table setup) issues in CHRS.

Message ID
Description

Suggested Resolution

000005
The deduction code displayed below was not found in the deduction table. Table Setup: Check the associate's Benefit Program, make sure that the spelling of the Deduction Code matches the row in the Deduction Table. Either change the Benefit Program or the Deduction Table entry to match the other. Rerun the process following the 'Prep Error' procedure.
000011 The pay group displayed below was found but is currently inactive. Table Setup: Determine the associate's company and paygroup on Job Data. Then, lookup the company/ paygroup combination in the Paygroup Table. Either change the associate's paygroup or activate the paygroup on Paygroup Table. Rerun the BenAdmin process following the 'Prep Error' procedure.
000014 The pay group displayed below was not found in the pay group table. Table Setup: Determine the associate's company and paygroup on Job Data. Then, determine whether the paygroup should be added to the Paygroup Table. If not, correct the associate's paygroup on Job Data. Rerun the BenAdmin process following the 'Prep Error' procedure.
000015 The pay calendar entry displayed below was not found in the pay calendar table. Table Setup: Coordinate with payroll to run the pay calendar setup program for the indicated paygroup. Rerun the BenAdmin process following the 'Prep Error' procedure.
000023 The company displayed below was not found in the company table. Table Setup: Determine the associate's company on Job Data. Then, determine whether the company should be added to the Company Table. If not, correct the associate's company on Job Data. Rerun the BenAdmin process following the 'Prep Error' procedure.
000024 The company displayed below was found but is currently inactive. Table Setup: Determine the associate's company on Job Data. Then, determine whether the company should be active on the Company Table. If not, correct the associate's company on Job Data. Rerun the BenAdmin process following the 'Prep Error' procedure.
000027 The benefit plan displayed below was not found in the appropriate benefit table. Table Setup: Check the Benefit Plan Table to ensure benefit plan has been set up. If it exists, then check the associate’s Benefit Program Table to ensure that the benefit plan exists as an option. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000030 An age-graded rate was not found for the employee's category. Review the Age Graded Rate Table set-up for the benefit specified / table ID specified. Review the associate’s age / sex to ensure it applies to the table data. Many times, this error is caused by no sex or birthdate being specified in Personal Data. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000039 The Coverage Group for the Life/ADD plan was not found. Review the Life and AD/D Plan Table for the benefit plan specified to ensure the proper Coverage Group Code is present. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000056 The form displayed below was not found in the Form Table. Review the Form Table for the form ID specified. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000070 There is no birth date provided for this employee. The employee participates in the life insurance plan identified below. That plan uses an age-graded rate table to determine costs and requires a birth date. Review the associate’s Personal Data page to ensure that a birth date is specified on the page. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000087 The Benefit Program defined for this employee was not found. Review the Ben Prog Partic record for the associate and then the Benefit / Deduction Program Table for the specified program. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000088 The Benefit Program defined for this employee was inactive for the current check date. Review the Benefit / Deduction Program Table status for the program specified. Correct if appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000089 The Benefit Plan / Deduction Code is not found for the Benefit Program defined for this employee. Review the Benefit / Deduction Program Table for the specified plan / deduction. Correct if appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000090 The Calculation Rules table was not found for the Benefit defined. Review the Benefit / Deduction Program Table for the specified calc rules ID. Correct if appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000099 The Service Rate Table named below was not found in the database. Review the Service Rate Table for the specified service rate ID. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000100 The service value for this employee was not found in the ranges defined for this Service Rate Table or the Service Step Table. The first value is the Plan Type, next is the table name, and finally, the table type. Review the message detail. The first value is the Plan Type, next is the table name, and finally, the table type. Determine the benefit and table ID assigned to the plan. Then review the Service Rate Table or Service Step Table with which the Plan Type is associated. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000128 During Program Assignment, it was determined that this employee is eligible for more than one program. The Eligibility Rules Tables need to be modified to make Program eligibility unique. One error message will be generated for each eligible program. (MSGData1: Benefit-Program) Associates can only be eligible for one benefit program per empl record. Review the Eligibility Rules Table, comparing the data there with the data on the associate’s record. Correct data where eligibility duplicates exist. Rerun the BenAdmin process following the 'Assgn Error' procedure.
000129 During Program Assignment, it was determined that this employee is not eligible for any Benefit Program. The system attempted to terminate current participation, but no current PS_Ben_Prog_Partic record was found (default Hire record is missing). The bottom row of the associate’s Ben Prog Partic record should be effective dated to match that of the effective date of the bottom row of their Job record (Hire record). Review the associate’s Ben Prog Partic record. If no data exists which matches the Hire date, insert a row with the effective date matching the effective date of the Hire record. Rerun the BenAdmin process following the 'Assgn Error' procedure.
000132 The indicated salary-rate was not found on the Salary_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Table-Id) Review the Salary Rate Table to ensure proper set up of rate information. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000133 The indicated flat-rate was not found on the Flat_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Table-Id) Review the Flat Rate Table to ensure proper set up of rate information. Correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000149 Duplicate Enrollment Replaced. Informational Only: The system encountered a new enrollment action for which a Benefit Enrollment record already exists with the same Effective Date. The system deleted the current Benefit Enrollment record (and all associated dependent/beneficiary and investment records where applicable) and replaced it with the new enrollment. (MSGData1: Plan-Type; MSGData2: EffDt) This message indicates that two events have processed for the individual that have overwritten one another meaning the deduction begin date was the same for both events. This may be a coordination issue depending on which event was processed last. Check your events to make sure they processed in correct order.
000150 The Event Rule for this Plan Type requires that an election be made (the Election-Required indicator on Bas_Event_Rules is Yes) but no Option-Cd has been specified on Bas_Partic_Plan. (MSGData1: Plan-Type) This message indicates that the Elect Required flag has been turned on for this particular event and that no election was made for this event. Peruse the Benefit / Deduction Program Table to find the Event Rules ID associated with the plan type indicated. Now review the Event Rules Table using the proper Event Rules ID. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000151 The Option-Cd elected on Bas_Partic_Plan does not exist as an eligible 'O' or 'W' entry on Bas_Partic_Optn. (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Benefit / Deduction Program Table for the specified plan type and option. If data is correct, re-enter the Emplid in the Election Entry pages and correct the option code in error. If data on the Benefit / Deduction Program Table is in error, correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000152 The Option-Cd elected on Bas_Partic_Plan requires proof of insurability (the Proof-Required-Indicator on Bas_Partic_Optn is Yes) but the Proof-Received-Indicator is still No. (MSGData1: Plan-Type; MSGData2: Option-Cd) Peruse the Benefit / Deduction Program Table to find the Event Rules ID associated with the Plan Type indicated. Now review the Event Rules Table using the proper Event Rules ID. If the rule is incorrect, correct where appropriate. If the rule is correct and proof has not been received, the associate is not eligible for the benefit until such time as proof is received. Rerun the BenAdmin process following the 'Election Error' procedure.
000153 A Life_ADD_Tbl record was not found for the indicated 2x Plan Type being processed on Bas_Partic_Plan. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Event-Dt) Review the Life and AD/D Table to ensure proper set up of the benefit plan indicated. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000154 Event / Record Mismatch.
The PS_Job record which triggered a previous event can no longer be found (the record may have been deleted). Because of this, the Event cannot be processed any further. (MSGData1: Event Date)
Review the associate’s Job record matching the Empl Rcd #, Effective Date and / or Effective Date Sequence # indicated. If proper data exists, contact your technical support person for assistance. If data does not exist, the associate can no longer be processed in this Event Maintenance cycle for the event, due to the deletion of Job data. Examine more closely the event that had been processed to see if any action needs to be done. If the event was already finalized it may now need to be voided.
000155 No Schedule could be found to process a new event. A Schedule-Id must exist that matches the employee’s Company and BAS-Group-ID. (MSGData1: Company; MSGData2: BAS-Group-Id) Review the Schedule Table to ensure proper set up of the schedule indicated. If none exists, add a Schedule to the table including the proper BAS Group ID for processing Event Maintenance. Restart COBOL process with “None” Reprocess radio button turned on.
000156 The Option-Cd elected on Bas_Partic_Plan requires that a flat coverage amount be supplied (the Life-ADD-Covrg code is '1') but the Flat-Amount on Bas_Partic_Plan is zero. (This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on Employee Record). (MSGData1: Plan-Type; MSGData2: Option-Cd) This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on associate Record. Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question. If data is correct, re-enter the EmplID in the Election Entry pages and supply the flat amount of insurance. If data on the Life and AD/D Table is in error, correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000157 The Option-Cd elected on Bas_Partic_Plan requires that a salary coverage factor be supplied (the Life-ADD-Covrg code is '2') but the Factor-Xsalary on Bas_Partic_Plan is zero. (This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on Employee Record). (MSGData1: Plan-Type; MSGData2: Option-Cd) This message will only occur when the Life-ADD-Covrg type on Life_ADD_Tbl is '3' -Specify on associate Record. Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question. If data is correct, re-enter the EmplID in the Election Entry pages and supply the salary coverage factor for the proper insurance coverage calculation. If data on the Life and AD/D Table is in error, correct where appropriate and rerun the BenAdmin process following the 'Prep Error' procedure.
000158 The Option-Cd elected on Bas_Partic_Plan requires that a Benefits Base (either the Annual or BenefitsBase salary) be indicated for use in the calculation of Factor-Times-Salary life coverage amounts (the Life-ADD-Covrg code is '2') but the Benefits-Base flag on Bas_Partic_Plan is blank. (This message will only occur when the Life-ADD-Covrg code on Life_ADD_Tbl is '3' - Specify on Employee Record) (MSGData1: Plan-Type; MSGData2: Option-Cd) This message will only occur when the Life-ADD-Covrg code on Life_ADD_Tbl is '3' - Specify on associate Record. Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question. If data on the Life and AD/D Table is in error, correct where appropriate. If data is correct, review the associate’s Job Data to ensure that an Annual Rate or Benefits Base Rate is specified. If one is not present, contact the Payroll Supervisor for corrective action. If a salary is present, contact your technical support person for assistance. When data is corrected, rerun the BenAdmin process following the 'Election Error' procedure.
000159 The Option-Cd elected on Bas_Partic_Plan requires that a coverage calculation method be specified, but the Life-ADD-Covrg code on Bas_Partic_Plan is neither '1'(Flat Amount) nor '2'(Factor Xsalary). (This message will only occur when the Life-ADD-Covrg code on Life_ADD_Tbl is '3' - Specify on Employee Record) (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question. If data on the Life and AD/D Table is in error, correct where appropriate. If ‘3’ - Specified in associate Record is turned on review the associate’s Job Data - Use - Job Data) to ensure that an Annual Rate or Benefits Base Rate is specified. If one is not present, contact the Payroll Supervisor for corrective action. If ‘4’ - Special Calculation Routine or ‘5’ - Sum of Dependent Coverage is turned on, contact your technical support person for assistance. When corrections are complete, rerun the BenAdmin process following the 'Election Error' procedure.
000160 The Option-Cd elected on Bas_Partic_Plan is not defined as "Specify on Employee Record" (the Life-ADD-Covrg code on Life_ADD_Tbl is not '3'), but one of the fields Flat-Amount or Factor-Xsalary on Bas_Partic_Plan is not equal to zero. These two fields can only be used when the Life Plan is "Specify on Employee Record". (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Life and AD/D Table to ensure that the data established is correct for the benefit plan in question. If data on the Life and AD/D Table is in error, correct where appropriate. If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Amount or Factor –x Salary for the proper insurance coverage calculation. When corrections are complete, rerun the BenAdmin process following the 'Election Error' procedure.
000161 A Savings_Plan_Tbl record was not found for the indicated 4x Plan Type being processed on Bas_Partic_Plan. (MSGData1: Plan-Type; MSGData2: Benefit-Plan; MSGData3: Event-Dt) Review the Savings Plan Table to ensure proper set up of the benefit plan indicated. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000162 For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected before-tax contributions on a "Percent of Gross" basis (the Savings-Covrg field equals '2') but the Flat-Ded-Amt field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table to ensure proper set up of the benefit plan indicated. If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Deduction Amount data and enter the correct before-tax Percent of Gross. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000163 The employee's before-tax Savings Plan contribution rate (the Pct-Gross field on Bas_Partic_Plan) is greater than the maximum allowed percentage contribution on the Savings_Pln_Tbl (Empl-Pct-Btax field). (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table and correct the associate Before Tax Investment Limited To amount. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000164 For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected before-tax contributions on a "Flat-Amount" basis (the Savings-Covrg field equals '1') but the Pct-Gross field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table to ensure proper set up of the benefit plan indicated. If data is correct, re-enter the EmplID in the Election Entry pages and delete the Percent of Gross data and enter the correct Flat Deduction Amount. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000165 For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "Percent of Gross" basis (the Savings-Covrg-Atax field equals '2') but the Flat-Ded-Amt-Atax field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table to ensure proper set up of the benefit plan indicated. If data is correct, re-enter the EmplID in the Election Entry pages and delete the Flat Deduction Amount data and enter the correct after-tax Percent of Gross. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000166 The employee's after-tax Savings Plan contribution rate (the Pct-Gross-Atax field on Bas_Partic_Plan) is greater than the maximum allowed percentage contribution on the Savings_Pln_Tbl (Empl-Pct-Atax field). (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table and correct the associate After Tax Investment Limited To amount. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000167 For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "Flat-Amount" basis (the Savings-Covrg-Atax field equals '1') but the Pct-Gross-Atax field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table to ensure proper set up of the benefit plan indicated. If data is correct, re-enter the EmplID in the Election Entry pages and delete the Percent of Gross data and enter the correct Flat Deduction Amount. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000168 The employee has elected a Savings Plan option, but no contribution rate has been specified (the combined sum of Pct-Gross, Pct-Gross-Atax, Flat-Ded-Amt and Flat-Ded-Amt-Atax fields on Bas_Partic_Plan equals zero). (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages and enter the correct data required for the associate enrollment for the Savings Plan. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000169 The employee has elected a Savings Plan option, but the total contribution rate (sum of Pct-Gross and Pct-Gross-Atax fields on Bas_Partic_Plan) is greater than the maximum allowed combined percentage contribution on the Savings_Pln_Tbl (Empl-Limit-Pct field). (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Savings Plan Table (Define Business Rules - Administer Base Benefits - Setup) to find the associate Investment Limited To Percentage. Re-enter the EmplID in the Election Entry pages and enter the proper percentages to be less than or equal to the total investment limit. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000171 The total of percentage allocation of all Savings Plan investment options is invalid (the Investment-Pct fields for each Investment-Opt elected on Bas_Partic_Invt are greater than zero but are not equal to 100%. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages and enter the proper percentages for investment purposes, ensuring that all percentages are equal to 100%. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000172 The indicated Investment-Opt elected on Bas_Partic_Invt was not found as an active, eligible option in the Savings_Inv_Tbl. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Investment-Opt) Review the Savings Plan Table for the Investment Options set up. If incorrect, add or delete the proper investment options. Re-enter the EmplID in the Election Entry pages and enter the proper investment option(s). Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000173 The employee elected an FSA Plan option, but the Empl-Contributn-Amt or Annual-Pledge fields on Bas_Partic_Plan are less than or equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages and enter the proper associate Contribution Amount of Annual Pledge amount for the FSA plan. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000174 The employee elected an FSA Plan option, but the Annual_Pledge amount specified on Bas_Partic_Plan is less than the minimum allowed on Ben_Defn_Plan (Min-Annual-Contrib). (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Benefit / Deduction Program Table for the amount specified as the FSA Minimum Annual Pledge. Re-enter the EmplID in the Election Entry pages and enter the proper Annual Pledge amount for the associate. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000175 The employee elected an FSA Plan option, but the Annual_Pledge amount specified on Bas_Partic_Plan is more than the maximum allowed on Ben_Defn_Plan (Max-Annual-Contrib). (MSGData1: Plan-Type; MSGData2: Option-Cd) Review the Benefit / Deduction Program Table for the amount specified as the FSA Maximum Annual Pledge. Re-enter the EmplID in the Election Entry pages and enter the proper Annual Pledge amount for the associate. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000184 The employee has covered a dependent or assigned a beneficiary on the Bas_Partic_Dpnd table whose Dependent-Benef Id could not be found in the base Dependent_Benef table. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent-Benef) Review the Dependent / Beneficiary to review the established dependents and/or beneficiaries the associate has listed. Correct data, where appropriate. Re-enter the EmplID in the Election Entry pages and enter the correct dependent / beneficiary ID on the proper page. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000185 The employee has specified on Bas_Partic_Dpnd the Id of a beneficiary (type 'B') to be covered under a Plan Type that only allows dependents (types 'D' or 'O'). Only "dependents" may be covered under Plan Types 1X, 24 and 25. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent-Benef) Re-enter the EmplID in the Election Entry pages and enter the correct beneficiary ID on the proper page for the Plan Type specified. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000186 The employee has specified on Bas_Partic_Dpnd the Id of a dependent (type 'D') to be an assignee under a Plan Type that only allows beneficiaries (types 'B' or 'O'). Only "beneficiaries" may be covered under Plan Types 20, 21, 22, 4X and 8X. (MSGData1: Plan-Type; MSGData2: Option-Cd; MSGData3: Dependent-Benef) Re-enter the EmplID in the Election Entry pages and enter the correct dependent ID on the proper page for the Plan Type specified. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000187 The employee has elected a Dependent Coverage Plan Type (eg., 24 or 25). While specifying the dependents to be covered on Bas_Partic_Dpnd, beneficiary percentages were entered. This is not valid for these Plan Types. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Delete the beneficiary percentages entered. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000188 The employee has assigned benefits under a Plan using percentage allocations, but the percentages do not total 100% for both primary and contingent beneficiaries. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Change the beneficiary percentages to total 100%. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000192 The employee has assigned benefits under a Plan using flat-amount allocations but has failed to designate an "excess" beneficiary. An excess beneficiary must be specified to handle the possibility that the coverage amount exceeds the specified flat allocations. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter an excess beneficiary or change one of the beneficiaries already designated as the excess beneficiary, leaving flat amount blank. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000193 The sum of the Health Care FSA and Dependent Care FSA Annual-Pledge fields on Bas_Partic_Plan is greater than allowable combined maximum as defined on Ben_Defn_Pgm (the FSA-Max-Annl-Pldg field). (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Health Care spending account benefit. Review the pledge amount entered. Now scroll to the Dependent Care spending account benefit and review the pledge amount entered there. Add the two amounts together and adjust the totals according to the FSA Maximum Pledge Amount specified on the Benefit / Deduction Program Table. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000195 Based on the Event date being processed, the Pay-Begin-Date for the next pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay-Group; MSGData3: Event-Dt) Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000196 Current Pay Period Not Found.
Based on the Event date being processed, the Pay-Begin-Date for the current pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay-Group; MSGData3: Event-Dt)
Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000197 Based on the Event date being processed, the Pay-Begin-Date for the next full pay period cannot be determined from PS_Pay_Calendar. Establish the missing periods in the pay calendar. (MSGData1: Company; MSGData2: Pay-Group; MSGData3: Event-Dt) Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000198 Event Rules ID Not Found.
While processing an event for this employee which involves a transfer between Benefit Programs, the system could not find an applicable Event Rule on PS_Ben_Defn_Plan to use to terminate the employee’s current elections. (MSGData1: Plan-Type; MSGData2: Benefit-Program; MSGData3: Event-Dt)
When an individual moves between benefit programs the Ben Admin process will use the newly assigned benefit program’s event rules to determine how to process an event. However, for Plan Types that are not in the new benefit program, the process goes back to the previous program to determine how to process the Plan Type. If the Plan Type is not in the previous program either, then the process does not know how to handle the Plan Type. Most of the time the COBOL process wills abend. In very few instances you will get this message. In either case, to resolve, you will need to manually fix the data and prepare options again on the event.
000199 A Bas_Partic_Cost record required for computing the indicated option's price or credit amount cannot be found. (MSGData1: Plan-Type; MSGData2: Option-Id) Review the Benefit / Deduction Program Table- Cost page for the Plan Type and option ID indicated. Enter the appropriate rate information. Most of the time this will abend the COBOL batch process. In the event that you do get this message the event should be in a “Prep Error” status and you should be able to just rerun the process once the program entry is corrected.
000200 The employee has elected a Plan Type that requires covered dependents, but no dependents (Dependent-Benef types 'D' or 'O') have been specified on Bas_Partic_Dpnd. Dependents must be specified under Plan Types 1X, 24 and 25. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the covered dependents for the Health Plans the associate is enrolled in or change the coverage code to ‘1’ associate Only. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000201 The employee has elected a Plan Type that requires assignment of beneficiaries, but no beneficiaries (Dependent-Benef types 'B' or 'O') have been specified on Bas_Partic_Dpnd. Beneficiaries must be specified under Plan Types 20, 21, 22, 4X and 8X. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000202 The employee has elected a Savings Plan that requires the selection of investment options, but no investment entries exist on Bas_Partic_Invt. (MSGData1: Plan-Type; MSGData2: Option-Cd) Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the investment option for the benefit plan specified. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000220 Dependent enrolled in a health plan is deceased as of the event date. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000221 A dependent who is an ex-spouse with a marital status date less than or equal to the event date may not be enrolled in a health plan. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000222 Non-student is overage.
A dependent that is not a student is over the age limit specified at the benefit program level as of the event date.
Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000223 A dependent that is a student as of the event date is over the age limit specified at the benefit program level. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000224 The benefit program does not allow coverage for married dependents. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000225 The number of dependents is less than the minimum defined for the elected coverage code. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000226 The number of dependents enrolled exceeds the maximum allowed for the coverage code. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000227 A dependent that is a spouse has been elected for coverage. The coverage code prohibits spouses from being enrolled. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000228 A dependent with the relationship of spouse must be enrolled for the coverage elected. Re-enter the EmplID in the Election Entry pages moving to the proper page for the Plan Type specified. Enter the correct dependent information or make sure the coverage code is correct for the plans the associate is enrolled in. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000232 The FSA Annual Pledge elected cannot be less than the total amount of claims that have been approved for payment to date. Increase the Annual Pledge until it equals or exceeds the Approved amount, as shown on the FSA Year-to-Date Activity page. (MSGData1: Plan-Type; MSGData2: Option-Cd) This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD approved for payment amount for the MER/DCA plan in the calendar year. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000233 The FSA Annual Pledge elected cannot be less than the total amount of FSA contributions that have been deducted to date. Increase the Annual Pledge until it equals or exceeds the Contributions amount, as shown on the FSA Year-to-Date Activity page. (MSGData1: Plan-Type; MSGData2: Option-Cd) This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD deductions taken for the MER/DCA plan in the calendar year. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000234 No Open On-Cycle Pay Periods
000235 The current FSA deduction calculation was determined to be negative, indicating that the Annual Pledge and the year-to-date Deduction Balance for this Plan Type are out of agreement. For consistency, a zero deduction amount has been returned since negative deductions are not supported. Please adjust as required either to the employee's benefit election or to his deduction balances. (MSGData1: Plan-Type and Benefit-Plan; MSGData2: Deduction-Code and Class; MSGData3: Calculated negative deduction) This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but the Annual Pledge amount was less than the total YTD deductions taken for the MER/DCA plan in the calendar year. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000236 The employee elected an FSA Plan option, but the Annual-Pledge field on Bas_Partic_Plan is less than or equal to zero. This is a required entry and must be a positive dollar amount. (MSGData1: Plan-Type; MSGData2: Option-Cd) This message is saying that when the enrollment for FSA was done, the associate was enrolled in the plan, but forgot to put in an YTD pledge amount. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000288 No covered dependents were found for this Plan. This is a Dependent Life plan-type, which requires that each dependent covered by the policy be individually entered. Because no dependents were found, the Coverage Amount, and therefore the resulting Deduction, may have been calculated as $0. This may also impact imputed income calculations. (MSGData1: Plan-Type) This message is saying that when the enrollment for dependent life was done, no dependents were ever tied to the plan, so there may be a problem with imputed income on dependent life. Correct where appropriate and rerun the BenAdmin process following the 'Election Error' procedure.
000292 The employee has an unfinalized event on a job row that is not the highest sequence number for that day. This can be caused by someone adding a new row for the day after event maintenance has already started processing the earlier row. Please review the employee's events and take appropriate action. (MSGData1: Job-EffDate; MSGData2: Job-EffSeq) This message is telling you that a new event has been initiated with an event date prior to a finalized future event. There may be some coordination issues to deal with so examination of the future event needs to take place and possibly reprocessing of the event.
000293 The system has found a new sequence number on this date. The system has already processed an event for this date. Please review this employee’s events. The system will not take any automatic action against the earlier event. (MSGData1: Job-EffDate; MSGData2: Job-EffSeq) This message is telling you that a new event has been initiated with an event date equal to a currently processing event. There may be some coordination issues to deal with so examination of the current event needs to take place and possibly reprocessing of the event.
000294 This event has become disconnected (the associated JOB record has been deleted or redated). This event has a status of Finalized-Enrolled. This means that the system may have made changes to the employee's benefit elections. Review the employee's benefits to see if the employee's benefits should be changed or redated. (MSGData1: Event-Date) This message is telling you about an event in a Finalized-Enrolled status has been disconnected. The event was completed and an enrollment situation was performed meaning that before the job record was deleted, the event should have been voided. Be sure that there are no active elections for this disconnected event in Base Benefits.
000295 Future Election Deleted.
Informational only: The system encountered a new enrollment action for a plan type for which a future dated benefit enrollment record already exists. The existing enrollment record was inserted by an event which precedes the current event. The system deleted the future benefit enrollment record (and all associated dependent/beneficiary, investment and billing records where applicable).
Happens when you add dependents to vision and the vision has already been assigned. System is overwriting the enrollment without dependents with the enrollment that includes dependents.
000325 Multi Job Not Found.
A job record does not exist as of the event date specified on the BAS_ACTIVITY record.
A job record/row was deleted or There’s a mismatch in the Benefit Rcd Nbr/Empl Rcd in the Bas Activity table vs the Per Org Asgn table.
The system deletes the schedule ID from the bas activity, so it no longer appears on the Review Bas Activity page.
000326 Duplicate Manual Event.
A BAS_PARTIC record exists for the same manual event on the BAS_ACTIVITY record. The BAS_ACTIVITY was not processed and was not deleted. (MSGData1: Empl Rcd No, MSGData2:
Event Dt, MSGData3: Event Class)
Employees appeared on the BAS03 report. Unable to resolve/reprocess, no schedule ID. Delete the offending rows from the BAS_MESSAGE table via SQL.
An event already exists with the same emplid, benefit rcd nbr, event date and bas action. The system deletes the schedule ID from the bas activity, so it no longer appears on the Review Bas Activity page.
000327 No Job Data for Event.
The HR data required to process eligibility for the participant does not exist.
The event has been disconnected because an effective dated job or address row that was originally used to determine eligibility for the event no longer exists. REQUIRED ACTION only if the process status of the event is Finalized-Enrolled (FE or Enrolled) is to change the process indicator on the event to VOID and run the batch cobol process to back out any rows that the event posted to base benefits. The process status changes to “Re-enter.” Disconnected events cannot be processed other than to void finalized-enrolled events.
000328 Partic Eligibility has changed. The eligibility data has changed between benefit program assignment and option processing phases. Review the participant's HR data to determine if reprocessing is required. This is a student and does not have any qualifying appointments. Close the open event. Change flag(s) to processed.
000330 Current Coverage Ineligible. The employee is not eligible for the coverage in the base benefits tables. This may be either an error in the data load to the base benefits tables or an error in the eligibility rules.
000351 While processing eligibility for this event, none of the employee's jobs were evaluated, even though an eligibility rule contained job-level eligibility criteria. Check this employee's benefit system and "include for eligibility" flags to determine why no jobs were evaluated. This message will appear for each eligibility rule evaluated, containing job-level eligibility criteria.
000608 Minimum Number Covered Error. There are not enough dependents of this type of dependent and this coverage code. This happens when you enter party code 3 but only one dependent-won't let you save until you fix it. There are an insufficient number of dependents enrolled for the coverage code. The event needs to have election entry corrected to reflect the correct coverage code for the # of covered dependents.
000609 Maximum Number Covered Error Too many dependents were enrolled for the coverage code. The event needs to have election entry corrected to reflect the correct coverage code for the # of covered dependents.
000613 Future Dated Enrollment Exists. Informational only: The system encountered a new enrollment action for which a benefit enrollment record already exists with the future effective date. Correct accordingly. Enrollment dates need to be verified and corrected as needed.

End of Article

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Previous Article Benefits Audit Tables Process Guide
Next Article Delta Dental Interface User Guide