Invalid Elections Report - BAS003.SQR is a delivered PeopleSoft report that lists all Benefit Administration (Ben Admin) errors and warnings by BAS Schedule ID after running the PSPBARUN process.

• The report shows the schedule ID, employee ID, error message, and cause of the error. Review this report each day and resolve all listed errors and warnings.

Review this report daily and resolve all issues. Be aware that resolved issues will remain on the report until the PSPBARUN process is run again for the related BAS Schedule ID.

Assign None (AN) errors

• Occur when Ben Admin cannot determine the employee’s benefit program.
• These should not normally occur.
• To fix:
  1. Review the employee’s Job Data.
  2. Correct any errors.
  3. In On Demand Event Maintenance, enter “A” next to the Reprocess button, then click Reprocess.
  4. If the issue remains, submit a ServiceNow ticket for CMS review.
• Note: AN events become Finalized None (FN) after the next PSPBARUN run.

Assign Errors (AE)

• Caused by incorrect Job Data or configuration issues.
• To fix:
  • If not an eBenefits Self Service event: Reprocess using “A” as above.
  • If an eBenefits Self Service event: Reprocess using “A,” confirm the status is Prepared, and advise the employee to continue.
  • If the employee cannot access the corrected event, have them cancel the transaction in eBenefits and start a new one.

Prep Errors (PE)

• Similar to AE, caused by incorrect Job Data or configuration issues.
• To fix:
  • If not an eBenefits Self Service event: Reprocess using “A.”
  • If an eBenefits Self Service event: Reprocess using “A,” confirm the status is Prepared, and advise the employee to continue.
  • If the employee cannot access the corrected event, have them cancel and create a new transaction.

Election Errors (EE)

• Caused by incorrect election data.
• To fix:
  • If not an eBenefits Self Service event: Open Election Entry in On Demand Event Maintenance, correct the error, and save.
  • If an eBenefits Self Service event: Use Election Entry to correct the error and enter the required permitting event codes.
    • Do not reprocess back before “Re-enter,” or the submission date will be lost.
    • The submission date is used for eSignature, Perm Event HBO Received Date, and CSU_BA_EVT_DT processing.

Additional Notes

• No changes are needed in Event Status Update unless AN errors have become FN errors and need to be reset.
• This report does not include errors from disconnected events.

The Invalid Elections Report is not part of the nightly CSUBASOE job schedule in CHRS. You must run this report manually each day (ad-hoc) to review and resolve Ben Admin processing errors.

• Navigation:
  • NavBar > Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Invalid Elections Rpt

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

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

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.
6. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Sucess
7. Click on the Details link.

1. Click on the Details link.
2. The Process Detail page appears. Click on the View Log/Trace link.

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.
3. Note that resolved errors do not fall off the report or the Processing Messages page after they are resolved until PSPBARUN is run again for the applicable Schedule ID.

• This report lists BAS events that have been flagged and require daily review and resolution.
• Flagged BAS events may occur when:
  1. Job, Address, or Union eligibility information has changed and may affect benefits eligibility (requires review and possible reprocessing).
  2. Events have been processed out of sequence and may require reprocessing or voiding.
  3. Events have been disconnected during processing and need review and resolution.
• The Report on Flagged Items is a delivered PeopleSoft report (BAS008.SQR) that produces, by BAS Schedule ID, a detailed listing of all BAS events with one or more of the following flags:
  • Address Eligibility Changed
  • MultiJob Indicator Changed
  • Job Eligibility Changed
  • Event Out of Sequence
  • Event Disconnected
• The report includes the Schedule ID, employee ID, error description, and cause of the error. Review and resolve all items on this report each day.

• Review and resolve items on this report daily.
• Audit flagged events and reprocess as needed.
  • Use the Reprocessing a CHRS BAS Event cheat sheet for guidance.
  • For eBenefits ESS events, also use the ESS OK to Reprocess Cheat Sheet to confirm whether reprocessing is allowed.

Address Eligibility Change Flag

• Check if the employee’s home state or zip code changed. Mailing address changes do not affect eligibility.
• If no state/zip change → Uncheck the flag and save.
• If state/zip changed → Reprocess the BAS event. This may require a new benefit plan election.

Job Eligibility Change Flag

• Review Job Data fields that impact eligibility (e.g., location, employee class, FLSA status, pay group, union code, FTE, benefit program, BAS Group ID).
• If no eligibility impact → Uncheck the flag and save.
• If eligibility impact → Reprocess the BAS event.

MultiJob Eligibility Change Flag

• Review all active jobs and key Job Data fields for the employee (same fields as Job Eligibility Change).
• If no eligibility impact → Uncheck the flag and save.
• If eligibility impact → Reprocess the BAS event.

Important Notes

• Always reference the Reprocessing a CHRS BAS Event and ESS OK to Reprocess Cheat Sheets before reprocessing.
• These resources outline when reprocessing is safe and what steps to take if it is not allowed.

Address Eligibility Changed Flag

• Triggered when an address change impacts eligibility (state or zip code).
• Example: A 9/1/2003 BAS event exists, and a change of address is entered on 8/15/2003. The later BAS event (9/1/2003) will show this flag.
• Action: Reprocess the event if the address change affects benefit eligibility.

MultiJob Indicator Changed Flag

• Triggered when Multiple Jobs functionality is used and a change impacts eligibility across jobs.
• Example: Adding, deleting, or modifying job data after the BAS event began processing.
• Action: Reprocess the BAS event if eligibility is impacted by the change.

Job Eligibility Changed Flag

• Triggered when a correction is made to Job Data that impacts benefits eligibility.
• Example: A change in employee class, union code, pay group, FTE, or other eligibility-related fields.
• Action: Reprocess the BAS event if the change affects benefits eligibility.

Event Disconnected Flag

• Triggered when a BAS event is “broken” because the underlying HR data that created it has changed or been deleted.
• Causes:
  • Job Data effective date was changed.
  • Action or Action/Reason code was changed.
  • Job Data row was deleted.
• Action:
  • Analyze each case individually.
  • If disconnected after finalization, void the event. Note: elections may remain on Base Benefits tables and may require Correction mode to clear.
  • Be aware: If a disconnected event has a status of Closed (with a greyed-out Event Status box), it cannot be reprocessed or voided.

Event Out of Sequence Flag

• Triggered when BAS events are processed out of chronological order.
• Example: An employee has a future-dated OE BAS event in Prepared status, then later creates a Life Event (e.g., birth of a child) with an earlier effective date. The Life Event processes first, closing the OE event, which then requires reprocessing to capture the dependent.
• Action: Reprocess the OE BAS event so the new dependent and benefit changes are included.

The Report on Flagged Items is not part of the nightly CSUBASOE job schedule in CHRS. You must run this report manually each day (ad-hoc) to review and resolve Ben Admin processing errors.

• Navigation:
  • NavBar > Menu > Benefits > Manage Automated Enrollment > Investigate Exceptions > Report on Flagged Items

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

• 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 Report On Flagged Items page appears.

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.

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.
6. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success
   • Click on the Details link.

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.

This report lists all open BAS events for a specific BAS Schedule ID. It is a customized version of the delivered BAS27.sqr and excludes events with a status of Void, Closed, or Disconnected.

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 this report to monitor OE BAS processing.
• Identify BAS events that are open but not finalizing in a timely manner.
• Be aware that eBenefits ESS BAS events automatically expire after 1, 30, or 60 days depending on the event type.
• For eBenefits ESS BAS events, also run the CSU_BAS_SS_EVENTS and CSU_BAS_SS_NT queries (see the Daily Review BA Baseline Queries job aid).
• Some eBenefits BAS events may require direct follow-up with the employee to ensure the process is completed.

• Election Error (EE) or Prep Error (PE)
  • These events are in an error status and should also appear on the BAS003 Invalid Elections Report.
  • Action: Review and resolve using the BAS003 report guidance.
• Assigned (AS) Status
  • These events are not errors. They occur when a new BAS event starts while another event for the employee is still in process.
  • The new event will remain at Assigned until the current event finishes processing. Once the current event is complete, the Assigned event will automatically continue processing.
  • Action: No immediate action required—monitor to ensure the event resumes after the earlier one is complete.

The Process Status Report is not part of the nightly CSUBASOE job schedule in CHRS. Run this report manually each day (ad-hoc) to review and resolve Ben Admin processing errors.

• Navigation:
  • NavBar > Menu > Benefits > Reports > CSU Benefits Reports

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

• 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 Process Status Rpt page appears.

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.

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.
6. Locate your job on the Process List, then click on the Refresh button until the job’s Run Status is Success
7. Click on the Details link.
   • The Process Detail page appears. Click on the View Log/Trace link.

1. Click on the Details link.
2. The Process Detail page appears. Click on the View Log/Trace link.

• The View Log/Trace page appears. Click on the link that ends in .PDF as this is the report.

End of Article