This document is intended to provide users with answers to frequently asked questions about various aspects of creating queries in CHRS.
General
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.
Private Queries
Yes.
Public Queries
No.
Campuses can either submit a Change Control requesting the query be created by CMS in CHRS as public or submit a Change Control to have it created in CHRS Reporting (Quicksight).
The campus can either recreate the public query as a campus private query or submit a Change Control requesting a modification.
To change a private query to a public query, the campus must submit a ServiceNow ticket. So to answer the question above should simply be submit a change control and attach their private query for CMS to use as a basis
Implementing Campus Specifics
- 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.
- 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;
End of Article