It is 3-letter Campus Code_2-letter Module Code_Name with_between words.

Each module tile includes a Troubleshooting/FAQ section that lists the resolved queries for that specific module. 

A Private Query is a query created by an authorized campus user that is:

• Saved within their campus environment
• Not available system-wide
• Shareable only within the same campus

Private queries are intended to meet campus-specific reporting needs.

Only users granted Query Development Access may create private queries. This access should be limited to:

• Technical users
• Designated power users
• Individuals who have completed proper query training

Campuses are expected to keep this group small.

Only users granted Query Development Access may create private queries. This access should be limited to:

• Technical users
• Designated power users
• Individuals who have completed proper query training

Campuses are expected to keep this group small.

Yes. The creator of a private query can share it with other users within the same campus.
Private queries are not automatically visible to all users.

No. Queries will not be migrated from 9.0 to 9.2. Campuses must recreate needed queries in CHRS.

Yes. The creator of a private query can share it with other users within the same campus.
Private queries are not automatically visible to all users.

A Public Query is a query that is available to all CSU campuses.
Unlike private queries, public queries are stored in the public folder and can be run by authorized users system-wide.

No. Only the Chancellor’s Office support team has the authority to create and save public queries.

A campus should request a public query when:

• The query benefits multiple campuses
• The data cannot be obtained through:
  • CHRS Baseline delivered reports
  • CHRS Reporting tools
• The query cannot be replicated using ad hoc reporting

If the requirement is campus-specific, it should remain private.

The campus can either recreate the public query as a campus private query or submit a Change Control requesting a modification.

A campus should request a public query when:

• The query benefits multiple campuses
• The data cannot be obtained through:
  • CHRS Baseline delivered reports
  • CHRS Reporting tools
• The query cannot be replicated using ad hoc reporting

If the requirement is campus-specific, it should remain private.

To request a public query:

1. Develop and test the query as a private query in production
2. Confirm it meets system-wide need
3. Submit a ServiceNow ticket
4. Include the name of the tested private query

The Chancellor’s Office will review and determine whether to publish it.

A request may be denied if:

• The requirement is campus-specific
• The report can be created in CHRS Reporting
• The query duplicates an existing public query
• It exposes sensitive data without proper controls
• It lacks sufficient justification

1. Ensure queries are written with the “3-letter Campus Code_2-letter Module Code_Name with_between words”. Business Unit must be part of the criteria in queries.
2. Campuses should retrofit any query that still utilizes SJT tables, which have not been a part of CS since the HR/CS split.

The following SQL identifies custom queries created in your system from the PSQRYDEFN PeopleTools table. It includes the query type (and the operator ID who owns the query if it is private).

select

QRYNAME as "Query Name",

DESCR as "Query Description",

CREATEOPRID as "Created By",

CREATEDTTM as "Created On",

LASTUPDDTTM as "Last Updated On",

LASTUPDOPRID as "Last Updated By", case when OPRID != ' ' then 'Private - ' || OPRID else 'Public' end as "Query Type",

VERSION as "Revisions",

QRYAPPROVED as "Query Approved?",

APPROVEOPRID as "Approved By",

APPROVEDTTM as "Approved On"

from PSQRYDEFN

where LASTUPDOPRID != 'PPLSOFT'

order by QRYNAME;