Design a Query

...

Design a Query

Definition

This form is used to expedite the design of new user-defined queries.

It is for your use only. It is a training tool and not a required document.

1. What is the purpose of the report and who needs to see it?

2. Define all elements required.

3. Describe additional elements that would enhance the data.

4. Determine if the data required is captured in IS and in which tables.

5. Review Predefined reports in Discoverer Plus to determine whether the report you need already exists.

6. What is missing? Is it available?

7. Determine the restraints required.

8. Determine any design requirements for the finished report.

Business Purpose

1 Business Purpose



Requestor
Date Requested		Date Required
Query Designer		Intended Audience

Data Requirements / Oracle Table / Location in IS or SIS

2 Data Elements Required					IS Module Location of data
1.
2.
3.
4.
5.
6.
7.
3 Additional desirable elements




	4 Request Details
	Is data captured in IS?
	Which Module or Modules?
	Which form within the module(s)?
	Level of access needed to see the data in IS?

Review Existing Reports

5 Predefined reports reviewed	Valuable Elements for Query Being Designed

Additional Information Needed

6 Needed Data elements not included in reviewed predefined reports		Available? Y/N

Constraints / Format

7 Constraints/Conditions/Parameters Required		If Yes / specify preference
Date constraint needed?
Date range needed?
Limit by Org, MBU, Other?

Distribution

ODS Specialist

ODS Specialist-Limited

ODS Specialist-Restricted

Ownership

The Administrator Operational Data Store (ODS) is responsible for ensuring that this document is necessary, that it reflects actual practice, and that it supports University policy.

Effective: 7/1/2010

Revision: 1