Overview
This job aid shows Benefits Officers how to review daily CSUBASDL logs and campus-specific CSUBAS logs.
- Daily review items
- What is CSUBASDL?
- Review the CSUBASDL Processes
- Obtain CSUBASDL Process IDs in Process Monitor
- Review CSUBASDL Log files in Report Manager
- Run CSUBAS on demand
- Find CSUBAS process logs after on-demand
- View CSUBASDL process logs
- Appendix: CSUBAS log error issues
- Appendix: Check Event Statuses
Background
CSUBASDL runs each night for all campuses to process benefits. Your campus is responsible for:
- Reviewing its own CSUBAS process logs.
- Resolving the CSUBAS process errors.
Daily Review items
Benefits Officer must review the following items daily. Use the event statuses of the events to guide your solutions. See Appendix: Check Event Statuses.
Review Item | Details | Navigation |
---|---|---|
CSUBASDL logs | CSU_PERM_DEL (x2) CSU_BA18003 CSUBA01A (x7) CSU_BA_EV_DT PSPBARUN (x5) CSU_PERM_INS (x3) |
|
CSU Benefits Reports | CSU Benefits Termination Rpt CSU Benefits Transaction Rpt CSU Job Changes Prior Ben Admin CSU Snapshot Unique Constraint |
|
Exceptions Reports | Invalid Elections Rpt Report on Flagged Items CSU Process Status Rpt |
|
CHRS BA Baseline Queries | CSU_BAS_DELETED_ACTIONS CSU_BAS_SS_NT CSU_BAS_SS_EVENTS CSU_BAS_HEALTH_PERM_AUDIT1 CSU_BAS_HEALTH_PERM_MISSING CSU_BAS_CALPERS_ID_MISSING CSU_BAS_CALPERS_ID_MISSING_DEP |
|
What is CSUBASDL?
- Processes employees’ eligibility for benefits, finalizes HIR and TER BAS events, processes eBenefits enrollment.
- Deletes BAS events when the employee’s eligibility is not impacted. Deleted BAS events do not process through Ben Admin.
- Processes eBenefits self-service BAS events and applies submission date rules.
- Inserts permitting event codes for eBenefits self-service BAS events and deletes orphaned event codes.
- Comprises several processes that run on a nightly schedule, starting at 7:00 pm, 7 days a week.
- Runs separately for each campus in the shared CHRS environment.
Distinguish the two (2) jobs
CSUBAS | A job that runs several processes. These processes update employee benefits in CHRS.
|
CSUBASDL | A job that automatically runs CSUBAS jobs for all campuses daily.
|
CSUBAS Processes
Process | Information |
---|---|
CSU_PERM_DEL | Deletes orphaned CSU Permitting Event Codes |
CSU_BA18003 | Deletes events from the Review BAS Activity page that do not affect benefit eligibility if configured, such as MSC, ACT, POS, DTA, PAY, JRC. Note: Only Fullerton (the first campus on the CSUBASDL schedule) sees data in this report. All other campuses must run the CSU_BAS_DELETED_ACTIONS query to see the deleted BAS actions. If a campus runs CSUBAS manually before the nightly CSUBASDL run, the campus that ran CSUBAS manually will see all deleted BAS actions on the CSUBAS job log. |
CSUBA01A | Sets HIR and TER BAS events to be finalized by the Ben Admin Process |
CSU_BA_EV_DT | Updates Employee Self Service (ESS) event dates. Creates custom ESS xx1 events
|
PSPBARUN | The Ben Admin Process schedules employees, prepares options and finalizes elections and events |
CSU_PERM_INS | Inserts permitting event codes for HIR and self-service events |
CSU_BA_SF_CL | Soft closes open BAS events except for ESS BAS events that are not disconnected and have not processed |
CSU_BA_SFOP1 | Reopens soft closed ESS events |
CSU_BA_FLAG | Removes the Event out of Sequence flag from ESS ‘xx1’ events |
CSU_BA_SFOP2 | Reopens all soft closed events |
CSU_BAS_ACTP | This process deletes activity guides for aged-out or finalized Life or Open Enrollment BAS events, deletes voided Life and OE BAS events, and lists employees who are missing their Life and OE electronic signatures. |
CSUBASSCHED | D Sets the schedule ID on the run control ID. No need to review logs if run shows as a Success. |
Review the CSUBASDL Processes
Use this procedure to review the nightly CSUBASDL processes
Step 1: Navigate to Process Manager.
- Menu > PeopleTools > Process Scheduler > Process Monitor
Step 2: Enter the search criteria:
- User ID: CHR_SCHEDUCSU
- Process name - CSUBASDL

Step 3: Add the number of days to collect logs for
- After a weekend or holiday, set this field to include all of the missing days

Step 4: Click Refresh.

Step 5: Click the instance of CSUBASDL; the process detail page opens

Step 6: Click Expand Node to expand the CSUBAS instance for your campus.
- Each campus instance of CSUBAS is identified by the campus two-letter suffix. For example, CSUBASFL is the run for Fullerton.
- Make sure to click the expand node icon, and not the process itself

Step 7: Click Expand Node to expand the CSUBAS instance

Step 8: Click Expand Node for your campus CSUBAS instance

Step 8: Ensure all processes ran successfully
- Each process must be followed by a Success message. If any process shows Error or Abend:
- Review the log files for the process that failed.
- Fix the issue that cause the process failure.
- Open a Service Now support ticket.so they can restart the job. The assignment group will be CMS operations.

Obtain CSUBASDL Process IDs in Process Monitor
CSUBASDL logs are not available directly from the Process Monitor. Use the following procedure to get the process IDs for the CSUBASDL logs. You need these process IDs to find the logs in Report Manager. You are viewing the Process Detail from the previous procedure
Step 1: Highlight the text only on the process list for your campus and copy
- Click just before the text and drag to after the text that you want to capture. Do not click directly on the links.
- Right-click the highlighted text and then select Copy. - Optionally: Press CTRL+C.

Step 2: Right-click the highlighted text and then select Copy.
- Optionally: Press CTRL+C.
- The text is copied to your workstation buffer

Step 3: Open a text editor; i.e. Notepad
- Paste the text into a text editor

Step 4: In CHRS, Click return to go back to process list to navigate to report manager to review the log files
Step 5: Keep the file with the process IDs available while you review the CSUBASDL log files in Report Manager.
Review CSUBASDL Log files in Report Manager
Log files in Report Manager are secured by campus. This is why you open CSUBASDL logs in Report Manager instead of Report Monitor. Use the text file that you created in the previous procedure to look up the process IDs in Report Manager
Step 1: Navigate to Report Manager
- Menu > Reporting Tools > Report Manager
Step 2: Enter the process ID for one of the following processes that you obtained from the prior procedure.
- Any process that has error
- CSU_PERM_DEL
- CSU_BA18003
- CSUBA01A
- CSU_BA_EV_DT
- PSPBARUN
- CSU_BAS_ACTP
- CSU_PERM_INS
In this example below, you are going to view the log for CSU_PERM_DEL. The process ID that you copied is 50496. Search for this Process ID to view the log files for this process.
- Copy the Process ID from the Text File and paste the ID into the Report Instance Fields
Tip: Although you can search for a range of processes, the CSUBAS processes do not always run in an uninterrupted sequence. Search for each process individually to ensure that you are getting precisely the process that you need to review
Step 3: Click Refresh

Step 4: For each listed report, click the report to open the logs.

Step 5: Review all of the files in the File List
- These logs detail what the CSUBAS process did for this run.
- LOG and TXT files open in a new browser tab.
- When you finish reviewing them, close the browser tab.
- CSV files are downloaded. After you review the files, close them.
- If there are any errors or issues, you must resolve them.

Step 6: Click return to go back to the report manager page.
Guidelines
Review reports for every day, including those generated on weekends and holidays.
You must review and fix any issues that are mentioned in the following reports:
-
PSPBARUN:
- Delivered Ben Admin process. Make sure the log says process successfully completed.
- If it says it aborted or abend, there’s a problem with the process.
-
CSU_PERM_DEL:
- Make sure the log says process ended normally.
- If it says it aborted or abend, there’s a problem with the process.
-
CSU_BA18003:
- Make sure the log says process ended normally. If it says it aborted or abend, there’s a problem with the process.
- The .csv report lists BAS Actions deleted from the Review BAS Activity page.
- The first run of this process nightly deletes applicable BAS Actions for all campuses on CHRS. Use the CSU_BAS_DELETED_ACTIONS baseline query to see BAS Actions deleted for your campus.
- Only Fullerton (the first campus on the CSUBASDL schedule), sees data in this report in the CSUBASDL runs. All other campuses must run the CSU_BAS_DELETED_ACTIONS query to see the deleted BAS actions.
- If a campus runs CSUBAS manually before the nightly CSUBASDL run, the campus that ran CSUBAS manually see all deleted BAS actions on the CSUBAS job log.
-
CSU_PERM_INS:
- Make sure the log says process ended normally. If it says it aborted or abend, there’s a problem with the process.
- This log lists the employees and permitting events that were inserted.
- For HCRA/DCRA perm event codes, use this log to review and update the monthly HCDRA/DCRA contribution amounts for employees in the Spending Accounts Component.
-
CSU_BAS_ACTP:
- Follow up with employees who are missing their electronic signatures.
- If the process is not completed to Success’ status, review the process log to see if there are errors that require resolution.
-
CSU_BA_EV_DT:
- Make sure the log says process ended normally.
- If it says it aborted or abend, there’s a problem with the process.
Run CSUBAS on demand
Use this procedure to manually run CSUBAS for your event maintenance schedule in situations where you made updates and do not want to wait for the nightly process run
Step 1: Navigate to Run Automated Event Processing.
- Menu > Benefits > Manage Automated Enrollment > Events > Run Automated Event Processing
Step 2: Select the schedule ID.
- In this example, the schedule for Fullerton event maintenance is selected. Each campus has its own schedule for event maintenance

Step 3: Click Run
- The process schedule will open

Step 4: Prepare the Process:
- Select the active server
- Select CSU Ben Admin Job
IMPORTANT:
- When you run the CSUBAS process on demand, always run CSUBAS not CSUBASDL. The CSUBASDL process runs for all campuses.
- If the Server Name field is blank and you cannot select a server, you can still run the process: the active server is set by default.

Step 5: Click OK

Find CSUBAS process logs after on-demand
When you run the CSUBAS process on-demand just for your campus, you can review the process logs directly from Process Monitor. Use this procedure to find and view the CSUBAS logs. You are on the Run Automated Processing page.
Step 1: Open the Process Monitor.
- Menu > PeopleTools > Process Scheduler > Process Monitor
Step 2: Click the CSUBAS process

Step 3: Click Refresh
Step 4: Scan the CSUBAS process list. - Confirm that each process resulted in a Success.
- If any process shows Error or Abend, open a Service Now support ticket.

View CSUBASDL process logs
Step 1: Click the process
- This example shows the CSU_PERM_DEL process. You need to review each of the listed processes.

Step 2: Click View/Log/Trace under the Action drop down menu

Step 3: Click to open or download each file.

Step 4: Review the log

Step 5: If the process has another file, click that as well.
- The file is downloaded to your browser’s download folder.

Step 6: Open the file to review the system changes of that process

Step 7: Click Return then Click OK


Appendix: CSUBAS log error issues
Review the Process Statuses on the CSU Process Status report to determine next steps. Refer to the eBenefits ESS OK to Reprocess cheat sheet to see if you can reprocess a eBenefits BAS event if it is flagged.
Location | File Name | What to look for | What to do |
---|---|---|---|
CSU_PERM_DEL | AE_CSU_PERM_DEL_[xxxxx].log | Did not end normally | Research* |
CSU_BA18003 | AE_CSU_BA18003_[xxxxx].log | Did not end normally | Research* |
BasActivityDeletes_[xxxxx].csv | Empty file** | ||
CSUBA01A | AE_CSUBA01A_[xxxxx].log | Did not end normally | Research* |
CSU_BA_EV_DT | AE_CSU_BA_EV_DT_[xxxxx].log | Did not end normally | Research* |
CSU_Health_Effective_Dates.txt | Dates that were changed by the process | Confirm dates are correct | |
CSU_Health_Effective_Dates_Errors.txt | Errors | Research: Void incorrect enrollment (page 39) | |
PSPBARUN | CBL_PSPBARUN_[xxxxx].log | Errors | Research* |
CSU_BAS_ACTP | AE_CSU_BAS_ACTP_[xxxxx].log | Processes that did not complete to Success | Look for errors that require a solution. |
Missing employee signature | Contact the employee to get the signature completed | ||
CSU_PERM_INS | AE_CSU_PERM_INS_[xxxxx].log | Warning, different perm event code already exists Already exists on health perm |
If applicable, determine the correct permitting code and delete the incorrect permitting event code. |
*Research the reason the job did not end. Resolve the issue. Open a Service Now ticket to restart the CSUBASDL job.
** BasActivityDeletes_[xxxxx].csv. The first time this process runs, it deletes BAS events for all campuses. This file is blank for all subsequent runs. To see the BAS events that were deleted, the campus must run a query
Appendix: Check Event Statuses
Review the Process Statuses on the CSU Process Status report to determine next steps. Refer to the eBenefits ESS OK to Reprocess cheat sheet to see if you can reprocess a eBenefits BAS event if it is flagged.
Event Status | Actions to take |
---|---|
AN | Assign No Benefit Program – verify that this is not a benefits eligible employee. If it is, verify that Job Data is correct. If Job Data is correct for a benefits’ eligible employee and the BAS event Process Status changes to FA, use the Review Eligibility Results process to determine why and the next steps to take. This process is in the Benefits Events Troubleshooting position paper. |
AS |
Benefit Program is assigned. This means that the benefit program has been assigned but the BAS event is awaiting processing because another BAS event is currently in processing. Next step is either PR or FP for the BAS event when it gets into Ben Admin processing unless an error occurs. Do nothing and check to see if this BAS event is processed the next day. If nothing happened the next day, see what BAS events are currently in processing. |
AE |
Assign Error - review and resolve the issue using the Benefits Events Troubleshooting position paper. |
PE |
Prepare Error – review and resolve the issue using the Benefits Events Troubleshooting position paper. Note that you currently have some BAS events with dates in 2025 that are in PE status, and they will remain that way until the 2025 Calendar Year (CY) Payroll calendars are created in HR9.0. You can fix and reprocess when this is a eBenefits BAS event. |
PR |
Prepared – the BAS event is awaiting data entry. You can go into the On Demand Event Maintenance page and checkmark the Finalize/Apply Defaults checkbox and then click on the Validate/Finalize button for HIR, ACT, MSC and TER BAS events to complete processing. TBC, LVE, DEA, CNC, HBE, FSA, LIF and RFL BAS events require research to determine next steps. Or, you can ignore the BAS events in this status and see if all other BAS events are processed after the next evening’s CSUBAS run and if not, review the next day to determine why. You can reprocess if needed when this is an eBenefits BAS event. |
NT |
Notified – the BAS event has been looked at, and elections may have been entered, but no elections have been submitted for processing. Review this BAS event if it does not leave this status after a couple of days. Do not reprocess this if this is an eBenefits BAS event. |
EE |
Election Error – the BAS event has an election error. If this is not an ESS BAS event, go into the On Demand Event Maintenance page and correct the election error and then finalize the BAS event. If this is an eBenefits BAS event, look on the BAS003 report (Invalid Elections report) to find the error and reach out to the employee and tell the employee how to resolve the error. |
ET | Entered – Elections have been entered for the BAS event. If this is a non-ESS BAS event, and the BAS event is HIR, TER, MSC or ACT, you can checkmark the Finalize/Apply Defaults checkbox and then click on the Validate/Finalize button in the On Demand Event Maintenance page if the BAS event is ready to be finalized. Do not touch ESS BAS events in an ET status on this page other than to do an ESS audit if you have already received the supporting documents and you are following the Audit Employee Benefits job aid instructions. |
RE |
Re-entered – Elections have been entered for the BAS event but have not been finalized. Ben Admin skips processing BAS events in the RE status. Determine why the BAS event is in the RE status and if you need to take action to finalize the BAS event if it is not voided or disconnected. Do not reprocess this if this is an eBenefits BAS event! If this is an eBenefits BAS event, chances are you are waiting to receive the supporting documents before you can perform your ESS audit. |
FE |
Finalized Enrolled – The BAS event is closed and finalized with a benefit program assigned and possibly benefits plans defaulted/elected. All BAS events in FE status can be reprocessed. |
FP |
Finalized Prep None – The BAS event is closed and finalized with a benefit program assigned but no benefits enrollments entered. The system determined that there’s no benefit options to change, or the employee is not eligible for any benefit options. All BAS events in FP status can be reprocessed. |
FA |
Finalized Ben Prog None - The BAS event is closed and finalized with no benefit program assigned and no benefits enrollments entered as the employee is not eligible for any benefit options. All BAS events in FA status can be reprocessed. |
End of Article
0 Comments
Add your comment