When testing a recursive hierarchy, the Intersection and Column Value fields of the Drill-through Report Testing dialog box are used differently than when testing a standard hierarchy:
In the Intersection field, the recursive hierarchy name is displayed.
In the Column Value field, a parent or child column name is entered, not a data value.
This is illustrated in the following example scenario.
Note: | The example procedure assumes (1) that you have created a data source connection to the sample TBC database, and (2) that you have created a minischema of the TBC source which contains a self-join between the PARENT and CHILD columns of the MEASURES table. |
To test a recursive hierarchy selected for drill-through:
Create a recursive hierarchy called “recursive_hier” with the PARENT column from the MEASURES table as the parent level, and the CHILD column from the MEASURES table as the child level.
Note:
Ensure that you have created a minischema which contains a self-join between the PARENT and CHILD columns of the MEASURES table
Create a cube schema and Essbase model using the “recursive_hier” hierarchy you created in step 1; use AMOUNT from 'TBC.SALES' as the measure.
Create a drill-through report as specified below:
In the Context tab, add the “recursive_hier” hierarchy you created in step 1.
In the Report Contents tab, place any fields from TBC.PRODUCT, for example: CAFFEINATED or PKGTYPE.
Click Test to launch the Drill-through Report Testing dialog box.
Note that the Intersection field contains the name of the recursive hierarchy, “recursive_hier.”
In the Column Value field, select a column name; for example, select COGS.
Note:
A column name is used here, not column data.