CHRS Knowledge Base

Add BU to BA ESS Provisioning Queries

Updated on

Overview

1. Campus Setup

Each campus is either:

  • Benefits Full ESS
  • Benefits View Only ESS
  • Two dynamic queries handle provisioning/de-provisioning of eBenefits ESS roles, depending on the campus setup

2. How the Dynamic Queries Work

  • Queries assign or remove the Benefits ESS role for benefits-eligible employees:
    • Benefits eligibility = JOB_ELIG_FLD_1 = Y OR JOB_ELIG_FLD_3 = Y
    • Role is assigned to the User ID of the Benefits Primary Job (BPJ) campus.
    • Payroll status must be Active (A), Short Work Break (S), or Paid Leave (P).
  • Queries remove Benefits ESS access if:
    • Employee is not benefits-eligible (JOB_ELIG_FLD_1 or JOB_ELIG_FLD_3 = N), OR
    • Payroll status = Terminated (T), Suspended (U), Retired (R), Quit (Q), Leave (L), Withdrawn (W).
  • Queries run daily at 4am, 10am, and 4pm.

⚠️ Do not manually assign/remove Benefits ESS roles.

Manually changed roles are ignored by the dynamic queries.

3. Turning on Benefits ESS for a Campus

  1. Campus must submit a ServiceNow ticket requesting their Business Unit be added to the provisioning/de-provisioning queries.
  2. Adding the Business Unit is the final step to "turn on" Benefits ESS for a campus.
  3. Best practice:
    • Wait 3–4 weeks after CHRS go-live before activating Benefits ESS.
    • This allows time for conversion cleanup and stabilization.

4. Queries Used

  • CSU_SEC_CHR_SS_BENEFITS_FLUID → for Full ESS campuses
  • CSU_SEC_CHR_SS_BENEFITS_FL_CL → for View Only campuses

5. Examples

Example 1: STA is BPJ (View Only Campus)

  • Employee works at Stanislaus (STA) and Fullerton (FUL).
  • STA owns BPJ → employee gets View Only Benefits ESS on STA User ID.
  • FUL User ID → no Benefits ESS role.

If STA EMPL_STATUS changes:

  • To T, U, R, Q, W, L → View Only role is removed from STA User ID.
  • To T, U, R, QFUL becomes BPJ. If eligible, employee is provisioned Full ESS on FUL User ID.
  • From W or L → A or P → View Only ESS is restored on STA User ID

Example 2: FUL is BPJ (Full ESS Campus)

  • Employee works at STA and FUL.
  • FUL owns BPJ → employee gets Full ESS on FUL User ID.
  • STA User ID → no Benefits ESS role.

If FUL EMPL_STATUS changes:

  • To T, U, R, Q, W, L → Full ESS is removed from FUL User ID.
  • To T, U, R, QSTA becomes BPJ. If eligible, employee is provisioned View Only ESS on STA User ID.
  • From W or L → A or P → Full ESS is restored on FUL User ID.

Key Takeaways

  • ESS access is automatic via queries—never assign manually.
  • Campus must request Business Unit setup in ServiceNow to activate.
  • Wait a few weeks post-conversion before Benefits ESS go-live.

Instructions to Add Business Unit to BA ESS Security Provisioning Queries

  1. Step 1. Confirm your campus is ready to activate Benefits ESS.
    • Ensure conversion cleanup and stabilization tasks are done.
  2. Step 2. The designated campus resource must create a ServiceNow (SN) ticket.
  3. Step 3. In the SN ticket:
    • Indicate whether your campus needs Benefits View Only ESS or Benefits Full ESS.
    • Include:
      • Campus name
      • CHRS PeopleSoft Business Unit
      • Add these details in both the Short Description and the Description fields.
  4. Add watchers to the ticket:
    • Key Wave users for your campus
    • CMS-Benefits team:
      • Sande Meith
      • Lizbeth Henson
      • Mahesh Patel
      • John Osburn

Example SN Ticket Requesting Dynamic Query set up for Benefits View Only ESS Security Provisioning

Example SN Ticket Requesting Dynamic Query set up for Benefits Full ESS Security Provisioning

End of Article

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Do you need an article? Contact Us