Review / Approval History

CHRS Benefits Daily Review and Troubleshooting User Guide

Table of Contents Page

1. Process Overview 5
2. Related Documentation 5
3. Daily Benefits Review - Job Aids 6
4. BAS003.SQR - Invalid Elections Report 6
   1. Report Description 6
   2. Recommended Use and Follow-up 6
   3. Things to Look For 6
   4. Online Processing Messages Page 8
   5. Navigation 8
   6. Sample Report 11
5. BAS008.SQR - Report on Flagged Items 11
   1. Report Description 11
   2. Recommended Use and Follow-up 12
   3. Things to Look For 13
   4. Navigation 14
   5. Sample Report 17
6. CSUBAS27.SQR – CSU Process Status Report 18
   1. Description 18
   2. Criteria 18
   3. Recommended Use and Follow-up 18
   4. Things to Look For 18
   5. Navigation 18
   6. Sample Report 21
   7. Process Statuses 21

Program Assignment 21

Prepare Options 22

Entering Elections 23

Example of a Prep Error 24

1. CSUBB010.SQR – Benefits Transaction Report 24
   1. Description 24
   2. Criteria 25
   3. Recommended Use and Follow-up 26
   4. Navigation 26
   5. Sample Report 28
2. CSUBAS30.SQR – CSU Benefits Termination Report 28
   1. Description 28

CHRS Benefits Daily Review and Troubleshooting User Guide

1. Criteria 29
2. Recommend Use and Follow-up 29
3. Navigation 30
4. Sample Report 32
5. CSUBAS30.SQR – CSU Job Change Prior to Ben Admin 32
   1. Description 32
   2. Criteria 32
   3. Recommended Use for Follow-Up 32
   4. Navigation 32
   5. Sample Report 35
6. Why Did a Benefit Terminate or Isn’t Correct Troubleshooting Checklist 35
7. Appendix A – Ben Admin Error Messages 39

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

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.

• Daily Review CSUBAS Logs and Reports
• Daily Review BA Baseline Queries

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.

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.

• 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.

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 , then go to Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Invalid Elections Rpt

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.

• 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 , then go to Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Report on Flagged Items

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.

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

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.

• 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

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.

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).

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 , then go to Menu > Benefits > Reports > CSU Benefits Reports

> CSU Benefits Transaction Rpt

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.

1. 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. The CSU Benefits Transaction Rpt page appears.

1. Enter your Business Unit.
2. The Default - 30-Days checkbox looks for Coverage Begin/End EFFDT equal to or less than 30 days from the report run 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.

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.

1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is

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.

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

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 , then go to Menu > Benefits > Reports > CSU Benefits Reports

> CSU Benefits Termination Rpt

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.

1. 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. The CSU Benefits Termination Rpt page appears.

1. Enter your Business Unit.
2. Select the Default – 30 Days checkbox if you want to run the report to check for Coverage Begin/End Effective Date or Coverage Elect Date equal to or less than 30 days from the report run 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.

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.

1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is

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.

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 , then go to Menu > Benefits > Reports > CSU Benefits Reports

> CSU Job Changes Prior BenAdmin

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.

1. 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.

The CSU Job Changes Prior BenAdmin page appears.

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.

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.

1. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is

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).

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.