When you query against an Essbase cube, by default the CubeQuery section is created in the Interactive Reporting document. To use this section, you must have access to an Essbase 7.x or 9.x server data source. Interactive Reporting also requires an Essbase 9.3 Runtime or greater client installation.
To create a CubeQuery section:
Select Tools, then Options, then Program Options, then OLAP and then clear Use Old OLAP Query section.
By default, new Essbase queries use the new section type (CubeQuery).
Select Insert, then New Query.
The Insert New Query dialog box opens.
Select an Interactive Reporting database connection file (.oce) associated with an Essbase 7.x or 9.x server used as a data source.
For information on connecting to Essbase, see Connecting to Essbase (CubeQuery only).
Enter your name in the Host Name field and password in the Host Password field and click OK.
Interactive Reporting creates a Query section in the Section pane. The Catalog shows the dimensions available to add to the query.
To toggle the Catalog between single and all dimension modes, click .
In the Catalog, select a member dimension and select Query, then Add to Rows or Query, then Add to Columns.
Note: | Members from the same dimension cannot be split across columns, rows and filters. |
In the Catalog, select a measure dimension and select Query, then Add to Rows or Query, then Add to Columns.
To filter a member, select a member in the Catalog and select Query, then Add to Filters.
Note: | If missing values are not displayed, missing rows and columns may be suppressed. This option is enabled in Query options. |
Note: | When using Essbase metaread filters that restrict Essbase metadata/members for specific users or groups, a user may see member in the Interactive Reporting document file that do not have metaread access in Essbase. This results because Interactive Reporting document files save data and metadata in the physical file. When the query is processed, they may then receive an “unknown member” error because they may not have access to one or members in the query due to their metaread access. When using CubeQuery with metaread filter access, the following is recommended. First, dynamic member selections (for example. Children, Descendants, etc.) should be used for any dimensions that have metaread filters applied. Second, members that users might not have access to should not be individually selected. Third, do not process the query before saving and/or publishing the Interactive Reporting document file. |