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

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.

Benefits Officer must review the following items daily.

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

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.

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.

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

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

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:

1. Select the active server
2. 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

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.

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

*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

End of Article