Databases Reference
In-Depth Information
15. Now to test your query you simply right-click on the Microsoft Excel
worksheet that you are designing the query under and click on
Apply Query
.
The data with the layout you defined will be pulled into the Microsoft Excel
worksheet. Remember to also save your query with the same rules as any
Essbase file object. You now have a reusable query that you can use anytime
by simply opening through EQD and running it.
16. Oh yes when you save the query, Essbase saves it with an
.eqd
extension
and at the same time saves the query as the equivalent Essbase report script
with a
.rep
file extension. The actual query can only be opened by the EQD
but the report script can be opened by any ASCII text editor and modified
for use with any report script execution method described earlier.
Report script by-product
Previously, we explained the Essbase report script and its usefulness as a reporting
tool or as a method of creating extract data from your Essbase database. A desirable
and welcome by-product of an Essbase query created with the EQD is a matching
Essbase report script.
One of the easiest ways to create an Essbase report script is to use the EQD to
design what you would like your report or extract file to look like, then use the
simultaneously generated report script file to use and modify as needed. This
is your basic Essbase report script:
// This Report Script was generated by the Essbase Query Designer
<SETUP { TabDelimit } { decimal 13 } { IndentGen -5 } <ACCON <SYM
<QUOTE <END
<PAGE("METRIC")
<COLUMN("Calendar Periods")
<ROW("Total Market","Model Year","Total Vehicles")
// Page Members
// Selection rules and output options for dimension: METRIC
{OUTMBRNAMES}
"Gross Stock"
// Column Members
// Selection rules and output options for dimension: Calendar
//Periods
{OUTMBRNAMES}
<Link ((<LEV("Calendar Periods", "Lev0,Calendar Periods")) AND (
<IDESC("2009")))
<Link ((<LEV("Calendar Periods", "Lev0,Calendar Periods")) AND (
<IDESC("2010")))
// Row Members
