The purpose of this document is to assist campuses with Benefits related issues.
Shared Employee
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
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 andRun 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
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 andRun 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
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
Excluded
ACA_EXCLUD - Excluded from ACA consideration
- 1151 Instr Stdnt Asst On-Cmps WS
- 1153 Instr Stdnt Asst Off-Cmps WS
- 1860 STUDENT ASSISTANT
- 1861 STUDENT TRAINEE, ON-CAMPUS WOR
- 1868 Student - NCS
- 1870 Student Asst
- 1871 Stdnt Trainee On-Cmps WS
- 1872 Stdnt Trainee Off-Cmps WS
- 1874 BRIDGE STUDENT ASSISTANT
- 1875 BRIDGE STUDENT TRAINEE, ON-CAM
- 1876 Brdg Stdnt Trainee Off-Cmps WS
- 1880 Stud TR LAEP On-Campus
- 1881 Stud TR LAEP Off-Campus
- 1882 BR Stud TR LAEP On-Campus
- 1883 BR Stud TR LAEP Off-Campus
- 2326 Graduate Assistant OCWS
- 2681 Acad Supp Student Em I-OnCmpWS
CSU_EXCLUD - Benefit Ineligible
- 0350 Continuing Ed Instructor CMA
- 1150 Instr Stdnt Asst
- 1151 Instr Stdnt Asst On-Cmps WS
- 1152 Instr Stdnt Asst Off-Cmps
- 1153 Instr Stdnt Asst Off-Cmps WS
- 1800 Casual Worker
- 1860 STUDENT ASSISTANT
- 1861 STUDENT TRAINEE, ON-CAMPUS WOR
- 1868 Student - NCS
- 1870 Student Asst
- 1871 Stdnt Trainee On-Cmps WS
- 1872 Stdnt Trainee Off-Cmps WS
- 1874 BRIDGE STUDENT ASSISTANT
- 1875 BRIDGE STUDENT TRAINEE, ON-CAM
- 1876 Brdg Stdnt Trainee Off-Cmps WS
- 1880 Stud TR LAEP On-Campus
- 1881 Stud TR LAEP Off-Campus
- 1882 BR Stud TR LAEP On-Campus
- 1883 BR Stud TR LAEP Off-Campus
- 2309 Tchg Assoc Ext. Ed-For Credit
- 2322 Instr Fac,Spcl Pgms-For Credit
- 2323 Instr Fac,Extension-For Credit
- 2324 Teaching Associate Summer Term
- 2325 Graduate Assistant Monthly
- 2336 E99 403B Deduction Monthly
- 2337 R03 403B Deduction Monthly
- 2355 Graduate Assistant
- 2356 Substitute Instructional Facul
- 2357 If Summer Session Extension
- 2362 Demonstration Instr Fac
- 2363 Instr Fac,Extension Non-Credit
- 2365 Music Studio Instr Faculty
- 2368 Instr Fac, Extra Quarter,QSYRO
- 2390 Instr Fac,Summer Quarter
- 2402 Instr Fac,Summer Arts Pgm
- 2422 IF. Spc Prgms FC - ACA
- 2423 IF, Extension FC - ACA
- 2456 Substitute IF - ACA
- 2457 IF Summer Session State Supprt
- 2465 Music Studio IF - ACA
- 2502 IF - Summer Arts Program - ACA
- 2557 IF, SS Ext - ACA
- 2563 IF, Ext Non-Credit - ACA
- 2662 Demonstration IF - ACA
- 2680 Acad Supp Student Employee I
- 2681 Acad Supp Student Em I-OnCmpWS
- 2757 IF, SS State Support - ACA
- 4660 Special Consultant
- 4661 Mediator/Facilitator-Sac
- 4760 Special Consultant - ACA
- 7171 Notetaker
- 7172 Reader
- 7930 Per Diem Non Exempt Healthcare
- 8347 Police Officer-Int NonRep
- 8374 Excl 403B Deduction Monthly-NE
- 8379 Special Consultant-NE
- 8380 Special Consultant-ACA-NE
Updated as of 7/1/2025
Eligibility
Benefits Administration Eligibility fields are on an employee’s Job Data component. You can see them from the Benefits Program Participation link. To edit them, you must use a Benefits Eligibility Override.
Field Label on Job Data > Benefits Program Participation page: Elig Fld 1
Purpose: Met Duration of Appointment
Explanation: Determine Duration of Appointment and populate Elig Fld 1 on Job Data > Benefits Program Participation Job Data > Benefits Program Participation page with Y (yes duration is met) or N (no duration is not met). Ben Admin eligibility rules look for these values when determining the employee’s benefits eligibility. This is a system determined value that cannot be overwritten at this time
Valid Values: Y for duration is met and N for duration is not met.
Field Label on Job Data > Benefits Program Participation page: Elig Fld 2
Purpose: Job Code
Explanation: Populates Elig Fld 2 on Job Data > Benefits Program Participation Job Data > Benefits Program Participation page with the current Job Code of the employee record. This is a systemdetermined value that cannot be overwritten at this time.
Valid Values: The employee’s job code for the employment record
Field Label on Job Data > Benefits Program Participation page: Elig Fld 3
Purpose: ACA
Explanation: Determine ACA eligibility and populate Elig Fld 3 on Job Data > Benefits Program Participation Job Data > Benefits Program Participation page with Y (yes ACA applicable) or N (no not ACA applicable). This is a systemdetermined value that cannot be overwritten at this time.
Valid Values: Y for ACA applicable and N for Not ACA applicable.
Field Label on Job Data > Benefits Program Participation page: Elig Fld 4
Purpose: NE
Explanation: If populated with NE, which stands for Not Eligible, the employee will not be eligible for certain benefits.
Valid Values: NE
Field Label on Job Data > Benefits Program Participation page: Elig Fld 5
Purpose: After-tax Indicator
Explanation: If populated with AFTERTAX, after-tax medical plans present for benefits enrollment for the employee in On Demand Event Maintenance and in eBenefits Self Service. This is a manually entered value that can be removed at any time as long as the employee is not enrolled in an after-tax benefit plan.
Valid Values: AFTERTAX
Field Label on Job Data > Benefits Program Participation page: Elig Fld 6
Purpose: Benefits Eligibility Override Benefit Program Indicator
Explanation:If populated with AB2O, AYO, AC1O, AC2O, NOBO, STNO, UN6O, U13O, the employee will be placed into the following override benefit programs (see chart below)
Valid Values: AB2O, AYO, AC1O, AC2O, NOBO, STNO, UN6O, U13O
| Elig Fld 6 Values | Override Benefits Program |
|---|---|
| AB2O | ABO |
| AYO | AYO |
| STNO | STO |
| UN6O | U6O |
| U13O | U3O |
| AC1O | A1O |
| AC2O | A2O |
| NOBO | NBO |
Event Class
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.
Process Status Code: AS
Event Status is: Open
OK to Reprocess: N/A
Conditions: N/A
Notes: N/A
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 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 Code: PR
Event Status is: Open
OK to Reprocess: Yes
Conditions: N/A
Notes: Can reprocess back to Assign Benefit Program.
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 Code: NT
Event Status is: Open
OK to Reprocess: No
Conditions: N/A
Notes: N/A
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 Code: EE
Event Status is: Open
OK to Reprocess: Only reprocess to Re-enter status
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 Code: RE
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 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 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 Code: FP
Event Status is: Closed
OK to Reprocess: Yes
Conditions: N/A
Notes: N/A
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 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 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 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 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 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 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 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
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 Code: RE
Event Status is: N/A
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 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 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 Code: FP
Event Status is: Closed
OK to Reprocess: Yes
Conditions: N/A
Notes: N/A
Process Status Code: AS
Event Status is: Open
OK to Reprocess: N/A
Conditions: N/A
Notes: N/A
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 Code: AN
Event Status is: Open
OK to Reprocess: Yes
Conditions: Need to correct error first.
Notes: Can reprocess back to Assign.
Process Status Code: PR
Event Status is: Open
OK to Reprocess: Yes
Conditions: N/A
Notes: Can reprocess back to Assign.
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 Code: NT
Event Status is: Open
OK to Reprocess: No
Conditions: N/A
Notes: N/A
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 Code: EE
Event Status is: Open
OK to Reprocess: N/A
Conditions: N/A
Notes:N/A
Process Status Code: RE
Event Status is: N/A
OK to Reprocess: Yes
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 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 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 Code: FP
Event Status is: Closed
OK to Reprocess: Yes
Conditions: N/A
Notes: N/A
- 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
- LTE
- ADP
- BIR
- DGC
- DLC
- EGC
- ELC
- NEW
- ACM
- ACT
- AD1
- ADR
- BI1
- CNC
- DEA
- DG1
- DI1
- DIV
- DL1
- DRP
- EG1
- EL1
- FSA
- HBE
- HIR
- LIF
- LVE
- MA1
- MAR
- MSC
- NW1
- OE
- OVR
- PC1
- REH
- RFL
- SNP
- T90
- T92
- TBC
- TER
- LTE
- ADP
- BIR
- DGC
- DLC
- EGC
- ELC
- NEW
- ACM
- ACT
- AD1
- ADR
- BI1
- CNC
- DEA
- DG1
- DI1
- DIV
- DL1
- DRP
- EG1
- EL1
- FSA
- HBE
- HIR
- LIF
- LVE
- MA1
- MAR
- MSC
- NW1
- OE
- OVR
- PC1
- REH
- RFL
- SNP
- T90
- T92
- TBC
- TER
AG Page Status Codes:
1 – Assigned
2 – In Progress
4 – Completed
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
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
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
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)
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)
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)
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
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
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
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
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
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
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
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
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
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
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
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.
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).
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.
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).
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)
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)
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).
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.
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.
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
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.
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
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.
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.
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
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.
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.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, first check the Benefit Plan Table to confirm that the benefit plan has been set up. If it exists, review the associate’s Benefit Program Table to ensure the plan is available as an option. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Age Graded Rate Table setup for the specified benefit and table ID. Then confirm that the associate’s age and sex align with the applicable criteria. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Plan Table for the benefit plan specified to ensure the proper Coverage Group Code is present. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Form Table for the form ID specified. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
The employee record is missing a birthdate. Review the Modify a Person page, update the information accordingly, and rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Ben Prog Partic record for the employee and then review for the specified program. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit / Deduction Program Table status for the program specified. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
This issue often occurs when an employee transfers between benefit programs and is terminated from a benefit that does not exist in the new program (e.g., AY to AC1). Open a ServiceNow ticket, as the issue may be related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit / Deduction Program Table status for the program specified. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit / Deduction Program Table for the specified calc rules ID. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit / Deduction Program Table for the specified service rate ID. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Service Rate Table or Service Step Table with which the Plan Type is associated. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Employees can only be eligible for one benefit program per Empl record. Review Job Data to verify whether something was keyed incorrectly that could explain why the system is unable to assign a benefit program. If no issue is found, either apply an override or submit a ServiceNow ticket, as it may be a configuration issue.
Campus Action:
Employees can only be eligible for one benefit program per Empl record. Review Job Data to verify whether something was keyed incorrectly that could explain why the system is unable to assign a benefit program. If no issue is found, either apply an override or submit a ServiceNow ticket, as it may be a configuration issue.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Salary Rate Table to ensure proper set up of rate information. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Flat Rate Table to ensure proper set up of rate information. Make corrections where necessary, and coordinate with the campus to rerun the BenAdmin process.
Informational Only – no action required.
Campus Action:
This plan type requires an election to be made; however, for CSU it is not required. Open a ServiceNow ticket, as this is a configuration issue.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit/Deduction Program Table to identify the Event Rules ID associated with the indicated plan type. For CSU, an election is not required, so the Elect Required flag must be set to ‘Off.’ Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit/Deduction Program Table for the specified plan type and option. Coordinate with the campus to confirm whether the employees data is correct. If it is correct, have the campus re-enter the EmplID in the Election Entry pages, correct the option code error, and rerun the BenAdmin process. If the data on the Benefit/Deduction Program Table is incorrect, make the necessary corrections and then coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit/Deduction Program Table to identify the Event Rules ID associated with the specified plan type. Then review the Event Rules Table using that Event Rules ID. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to ensure proper set up of the benefit plan indicated. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Review the employee’s Job Record to match the Empl Rcd #, Effective Date, and/or Effective Date Sequence # indicated. If the corresponding data does not exist, the employee cannot be processed in this Event Maintenance cycle due to the deletion of Job data. If the event was already finalized, it may need to be voided. If a match is found in Job Data, open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the processed event in detail to determine whether any action is required. Coordinate with the campus to make any necessary corrections and rerun the BenAdmin process, if appropriate.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Schedule Table to confirm that the indicated schedule is set up correctly. If no schedule exists, add one to the table with the appropriate BAS Group ID for Event Maintenance processing, and then restart the COBOL process with the Reprocess radio button set to ‘None.’
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to confirm that the data established is correct for the benefit plan in question. If the data is correct, coordinate with the campus to re-enter the EmplID in the Election Entry pages and input the flat amount of insurance. If the Life and AD/D Table contains errors, correct them as appropriate. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to confirm that the data established is correct for the benefit plan in question. If the data is correct, coordinate with the campus to re-enter the EmplID in the Election Entry pages and input the flat amount of insurance. If the Life and AD/D Table contains errors, correct them as appropriate. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to confirm that the data established is correct for the benefit plan in question. If the data is correct, coordinate with the campus to re-enter the EmplID in the Election Entry pages and input the flat amount of insurance. If the Life and AD/D Table contains errors, correct them as appropriate. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to confirm that the data established is correct for the benefit plan in question. If the data is correct, coordinate with the campus to re-enter the EmplID in the Election Entry pages and input the flat amount of insurance. If the Life and AD/D Table contains errors, correct them as appropriate. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Life and AD/D Table to confirm that the data established is correct for the benefit plan in question. If the data is correct, coordinate with the campus to re-enter the EmplID in the Election Entry pages and input the flat amount of insurance. If the Life and AD/D Table contains errors, correct them as appropriate. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
The employee elected HICRA/DICRA but did not provide a contribution amount. Return to ODEM, move the employee to Re-Enter status, and enter the applicable monthly contribution amount along with the Annual Pledge amount. Then reprocess the event to clear the election error.
Campus Action:
The employee elected HICRA/DICRA but did not provide a contribution amount. Return to ODEM, move the employee to Re-Enter status, and enter the applicable monthly contribution amount along with the Annual Pledge amount. Then reprocess the event to clear the election error.
Campus Action:
The employee elected HICRA/DICRA but did not provide a contribution amount. Return to ODEM, move the employee to Re-Enter status, and enter the applicable monthly contribution amount along with the Annual Pledge amount. Then reprocess the event to clear the election error.
Campus Action:
Review the employee’s dependents, as one or more may have been deleted. An investigation is needed to determine whether the dependent should be reinstated in the system or excluded from enrollment. During conversion, if the dependent’s name matches a suffix or middle name, CHRS does not recognize it. In such cases, the dependent must be manually added, and the event reprocessed
Campus Action:
In CHRS, beneficiaries are not tracked—only dependents are. In HR 9.0, a dependent can also be designated as a beneficiary, but in CHRS the system is not configured to accept those three dependent types on a plan, so they are converted as beneficiaries.
To correct this, update the Dependent ID under Election Entry by selecting Dependent/Beneficiary and changing the designation from Beneficiary to Dependent or remove completely.
Campus Action:
In CHRS, beneficiaries are not tracked—only dependents are. In HR 9.0, a dependent can also be designated as a beneficiary, but in CHRS the system is not configured to accept those three dependent types on a plan, so they are converted as beneficiaries.
To correct this, update the Dependent ID under Election Entry by selecting Dependent/Beneficiary and changing the designation from Beneficiary to Dependent or remove completely.
Campus Action:
In CHRS, beneficiaries are not tracked—only dependents are. In HR 9.0, a dependent can also be designated as a beneficiary, but in CHRS the system is not configured to accept those three dependent types on a plan, so they are converted as beneficiaries.
To correct this, update the Dependent ID under Election Entry by selecting Dependent/Beneficiary and changing the designation from Beneficiary to Dependent or remove completely.
Campus Action:
In CHRS, the system is not configured to manage beneficiaries. Please submit a ServiceNow ticket for assistance.
Campus Action:
In CHRS, the system is not configured to manage beneficiaries. Please submit a ServiceNow ticket for assistance.
Campus Action:
The amount the employee has pledged exceeds the allocated limit. Please review the entered amounts and update them to stay within the allowable limits.
Example: For the year 2026, the combined limit for HCRA and DCRA is $10,000 — with individual limits of $3,300 for HCRA and $7,500 for DCRA. If you enter $3,400 for HCRA and $7,500 for DCRA, you’ll exceed the combined limit and must reduce one of the amounts accordingly.
Campus Action:
The error indicates that a Pay Calendar is missing for the month and year being entered. Before a Pay Calendar can be created, the Balance ID for that year must first be established. The campus should work with its payroll team to review and confirm that both the Balance ID and Pay Calendar are set up for the full year. If both are confirmed to be in place, a ServiceNow ticket should be opened for further investigation.
Campus Action:
The error indicates that a Pay Calendar is missing for the month and year being entered. Before a Pay Calendar can be created, the Balance ID for that year must first be established. The campus should work with its payroll team to review and confirm that both the Balance ID and Pay Calendar are set up for the full year. If both are confirmed to be in place, a ServiceNow ticket should be opened for further investigation.
Campus Action:
The error indicates that a Pay Calendar is missing for the month and year being entered. Before a Pay Calendar can be created, the Balance ID for that year must first be established. The campus should work with its payroll team to review and confirm that both the Balance ID and Pay Calendar are set up for the full year. If both are confirmed to be in place, a ServiceNow ticket should be opened for further investigation.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the data for the affected Plan Type. For Plan Types not included in the new benefit program, the process refers back to the previous program to determine how to process the Plan Type. If the Plan Type is not included in the previous program either, the system cannot determine how to handle it. If a Plan Type is being discontinued or transitioned to another Plan Type, it should remain in the program and event rule, but its eligibility should be configured to “None.” The Plan Type should not be inactivated or deleted—only the eligibility settings should be modified. Once any necessary corrections are made, coordinate with the campus to rerun the BenAdmin process.
Campus Action:
Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Benefit/Deduction Program Table – Cost page for the specified Plan Type and Option ID, as well as the associated COBOL batch process. Once any necessary corrections have been made, coordinate with the campus to rerun the Ben Admin process.
Campus Action:
Review the number of dependents indicated against the number entered, and make adjustments as needed by either correcting the count or entering any missing dependents.
Campus Action:
In CHRS, the system is not configured to manage beneficiaries. Please submit a ServiceNow ticket for assistance.
Campus Action:
Not applicable for CSU, as savings plans are not maintained. Open a ServiceNow ticket, as this issue is related to configuration.
CMS- Benefits Action:
In response to the ServiceNow ticket, review the Savings Plan Table to ensure it is not set up for the benefit plan indicate. Make any necessary corrections, and coordinate with the campus to rerun the BenAdmin process.
Campus Action:
In CHRS, the system is not configured to manage a dependent’s date of death. Review the dependent records and make adjustments by removing the dependent effective the following period.
Campus Action:
In CHRS, the system is not configured to allow ex-spouses to be included in a benefits plan. Review the dependents for any ex-spouses and remove them as needed.
Campus Action:
In CHRS, the system is not configured to track dependents based on student status and can only track them based on age. Review the dependents for any selected student indicators and remove them as needed.
Campus Action:
In CHRS, the system is not configured to track dependents based on student status and can only track them based on age. Review the dependents for any selected student indicators and remove them as needed.
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.
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.
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.
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.
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.
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.
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.
Suggested Resolution: Submit a ServiceNow Ticket.
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 HCRA/DCRA plan in the calendar year.
- Correct where appropriate
- Rerun the BenAdmin process following the 'Election Error' procedure.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Suggested Resolution: This is a student and does not have any qualifying appointments. Close the open event. Change flag(s) to processed.
Suggested Resolution: Review for other errors before submitting a ServiceNow Ticket.
Suggested Resolution: Review for other errors before submitting a ServiceNow Ticket.
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
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.
Suggested Resolution: Enrollment dates need to be verified and corrected as needed.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- Issue: Dependents older than 26 have not been removed.
- Resolution: Ensure CHRS updates reflect removal of dependents exceeding the age threshold (now age 26).
- 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.
- 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.
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.
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.
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).
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.
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.
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.
Audit the flags and re-process BAS events as needed.
- Use theReprocessing a CHRS BAS Eventcheat sheet every time you need to reprocess a BAS event in CHRS.
- Also use theeBenefits ESS OK to Reprocess Cheat Sheetevery 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. TheeBenefits ESS OK to Reprocess Cheat Sheetadvises when it is ok to reprocess an eBenefits ESS BAS event based on the BAS eventProcess Status. TheReprocessing a CHRS BAS Eventcheat sheet provides the next steps to take when the scenario dictates that you cannot reprocess a particular BAS event.
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.
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.
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.
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.
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.
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 Reportto evaluate employees who are eligible but not being assigned to a program.
Next Processing Steps: Events with an ANstatus will continue on through the process and end at a finalized – Assigned None(FA) status. All employees should receive a benefit program assignment.
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 AEdesignation and (try to) move them along in the process.
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.
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.
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.
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.
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- enteredprocess status automatically during the nightly CSUBASprocessing 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).
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
0 Comments
Add your comment