Benefits Troubleshooting Guide

Updated on Sep 12, 2025

The purpose of this document is to assist campuses with Benefits related issues.

Shared Employee

Employee no longer active in either campuses

Example:

Fullerton employee transferred to SBU, no break in service-San Bernardino is now the benefits primary campus. San Bernardino corrected Dental history with no issue-San Bernardino is unable to adjust the mandatory benefits history for LIFE and LTD BASE BENEFITS rows to 1/1/20 since the 1/1/20 date precedes San Bernardino hire date. Fullerton cannot access the Base Benefits pages for the employee since they are no longer the benefits primary job campus.

Steps to resolve:

Delete 6/10/2023 termination row in Employee Record 0 (Fullerton) and run primary benefits job to move primary benefits job to Fullerton.
Fullerton enters rows in LIFE and LTD.
Re-enter termination row on Employee Record 0 and re-run primary benefits job to move primary benefits job back to SBU.

Campus can refer to ServiceNow ticket INC0574371

Active at both campuses

Example:

San Bernardino and Fullerton shared employee where Fullerton has the Benefit Primary Job (BPJ). San Bernardino must work with Fullerton to adjust the mandatory benefits EFFDTs - San Bernardino can’t modify Base Benefits since Fullerton is BPJ. Fullerton is unable to modify Vision and LIFE EFFDT to 2/1/23, and LTD EFFDT to 1/20/23 due to HIRE date error-date trying to enter precedes San Bernardino hire date.

Steps to resolve:

San Bernardino can increase the FTE on the 8/19/2024 row to 1 FTE and Run Primary Benefits Job.
Make corrections to Life and LTD.
Fix the FTE on the 8/19/2025 row back to .6 and re-run primary benefits job.

Campus can refer to ServiceNow ticket INC0574371

Active at one campus and inactive at another

Example:

Transferred to Fullerton, no break in service- Fullerton is now Benefits Primary Job (BPJ). San Bernardino tried to work with Fullerton to adjust core and mandatory benefits history – San Bernardino can’t modify Base Benefits since Fullerton is BPJ. Fullerton is unable to add Plan Type 10, 11, 14, 23, 31 San Bernardino history for 2022 and 2021 due to HIRE date error-date trying to enter precedes San Bernardino hire date.

Steps to resolve:

San Bernardino remove the termination row (on the ServiceNow incident, refer to the EMPLID) on EMPLD RCD 1 dated 08/25/2023 and Run primary benefits job to move it to San Bernardino.
Build base benefits correctly.
Re-add termination row to employee record 1 with a date of 08/25/2023. Re-run primary benefits job to switch it back to Fullerton.

Campus can refer to ServiceNow ticket INC0574371

Active at one campus and inactive at another (with previous concurrent jobs)

Example:

Employee has been enrolled in Benefits continuously at Sacramento since 12/01/2015. No benefit enrollment rows converted. When attempting to enter the rows we get an error message due to the enrollment being prior to hire date. Original Hire date is driven by Stanislaus position and shows 08/23/2023. Sacramento was unable to enter enrollment for the employee.

Steps to resolve:

Sacramento to Change hire date on Employee RCD 3 to 11/23/2015 (as that is Benefits Primary Job).
In base benefit tables, rebuild the history as it should be
Change the hire date on Employee Record 3 back to the original one of 08/23/2023

Campus can refer to ServiceNow ticket INC0632013

Event Class

High Level Cheatsheet

Event Class Cheatsheet06252025.xlsx

eBenefits ESS Event Classes OK to Reprocess

eBenefits ESS BAS events cannot be reprocessed in certain situations because you'll overwrite (lose) vital submission date processing data, specifically, you'll lose the employee's submit date (Election Received Date). The Election Received Date used for the eSignature date on forms, the Perm Event HBO Received Date, and is also used by the nightly GRP 95 process CSU_BA_EVT_DT to change the event class event date for submission date processing.

Use this to see what and when you can reprocess for eBenefits ESS BAS events or if it’s better to void the ESS BAS events and re-enter the enrollments using the HBE and/or FSA BAS events via the On Demand Event Maintenance page in CHRS.

Use the Event Class and Process Status to guide your next steps.

eBenefits ESS OK to Reprocess Cheatsheet111124.pdf

Event Class is - ADP,BIR,DGC,DLC,DIV,DRP,EGC,ELC,LTE,MAR,NEW,PCR

Process Status: Assigned

Process Status Code: AS

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: N/A

Process Status: Assign Error

Process Status Code: AE

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign Benefit Program.

Process Status: Assign None

Process Status Code: AN

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign Benefit Program.

Process Status: Prepare

Process Status Code: PR

Event Status is: Open

OK to Reprocess: Yes

Conditions: N/A

Notes: Can reprocess back to Assign Benefit Program.

Process Status: Prepare Error

Process Status Code: PE

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign Benefit Program.

Process Status: Notified

Process Status Code: NT

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Notes: N/A

Process Status: Entered

Process Status Code: ET

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Notes: Do not reprocess to Assign Benefit Program or Prepare Options-you'll lose the employee's submit date (Election Received Date). Election Received Date used for eSignature date on forms, Perm Event HBO Received Date, and is used by nightly GRP 95 process CSU_BA_EVT_DT to change the event class event date for submission date processing.

Process Status: Election Error

Process Status Code: EE

Event Status is: Open

OK to Reprocess: Only reprocess to Re-enter status

Conditions: N/A

Process Status: Re-Enter

Process Status Code: RE

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Process Status: Finalized None

Process Status Code: FA

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Notes: This scenario should never occur but if it does, check to see if you have data issues on the employment record(s) in Job Data. If no, create a Service Now ticket for CMS-Benefits to determine if there is a Benefits Administration configuration error in PeopleSoft.

Process Status: Finalized Enrolled

Process Status Code: FE

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Notes: Reprocess first back to 'Re-enter' and write down the employee's election, then reprocess back to 'A' (Assign Benefit Program). Then you'll need to re-enter elections. The system overwrites the Election Received Date when you reprocess. The the Election Received Date is used as the employee's esignature date on enrollment forms. The original processing dates are preserved in the Ben Admin audit tables and can be viewed using query CSU_BAS_EVENT_CLASS_HISTORY_SUMMARY, available in the Queries menu in the CSU Benefits Administrator tile, if needed for audits and/or research. The query shows the employee's original submit date (Election Received Date). Know that the new Election Received Date is used for eSignature date on forms after reprocessing instead of the original Election Received Date.

Process Status: Finalized Prep None

Process Status Code: FP

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Notes: N/A

Event Class is - AD1,BI1,DG1,DL1,DI1,EG1,EL1,MA1,NW1,PC1

Process Status: Assigned

Process Status Code: AS

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Assign Error

Process Status Code: AE

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Assign None

Process Status Code: AN

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Prepared

Process Status Code: PR

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Prepare Error

Process Status Code: PE

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Notified

Process Status Code: FP

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: System creates event once original event is at a ET or RE status and the Finalize/Apply Defaults flag is checked.

Process Status: Entered

Process Status Code: ET

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Process Status: Election Error

Process Status Code: EE

Event Status is: Open

OK to Reprocess: No

Conditions: Correct election issue in ODEM and save. Do not finalize the enrollment in ODEM

Process Status: Re-Enter

Process Status Code: RE

Event Status is: N/A

OK to Reprocess: No

Conditions: N/A

Process Status: Finalized None

Process Status Code: FA

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Process Status: Finalized Enrolled

Process Status Code: FE

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Process Status: Finalized Prep None

Process Status Code: FP

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Notes: N/A

Event Class is - OE

Process Status: Assigned

Process Status Code: AS

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes: N/A

Process Status: Assign Error

Process Status Code: AE

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign.

Process Status: Assign None

Process Status Code: AN

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign.

Process Status: Prepared

Process Status Code: PR

Event Status is: Open

OK to Reprocess: Yes

Conditions: N/A

Notes: Can reprocess back to Assign.

Process Status: Prepare Error

Process Status Code: PE

Event Status is: Open

OK to Reprocess: Yes

Conditions: Need to correct error first.

Notes: Can reprocess back to Assign.

Process Status: Notified

Process Status Code: NT

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Notes: N/A

Process Status: Entered

Process Status Code: ET

Event Status is: Open

OK to Reprocess: No

Conditions: N/A

Notes: Know that you'll lose the employee's submit date (Election Received Date) if you reprocess to Assign or Prepare. Election Received Date is used for eSignature date on forms and to initially populate the Perm Event HBO Received Date. This could be an audit issue if we don't have audit tables. You'll need to re-enter elections.

Process Status: Election Error

Process Status Code: EE

Event Status is: Open

OK to Reprocess: N/A

Conditions: N/A

Notes:N/A

Process Status: Re-Enter

Process Status Code: RE

Event Status is: N/A

OK to Reprocess: Yes

Conditions: N/A

Process Status: Finalized None

Process Status Code: FA

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Process Status: Finalized Enrolled

Process Status Code: FE

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Process Status: Finalized Prep None

Process Status Code: FP

Event Status is: Closed

OK to Reprocess: Yes

Conditions: N/A

Notes: N/A

Event Date Rules-Like Rows Created Schedule

Submission Date Rules-Like Rows Created Schedu.pdf

Can Add in Review BAS Activity

Yes

ACM- Affordable Care Act
CNC- Cancel all Coverage
DEA- Death of a Dependent
FSA- FSA Enrollment
HBE- Health Benefit Enrollment
LIF- Life Enrollment
LVE- Leave of Absence - Unpaid
NEW- New Hire Newly Eligible
REH- Rehire
RFL- Return from Leave
T90- Transfer to 9.0 Campus
T92- Transfer from 9.0 Campus
TBC - Time Base Change

ACT - Action Needs Review
AD1 - Adoption Plus One Month
ADP - Adoption
ADR - Address Change
BI1 - Birth Plus One Month
BIR - Birth
DG1 - Dependent Gains Coverage +1
DGC - Dependent Gains Coverage Extn
DI1 - Divorced Plus One Month
DIV - Divorce
DL1 - Dependent Loses Coverage +1
DLC - Dependent Loses Coverage Extn
DRP - Drop all Dependents
EG1 - Employee Gains Cvg+One
EGC - Employee Gains Coverage Extn
EL1 - Employee Lost Cvg+1
ELC - Employee Lost Coverage Extn
HIR - New Hire
LTE - Late Enrollment
MA1 - Marriage Plus One Mnth
MAR - Marriage
MSC - Miscellaneous Change
NW1 - New Hire Plus One Month
OE - Open Enrollment
OVR - Override Benefit Eligibility
PC1 - Parent/Child Relationship 1mth
SNP - Snapshot
TER - Termination

Can CSU_BA_EV_ DT Auto Enroll/Close BAS event when 'PR' and 'ET'

Yes at day 31

Yes at day 61

CSU_BA_EV_ DT Auto Void BAS event when 'RE'

Yes at day 31

Yes at day 61

Delete Activity

Delete Activity Guide Cheat Sheet03062024 (1).pdf

AG Page Status Codes:
1 – Assigned
2 – In Progress
4 – Completed

Delete AG - Age-Out LTE with BAS Event

AG Template: EF_L1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: Not equal to Void
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS and BASPARTIC.EVENT_DT for EE
Days: equal/ greater than 31
Delete Reason and Issue Reason Report Message: Age Out with BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event not Finalized (generally Prepared) and AG not deleted

Delete AG - Age-Out DRP with BAS Event

AG Template: EF_E1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: Not equal to Void
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS and BASPARTIC.EVENT_DT for EE
Days: equal/ greater than 2
Delete Reason and Issue Reason Report Message: Age Out with BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event not Finalized (generally Prepared) and AG not deleted

Delete AG - Age-Out ADP, BIR, DIV, DGC, DLC, EGC, ELC, MAR, PCR with BAS Event

AG Template: EF_A2FL, EF_B4FL, EF_C1FL, EF_D3FL, EF_G1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: Not equal to Void
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS and BASPARTIC.EVENT_DT for EE
Days: equal/ greater than 61
Delete Reason and Issue Reason Report Message: Age Out with BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event not Finalized (generally Prepared) and AG not deleted

Delete AG - Age-Out LTE - No BAS Event

AG Template: EF_L1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS for EE
Days: equal/ greater than 31
Delete Reason and Issue Reason Report Message: Age Out without BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event Finalized and AG not completed - also check if something in BAS_ACTIVITY (if %SqlRows= 0 on process log means nothing found in BAS_ACTIVITY)

Delete AG - Age-Out DRP - No BAS Event

AG Template: EF_E1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS for EE
Days: equal/ greater than 2
Delete Reason and Issue Reason Report Message: Age Out without BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event Finalized and AG not completed - also check if something in BAS_ACTIVITY (if %SqlRows= 0 on process log means nothing found in BAS_ACTIVITY)

Delete AG - Age-Out ADP, BIR, DIV, DGC, DLC, EGC, ELC, MAR, PCR - No BAS Event

AG Template: EF_A2FL, EF_B4FL, EF_C1FL, EF_D3FL, EF_G1FL, EF_M4FL, EF_P1FL, EF_V1FL, EF_X1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS for EE
Days: equal/ greater than 61
Delete Reason and Issue Reason Report Message: Age Out without BAS Event
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event Finalized and AG not completed - also check if something in BAS_ACTIVITY (if %SqlRows= 0 on process log means nothing found in BAS_ACTIVITY)BAS event Finalized and AG not completed - also check if something in BAS_ACTIVITY (if %SqlRows= 0 on process log means nothing found in BAS_ACTIVITY)

Delete AG - Age-Out LTE - No BAS Event

AG Template: EF_L1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS; BAS_ACTIVITY. BAS_ACTION and EVENT_DT for EE
Days: equal/ greater than 31
Delete Reason and Issue Reason Report Message: Age Out with BAS ACTION
Delete AG process deletes BAS event: Yes from BAS_ACTIVITY
Update Allow in ESS Flag: N/A
Scenario Description: Scenario occurs if age out occurs before PSPBARUN prepares BAS _ACTION

Delete AG - Age-Out DRP - No BAS Event

AG Template: EF_E1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS; BAS_ACTIVITY. BAS_ACTION and EVENT_DT for EE
Days: equal/ greater than 2
Delete Reason and Issue Reason Report Message: Age Out with BAS ACTION
Delete AG process deletes BAS event: Yes from BAS_ACTIVITY
Update Allow in ESS Flag: N/A
Scenario Description: Scenario occurs if age out occurs before PSPBARUN prepares BAS _ACTION

Delete AG - Age-Out ADP, BIR, DIV, DGC, DLC, EGC, ELC, MAR, PCR - No BAS Event

AG Template: EF_A2FL, EF_B4FL, EF_C1FL, EF_D3FL, EF_G1FL, EF_M4FL, EF_P1FL, EF_V1FL, EF_X1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: W3EB_LE_STATE92. ACTION_DT_SS; BAS_ACTIVITY. BAS_ACTION and EVENT_DT for EE
Days: equal/ greater than 61
Delete Reason and Issue Reason Report Message: Age Out with BAS ACTION
Delete AG process deletes BAS event: Yes from BAS_ACTIVITY
Update Allow in ESS Flag: N/A
Scenario Description: Scenario occurs if age out occurs before PSPBARUN prepares BAS _ACTION

Delete AG - Finalized OE BAS Event During OE Period

AG Template: ENROLLC
AG Welcome page: N/A
AG Benefits Enrollment page: 4
AG Dep/Ben Coverage page: N/A
AG eSignature page: 4
AG Summary page: 2,1,4
BAS Event Class Process Status: FE
BAS Event Class Event Status: C (Closed)
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Finalized OE event and Signed Activity Guide
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: Update to N
Scenario Description: BAS event Finalized and AG not completed

Delete AG - Finalized OE BAS Event AFTER OE Period

AG Template: ENROLLC
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: 2, 1, 4
BAS Event Class Process Status: FE
BAS Event Class Event Status: C (Closed)
BAS Election Source: N
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Finalized OE Event None Entered Election Source
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: BAS event Finalized and AG not completed

Delete AG - Voided OE BAS Event (note that the process checks for voided bas events first)

AG Template: ENROLLC
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: V (Void)
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Voided BAS Event
Delete AG process deletes BAS event: Yes from BAS_PARTIC, et al
Update Allow in ESS Flag: N/A
Scenario Description: BAS event voided and AG open

Delete AG - Voided ADP, BIR, DIV, DGC, DLC, DRP, EGC, ELC, LTE, MAR and PCR BAS Event (note that the process checks for voided bas events first)

AG Template: EF_A2FL, EF_B4FL, EF_C1FL, EF_D3FL, EF_G1FL, EF_M4FL, EF_P1FL, EF_V1FL, EF_X1FL, EF_L1FL and EF_E1FL
AG Welcome page: N/A
AG Benefits Enrollment page: N/A
AG Dep/Ben Coverage page: N/A
AG eSignature page: N/A
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: V (Void)
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Voided BAS Event
Delete AG process deletes BAS event: Yes from BAS_PARTIC, et al
Update Allow in ESS Flag: N/A
Scenario Description: BAS event voided and AG open

Issue AG - Missing eSIG OE

AG Template: ENROLLC
AG Welcome page: N/A
AG Benefits Enrollment page: 4
AG Dep/Ben Coverage page: N/A
AG eSignature page: 1,2
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Missing Electronic Signature
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: Submitted enrollment but esignature missing

Issue AG - Missing eSIG ADP, BIR, DIV, DGC, DLC, DRP, EGC, ELC, LTE, MAR and PCR BAS Event

AG Template: EF_A2FL, EF_B4FL, EF_C1FL, EF_D3FL, EF_G1FL, EF_M4FL, EF_P1FL, EF_V1FL, EF_X1FL
AG Welcome page: N/A
AG Benefits Enrollment page: 4
AG Dep/Ben Coverage page: N/A
AG eSignature page: 1,2
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Missing Electronic Signature
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: Submitted enrollment but esignature missing

Issue AG - Missing eSIG LTE BAS Event

AG Template: EF_L1FL
AG Welcome page: N/A
AG Benefits Enrollment page: 4
AG Dep/Ben Coverage page: N/A
AG eSignature page: 1,2
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Missing Electronic Signature
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: Submitted enrollment but esignature missing

Issue AG - Missing eSIG DRP BAS Event

AG Template: EF_E1FL
AG Welcome page: N/A
AG Benefits Enrollment page: 4
AG Dep/Ben Coverage page: N/A
AG eSignature page: 1,2
AG Summary page: N/A
BAS Event Class Process Status: N/A
BAS Event Class Event Status: N/A
BAS Election Source: N/A
Date Used: N/A
Days: N/A
Delete Reason and Issue Reason Report Message: Missing Electronic Signature
Delete AG process deletes BAS event: No
Update Allow in ESS Flag: N/A
Scenario Description: Submitted enrollment but esignature missing

When Benefits Terminate or Are Incorrect

Pre-Ticket Steps

Use the following steps to troubleshoot why a benefit is incorrect or has terminated for an employee or dependent.

When researching, do not assume the Base Benefit tables are correct, especially if the employee has unresolved flagged BAS events. These flags can result from retroactive changes, late paperwork (new hires, rehires, transfers, terminations, life events), future-dated enrollments, corrections in Job Data, selective processing by Benefits Officers, or daily BAS events created before prior ones are resolved.

Base Benefit tables may be inaccurate for employees with flagged events, particularly Out of Sequence events. If BAS events are processed in the wrong order, benefit enrollments in the Base Benefit tables will also be incorrect.

Is the employee or dependent missing from the interface file for the applicable time period?

Benefits may terminate or be missing from the interface file for several reasons:

Job termination, unpaid leave, short work break, or employee waiver/life event (e.g., marriage, dependent gains coverage).
Dependent aged out (26+), though adult dependents are not currently configured to age out in CHRS.
Delayed entry of benefit changes when using the multiple permitting event code workaround (review via Health Benefits; note Election Date is when processed in Ben Admin).
Workaround timing issues, as daily enrollments can overwrite Ben Admin/Base Benefit tables. Review with Ben Admin and Base Benefit Audit queries.
Interface date earlier than the Health Benefits Election Date.
Interface selection criteria not met (e.g., missing gender, out-of-state address).

Is the employee’s Payroll Status Leave of Absence, Short Work Break, Terminated, Retired, or Deceased?

If an employee’s Payroll Status changes, their benefits may be waived or terminated. In some cases, a Suspended status can also result in cancelled benefits in CHRS.

Review BAS events and changes: Benefits > Manage Automated Enrollment > Employee Event Details (see Cheat Sheet).
Check overall enrollments: Benefits > Review Employee Benefits > CSU Benefits Summary.
Review detailed enrollments: Base Benefit tables (Health, Disability, Life/AD&D, Spending Accounts).
Did the employee voluntarily waive benefits while on leave, short work break, or due to a life event? Confirm via Employee Event Details.

What is the employee’s Benefits Employee Status?

Some benefits terminate based on Benefits Employee Status. If the status is Leave of Absence, Terminated, Retired, or Deceased, benefits may be waived or terminated. Employees may also voluntarily waive benefits during unpaid leave, short work breaks, or life events. Review BAS events in Benefits > Manage Automated Enrollment > Employee Event Details (see Cheat Sheet).

Did the employee lose benefits eligibility for the applicable time period?

Depending on the situation, additional questions may need to be asked:

Did the employee lose eligibility due to ACA?
Did the employee end another CSU job?
Did the employee’s Benefits Primary Job change? (Benefits > Maintain Primary Jobs > Maintain Flags)
Did the employee waive benefits while on unpaid leave, short work break, or a life event? (Benefits > Manage Automated Enrollment > Review Processing Results > Employee Event Details)
Did the employee’s work location or address change to outside a geographic eligibility area? (Contact Information & Work Location pages; review Geographic Location Elig Table)
Did Elig Fld 1–5 values change for the employee’s Benefits Primary Job? (Job Data > Benefits Program Participation)

Did the dependent lose benefit eligibility for the applicable time period?

Depending on the situation, additional questions may need to be asked:

Did the dependent age out (26 for a qualified child)? (Benefits > Employee/Dependent Info > Update Dependent/Beneficiary) — note: adult dependents are not currently set to age out in CHRS.
Was this a conversion issue from HR9.0 (dependent missing or dropped in HR9.0 to CHRS)? Compare HR9.0, campus conversion DB, and CHRS.
Is the dependent disabled but not flagged as disabled for the time period? (Update Dependent/Beneficiary)
Did the dependent’s relationship change (e.g., spouse → ex-spouse, domestic partner → ex-domestic partner)? (Update Dependent/Beneficiary)
Did Elig Fld 1–5 values change for the employee’s Benefits Primary Job? (Job Data > Benefits Program Participation)

Did the employee recently transfer between CSU campuses?

For example, the employee terminated at Fullerton and transferred to Stanislaus.

Review Job Data and check the action/action-reason combinations used for termination and hire rows. Benefits may have ended incorrectly due to how these rows were entered or because of gaps in CSU business processes. If so, coordinate with CMS-Benefits and Systemwide HR (SWHR) to determine if CHRS configuration or business process changes are needed.

For employees transferring between CSU locations, also review Employee Event Detail > Plan Type to confirm Ben Admin changes (see the Employee BAS Event Details Cheat Sheet for guidance).

Are there flagged BAS events for the applicable time period?

Flagged BAS events often result from retroactive changes in CHRS (e.g., late hires, rehires, transfers, terminations), Job Data corrections, selective processing by Benefits Officers, or daily BAS events generated before prior events are resolved.

To investigate:

Go to Benefits > Manage Automated Enrollment > Events > Update Event Status or Review Processing Results > Employee Event Detail to check for flagged BAS events.
Review flags:
- Out of Sequence → Events must be reprocessed in the correct order (see Reprocessing Cheat Sheets).
- Address Eligibility Changed → Check Modify a Person for home state/zip changes and Job Data for work location changes. Moves may affect eligibility for regional plans.
- Job Eligibility Changed → In Job Data, review fields such as Benefits Employee Status, Location, Empl_Class, Employee Type, FTE, Union Code, Pay Group, and Elig Flds 1–9.
- Multi Job Indicator Changed → Review the same Job Data fields across all active jobs.

Notes:

CSU uses the following fields in benefit eligibility rules: Benefits Employee Status, Location, Empl_Class, Employee Type, FTE, Company Code, Pay Group, Union Code, Elig Fld 1 (Duration of Appointment), Elig Fld 2 (Job Code), Elig Fld 3 (ACA Eligible), and Elig Fld 5 (After-tax Medical).
Base Benefit tables (Health, Disability, Life/AD&D, Spending Accounts) may be incorrect for flagged BAS events, especially Out of Sequence events.

Were BAS events processed or reprocess in the incorrect order for the applicable time period?

Processing BAS events out of order can incorrectly terminate benefits. Delivered PeopleSoft does not show the exact order of past manual processing, though you can use Ben Admin and Base Benefit Audit table queries (via the CSU Benefits Administrator Tile or Query Viewer) for partial insight. For audit table use, see the CHRS Benefits Audit Table User Guide.

The best solution is to reprocess BAS events in the correct order:

By Event Date – Process from oldest to newest (e.g., 1/1/2022 before 2/1/2022).
Check Event Date in: Benefits > Manage Automated Enrollment > Events > Update Event Status or the Event Status Update button in On Demand Event Maintenance.
By Event Priority – For events on the same date, process in order from lowest to highest priority (e.g., 35 → 45 → 200 → 375).
Check Event Priority in the same pages above.
By Event ID – For events with the same date and priority, process in ascending Event ID order (e.g., 1 → 2 → 3).
Check Event ID in the same pages above.

Possible CSU Benefit configuration issue?

There are numerous delivered and CSU-custom eBenefits, Ben Admin, and Base Benefit configuration pages. If you suspect a CHRS Benefits configuration issue, submit a ServiceNow ticket for CMS-Benefits to review.

Warnings and Errors

General

Refer to these error messages to guide resolution efforts.

These messages may differ based on the scenario, as they are only examples of what might appear. If the message you received is not listed, a ServiceNow ticket may be required.

The deduction code displayed below was not found in the deduction table. (Message ID: 000005)

Campus Action:

Confirm that the deduction code is included in the benefits program and properly defined with the correct effective date. If any changes are needed, submit a ServiceNow ticket to request the modification, and once the ticket is resolved, rerun the report.

CMS- Benefits Action:

In response to a ServiceNow ticket, review the current effective date for the deduction code, confirm the correct effective date, and coordinate with CHRS Operations to update it.

Navigation: Menu > Setup HCM > Product Related > Payroll for North America > Deductions > Deduction Table

The pay group displayed below was found but is currently inactive. (Message ID: 000011)

Campus Action:

Review the employee’s Paygroup in Job Data.
Check the Paygroup Table to confirm whether the paygroup is valid.
If invalid, update the employee’s paygroup to ACD, MST, POS, or STU as appropriate.
Rerun the BenAdmin process.

Error only appears due to conversion for implementing campuses.

The pay group displayed below was not found in the pay group table. (Message ID: 000014)

Campus Action:

Review the employee’s Paygroup in Job Data.
Check the Paygroup Table to confirm whether the paygroup is valid.
If invalid, update the employee’s paygroup to ACD, MST, POS, or STU as appropriate.
Rerun the BenAdmin process.

Error only appears due to conversion for implementing campuses.

The pay calendar entry displayed below was not found in the pay calendar table. (Message ID: 000015)

Campus Action:

Review the Balance ID and Pay Calendar for the selected range. If updates are required, coordinate with the appropriate team members to implement the changes, then rerun BenAdmin.

Job Aid - Create Balance IDs
Job Aid - Create Pay Run ID
Job Aid - Create Pay Calendars

The company displayed below was not found in the company table (Message ID: 000023)

Campus Action:

Open a ServiceNow ticket, as this issue may be caused by the value used by the campus in HR 9.0 not matching the standard value in CHRS.

Error only appears due to conversion for implementing campuses.

The company displayed below was found but is currently inactive. (Message ID: 000024)

Campus Action:

Open a ServiceNow ticket, as this issue may be caused by the value used by the campus in HR 9.0 not matching the standard value in CHRS.

Error only appears due to conversion for implementing campuses.

The benefit plan displayed below was not found in the appropriate benefit table. (Message ID: 000027)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Prep Error' procedure.

An age-graded rate was not found for the employee's category. (Message ID: 000030)

Suggested Resolution:

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
erun the BenAdmin process following the 'Prep Error' procedure.

The Coverage Group for the Life/ADD plan was not found. (Message ID: 000039)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Prep Error' procedure.

The form displayed below was not found in the Form Table. (Message ID: 000056)

Suggested Resolution:

Review the Form Table for the form ID specified.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

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. (Message ID: 000070)

Suggested Resolution:

Review the associate’s Personal Data page to ensure that a birth date is specified on the page.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

The Benefit Program defined for this employee was not found. (Message ID: 000087)

Suggested Resolution:

Review the Ben Prog Partic record for the associate
then the Benefit / Deduction Program Table for the specified program.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

The Benefit Program defined for this employee was inactive for the current check date. (Message ID: 000088)

Suggested Resolution:

Review the Benefit / Deduction Program Table status for the program specified.
Correct if appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure

The Benefit Plan / Deduction Code is not found for the Benefit Program defined for this employee. (Message ID: 000089)

Suggested Resolution:

Review the Benefit / Deduction Program Table status for the program specified.
Correct if appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

The Calculation Rules table was not found for the Benefit defined. (Message ID: 000090)

Suggested Resolution:

Review the Benefit / Deduction Program Table for the specified calc rules ID.
Correct if appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

The Service Rate Table named below was not found in the database. (Message ID: 000099)

Suggested Resolution:

Review the Service Rate Table for the specified service rate ID.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

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. (Message ID: 000100)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Prep Error' procedure.

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) (Message ID: 000128)

Suggested Resolution:

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.

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 currentPS_Ben_Prog_Partic record was found (default Hire record is missing). (Message ID: 000129)

Suggested Resolution:

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.

The indicated salary-rate was not found on the Salary_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan;MSGData3: Table-Id) (Message ID: 000132)

Suggested Resolution:

Review the Salary Rate Table to ensure proper set up of rate information.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

The indicated flat-rate was not found on the Flat_Rate_Tbl. (MSGData1: Plan-Type; MSGData2: Benefit-Plan;MSGData3: Table-Id) (Message ID: 000133)

Suggested Resolution:

Review the Flat Rate Table to ensure proper set up of rate information.
Correct where appropriate
Rerun the BenAdmin process following the 'Prep Error' procedure.

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) (Message ID: 000149)

Suggested Resolution:

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.

The Event Rule for this Plan Type requires that an election be made (theElection-Required indicator onBas_Event_Rules is Yes) but no Option-Cd has been specified on Bas_Partic_Plan. (MSGData1: PlanType) (Message ID: 000150)

Suggested Resolution: 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.

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) (Message ID: 000151)

Suggested Resolution: 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.

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) 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. (Message ID: 000152)

Suggested Resolution:

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.

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) (Message ID: 000153)

Suggested Resolution:

Review the Life and AD/D Table to ensure proper set up of the benefit plan indicated.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000154)

Suggested Resolution:

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.

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) (Message ID: 000155)

Suggested Resolution:

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.

The Option-Cd elected on Bas_Partic_Plan requires that a flat coverage amount be supplied (the Life-Bas_Partic_Plan requires that a flat coverage amount be supplied (the Life-ADD-Covrg code is '1') but the FlatAmount on Bas_Partic_Plan is zero. ADD-Covrg code is '1') but the FlatAmount 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) (Message ID: 000156)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

The Option-Cd elected on Bas_Partic_Plan requires that a salary coverage factor be supplied (the LifeADD-Covrg code is '2') but the FactorXsalary 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).(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) (Message ID: 000157)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Prep Error' procedure.

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) (Message ID: 000158)

Suggested Resolution:

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.

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 LifeADD-Covrg code on Life_ADD_Tbl is '3' - Specify on Employee Record) (MSGData1: Plan-Type; MSGData2 Option-Cd) (Message ID: 000159)

Suggested Resolution:

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.

The Option-Cd elected on Bas_Partic_Plan is not defined as "Specify on Employee Record" (the LifeADD-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) (Message ID: 000160)

Suggested Resolution:

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.

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) (Message ID: 000161)

Suggested Resolution:

Review the Savings Plan Table to ensure proper set up of the benefit plan indicated.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected before-tax contributions on a "Percent of Gross" basis (the SavingsCovrg field equals '2') but the Flat-DedAmt field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) (Message ID: 000162)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000163)

Suggested Resolution:

Review the Savings Plan Table and correct the associate Before Tax Investment Limited To amount.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

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. (Empl-Pct-Btax field). (MSGData1: Plan-Option-Cd) (Message ID: 000164)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "Percent of Gross" basis (the SavingsCovrg-Atax field equals '2') but the FlatDed-Amt-Atax field on Bas_Partic_Plan is not equal to zero. (MSGData1: Plan-Type; MSGData2: Option-Cd) (Message ID: 000165)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000166)

Suggested Resolution:

Review the Savings Plan Table and correct the associate After Tax Investment Limited To amount.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

For the Option-Cd indicated on Bas_Partic_Plan, the employee has elected after-tax contributions on a "FlatAmount" 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) (Message ID: 000167)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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-DedAmt and Flat-Ded-Amt-Atax fields on Bas_Partic_Plan equals zero).(MSGData1: Plan-Type; MSGData2:Option-Cd) (Message ID: 000168)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000169)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000171)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000172)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000173)

Suggested Resolution:

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.

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) (Message ID: 000174)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000175)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000184)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000185)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000186)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000187)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000188)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000192)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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 FSAMax-Annl-Pldg field). (MSGData1: Plan-Type; MSGData2: Option-Cd) (Message ID: 000193)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000195)

Suggested Resolution:

Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000196)

Suggested Resolution:

Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
Correct where appropriate
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000197)

Suggested Resolution:

Contact the Payroll Supervisor to have him/her establish the missing periods in the pay calendar table.
Correct where appropriate.
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000198)

Suggested Resolution:

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.

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) (Message ID: 000199)

Suggested Resolution:

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.

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) (Message ID: 000200)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000201)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000202)

Suggested Resolution:

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.
Rerun the BenAdmin process following the 'Election Error' procedure.

Dependent enrolled in a health plan is deceased as of the event date. (Message ID: 000220)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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. (Message ID: 000221)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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. (Message ID: 000222)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

A dependent that is a student as of the event date is over the age limit specified at the benefit program level. (Message ID: 000223)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

The benefit program does not allow coverage for married dependents. (Message ID: 000224)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

The number of dependents is less than the minimum defined for the elected coverage code. (Message ID: 000225)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

The number of dependents enrolled exceeds the maximum allowed for the coverage code. (Message ID: 000226)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

A dependent that is a spouse has been elected for coverage. The coverage code prohibits spouses from being enrolled. (Message ID: 000227)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

A dependent with the relationship of spouse must be enrolled for the coverage elected. (Message ID: 000228)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000232)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000233)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

No Open On-Cycle Pay Periods (Message ID: 000234)

Suggested Resolution: Submit a ServiceNow Ticket.

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: PlanType and Benefit-Plan; MSGData2: Deduction-Code and Class; MSGData3: Calculated negative deduction) (Message ID: 000235)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 000236)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

No covered dependents were found for this Plan. This is a Dependent Life plantype, 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) (Message ID: 000288)

Suggested Resolution:

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
Rerun the BenAdmin process following the 'Election Error' procedure.

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) (Message ID: 00292)

Suggested Resolution: 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.

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) (Message ID: 000293)

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) (Message ID:000294)

Suggested Resolution:

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.

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). (Message ID: 000295)

Suggested Resolution:

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.

Multi Job Not Found. A job record does not exist as of the event date specified on the BAS_ACTIVITY record. (Message ID: 000325)

Suggested Resolution:

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.

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) (Message ID: 000326)

Suggested Resolution:

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.

No Job Data for Event. The HR data required to process eligibility for the participant does not exist. (Message ID: 000327)

Suggested Resolution:

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.

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. (Message ID: 000328)

Suggested Resolution: This is a student and does not have any qualifying appointments. Close the open event. Change flag(s) to processed.

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. (Message ID: 000330)

Suggested Resolution: Review for other errors before submitting a ServiceNow Ticket.

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. (Message ID: 000351)

Suggested Resolution: Review for other errors before submitting a ServiceNow Ticket.

Minimum Number Covered Error. There are not enough dependents of this type of dependent and this coverage code. (Message ID: 000608)

Suggested Resolution:

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

Maximum Number Covered Error (Message ID: 000609)

Suggested Resolution:

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.

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. (Message ID: 000613)

Suggested Resolution: Enrollment dates need to be verified and corrected as needed.

Delta Dental Interface

Before opening a ServiceNow ticket, please verify the following:

Clear any Unique Constraint Errors.
Confirm the Nightly Refresh Benefits Snapshot completed successfully.
Review Snapshot details to ensure accuracy.
Double-check your Run Control parameters.
Verify you’ve selected the correct file type.
Make sure all required fields—such as EDI Partner ID, Company, Plan Type, and Benefit Plan Selection—are entered correctly.
Check for any Process Run errors and resolve them if possible.

PSR

Empty Outbound File

Issue: No data is present in the generated outbound file.
Resolution: Check the Run Control page for outbound file status, then review the CSU PSR Errors page. Resolve any CSU errors—the next outbound run will reattempt transmission.

Failed Authentication

Issue: Interface cannot authenticate with the PSR system.
Resolution: Verify FTP credentials and the CSU installation setup. If incorrect, coordinate with technical support or log a ServiceNow ticket.

Level‑1 Errors & CalPERS Notifications

Issue: A Level‑1 error occurs during processing.
Resolution: The campus technical contact should receive notifications from CalPERS. They must act on these alerts and follow up with response file availability.

Missing Permitting Event Codes / Missing Info

Issue: Transactions fail due to missing data or event codes.
Resolution: Run baseline queries (CSU_BAS_HEALTH_PERM_MISSING and CSU_BAS_HEALTH_PERM_AUDIT1) to identify and resolve missing permitting event codes, zip codes, counties, or dates.

Missing CalPERS ID for Employees or Dependents

Issue: The system flags missing CalPERS participant IDs.
Resolution: Run queries (CSU_BAS_CALPERS_ID_MISSING and _MISSING_DEP) to identify records missing CalPERS IDs and update them accordingly.

Errors Displayed in CSU PSR Errors Page

Issue: Certain transactions show errors after interface processing.
Resolution: Use the CSU PSR Errors page to review, resolve, or ignore each error. Mark them as "Error Resolved" (if corrected) or "Ignore Error" (if appropriate).

Invalid or Missing SSNs for Employee or Dependent

Issue: PSR interface rejects transactions with invalid or placeholder SSNs (e.g., starting with 999 or XXX).
Resolution: Replace invalid SSNs with accurate data in CHRS to ensure successful benefit administration.

Dependents Over Age 26 Still Listed

Issue: Dependents older than 26 have not been removed.
Resolution: Ensure CHRS updates reflect removal of dependents exceeding the age threshold (now age 26).

Incorrect Permitting Event Codes for FlexCash or Medical Coverage

Issue: The wrong Permitting Event Code is used when switching between FlexCash and CalPERS medical coverage.
Resolution: Use code 505 to cancel CalPERS medical when enrolling in FlexCash, and code 101 when enrolling in CalPERS medical after cancelling FlexCash.

Out‑of‑State Zip Codes Not in Reference Table

Issue: Out-of-state zip codes are unrecognized, causing PSR Xref errors.
Resolution: Confirm that the CSU PSR Xref tables include both "Out of State" entries in County and Zip Xref lists. If needed, request updates via ServiceNow.

SCO Interface

Before submitting a ServiceNow ticket, please confirm the following:

Review the CSUBAS05 process status and resolve any errors.
Use the View Log/Trace feature to check:
- Interface error report
- Current and retroactive deduction reports for Vision, Life/AD&D, and LTD
- Process output file
  Make sure any listed errors are resolved before moving forward.
Run the interface in Preliminary Mode to verify that errors no longer occur.
Confirm that file names use the correct prefixes (e.g., TRN, V/VR, B/BR, L/LR).
Ensure all prerequisites are met:
- Employees are active, benefit-eligible, and either enrolled or have coverage canceled.
- For FERP eligibility: employee must have at least 0.5 FTE, the correct employment class (FERP), and an eligibility end date after the processing period.

BAS003.SQR - Invalid Elections Report

There is no need to set anything on the Event Status Update page to resolve the 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.

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)

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

Suggested Resolution: 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.

Assign None (AN) BAS events become Finalized None (FN) process status after the next delivered Ben Admin run (PSPBARUN).

Assign Errors (AE)

Suggested Resolution: 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:

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

Prep Errors (PE)

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

Election Errors (EE)

Suggested Resolution: Determine what needs to be corrected for the related data entry:

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

BAS008.SQR - Report on Flagged Items

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.

Address Eligibility Change flag is Checked

Meaning: 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.

Suggested Resolution: 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.

Did NOT include a zip code or state change - Uncheck the Address Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
Did include a zip code or state change - 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.

Job Eligibility Change flag is checked

Meaning: 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.

Suggested Resolution: 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. 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.

Fields - 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, Elig Fld 9.
Did NOT update a field - Uncheck the Job Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
Did update a field - 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.

The BAS Group ID value is critical for OE BAS events.

MultiJob Eligibility Change flag is checked

Meaning: 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.

Suggested Resolution: 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. 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.

Fields - 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, Elig Fld 9.
Did NOT update a field - Uncheck the Job Eligibility Change flag on the Update Event Status page and then click on Save instead of reprocessing the specific BAS event.
Did update a field - 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.

CSUBAS27.SQR – CSU Process Status Report

This report lists all open BAS events for a given BAS Schedule ID. It is a customized clone of BAS27.sqr, excluding events in Void, Closed, or Disconnected status. Below are the process status descriptions and steps needed to move events toward finalization.

Example of a Prep Error.

The Process Status shows Prepare Error.

Program Assignment - Process Status

AS - Program Eligibility Assigned

Description: BAS event is assigned to a benefit program. – Process Successful.

Troubleshooting Steps: Events typically don’t remain in AS status long, as they usually advance to the next step. If an event is still in AS after CSUBAS processing, it indicates the employee has another BAS event in progress. The event will remain in AS until the open event is finalized.

Next Processing Steps: Once able, the event continues in Ben Admin processing to the prepare options step.

AN - Program Eligibility Assigned None

Description: BAS event is not assigned to a benefit program.

Troubleshooting Steps: 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.

Next Processing Steps: 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

Description: BAS event is assigned to multiple programs.

Troubleshooting Steps: The employee is eligible for multiple Benefit Programs. Corrections may be needed in personal, employment, job, or program eligibility data. Review Job Data for cross–bargaining unit cases; if the employee qualifies for more than one program, an EmplID override is required.

Next Processing Steps: 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

PR - Prepared

Description: The system has determined eligible benefit plan options for the participant associated with the event.

Troubleshooting Steps: Event requires Election Entry or finalization.

Next Processing Steps: The batch process force-finalizes prepared events so default benefits can be written (e.g., HIR BAS auto-enrolls Life, Vision, and LTD if applicable). The system then sets the status to FE (Finalized – Enrolled). BAS events stay at PR until elections are entered or, for eBenefits ESS events, until they expire.

FA - Finalized - Benefit Program None

Description: BAS event has no program assignment and no current elections.

Troubleshooting Steps: All employees should have a Benefit Program assignment. Program eligibility must be reviewed, and PeopleBooks recommends running eligibility reports to identify any issues with this status.

Next Processing Steps: 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 is Program None.

FP - Finalized - Prepared None

Description: System has assigned participant event to a benefit program, but the associated participant is ineligible to elect any new options.

Troubleshooting Steps: Event did not change eligibility. Prepared none should indicate no change in benefits. No further action required.

Next Processing Steps: No further processing occurs for this BAS event. The online page description for this process status is Prepare None.

PE - Prepare Error

Description: The system encountered an error while preparing options for the participant tied to the event. Events receive a PE status during option eligibility checks or credit calculations.

Troubleshooting Steps: To correct, you should make corrections to the personal/employment/job information of the associated participant or to plan and option eligibility information.

Next Processing Steps: 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

ET – Entered

Description: 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.

Troubleshooting Steps: Event needs finalization.

Next Processing Steps: If no errors are found, elections post to benefit and payroll tables, and the status updates to FE (Finalized – Enrolled). If errors exist, event rules decide whether to load current elections or defaults, and the status updates to EE (Election Error).

EE - Election Error

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

Troubleshooting Steps: You need to correct the errors by reviewing and possibly reentering employee elections.

Next Processing Steps: No further processing occurs for this BAS event until it is resolved. On the next run, Benefits Administration will attempt to move the status to FE (Finalized – Enrolled).

Alternatively, you can “force finalize” the event (or all events in the Open Enrollment schedule), finalizing with errors. In this case, the system loads the participant’s default benefit option(s). If a dependent/beneficiary is in error, only the employee’s plan choice is loaded; the dependent/beneficiary will not be included.

End of Article

Previous Article (job aid) Tuition Fee Waiver Frequently Asked Questions (FAQ)

Next Article (job aid) Benefits Delivered Queries for CHRS

CHRS Knowledge Base

Benefits Troubleshooting Guide

Shared Employee

Event Class

When Benefits Terminate or Are Incorrect

Warnings and Errors

Benefits Admin (BA)

Recently Updated Articles