Configure Hierarchies

Hierarchies

A hierarchy enables you to define and customize the row structure of a report. With a hierarchy, you can group data into multiple row-levels and create a parent/child structure. When used with consolidated columns, hierarchies can be used to produce high-level management reports with the result set being aggregated based on the hierarchy definition.

You can utilize existing hierarchical structures already defined within an ERP system or you can create a user-defined hierarchy.

The inquiry in the below example has been consolidated by removing the Business Unit, Company and other columns, leaving only the Object Category Code 17 Column. In this inquiry, users can be made aware of how closely their firm is tied to one Parent Company for auditing requirements.

There are two ways to create a hierarchy:

Import a hierarchy from the underlying ERP system.
Create a user-defined hierarchy structure from scratch.

To start, go to the Inquiry Objects menu. In the Inquiry Objects group, click Hierarchies.

Within the Hierarchies dialog that is then displayed, the following actions can be carried out:

Create New hierarchical structures based on a user-defined specification
Import existing hierarchical structures based on pre-defined ERP data structures
For Oracle EBS users, Import FSG will import existing row sets
Export Excel exports the hierarchy structure to Microsoft Excel
Edit existing user-defined hierarchical structures
Rename an existing hierarchy
Remove an existing hierarchy
Set hierarchy indentation and Expand/Collapse functionality using the Grid Options button
Establish Calculation Precedence on any calculations in an existing hierarchy
Set a hierarchy to be a filter or grid hierarchy
Set the beginning account level in which a hierarchy will be displayed in the result set

Set whether the parent level in a hierarchy is displayed first in the result set

Import a Hierarchy

When you import a hierarchy, you are importing a pre-defined account data structure from your ERP system.

The following pre-defined hierarchy structures are available to import:

MODULE	TEMPLATE	STANDARD HIERARCHY
JD Edwards - General Ledger	Balances	Account Level of Detail (F0901) BU Structure (F0050) BU Style (F0006)
JD Edwards - Fixed Assets	Balances	Account Level of Detail (F0901) Asset Parent Child (F1201) BU Structure (F0050)
JD Edwards - Job Cost	Balances	Account Level of Detail (F0901) BU Structure (F0050) BU Style (F0006)
JD Edwards - CAM, Manufacturing	BOM	Item Number/Parent Child (F3002)
Oracle EBS - General Ledger	Balances	Financial Statement Generator (FSG) Account Hierarchy Company Hierarchy Department Hierarchy Product Hierarchy Sub-Account Hierarchy
SAP	-	Not available

From within the Hierarchies dialog, click Import. (Note that this button is disabled when creating a hierarchy in a module such as AP, AR, Tax and Homebuilder where there is no pre-defined hierarchy in the ERP system.)
Go through the wizard and choose which standard structure you wish to import.
Depending on which hierarchy structure you choose, you may need to make further selections:
1. When importing an Account Level of Detail hierarchy (based on data from the F0901 Account Master table), you are prompted to choose a business unit on which to base the chart of account structure for aggregation purposes. Clicking on Retrieve will update the Available list. Since the F0901 file can contain multiple hierarchical structures, you need to specify which business unit you wish to use.
2. When importing a BU Structure hierarchy (based on data from the Organization Structure Master File (F0050), you are prompted to specify the Organization Type. Clicking Retrieve will update the Available list. Since the F0050 table can contain multiple hierarchical structures, you need to specify which structure you wish to use.
Optionally, set the hierarchy to be dynamic, meaning it is automatically rebuilt when to include any changes to the structure in the ERP system. (Hierarchies can only be dynamic if they are imported. It is important to note that dynamic hierarchies cannot be edited since they must be the same as the structure in the ERP system.)
When you choose to make the hierarchy dynamic, you then choose at what time to update, either Update After Load or Update Before Run. The Dynamic Parameters Option designates what the hierarchy will be using for its update. This option may not be enabled based on the type of hierarchy structure being imported. (In the example of an Account Level of Detail structure being imported, you can choose to base the structure off of a specific Business Unit.) The Dynamic Update setting can be changed in the main Hierarchy dialog once the hierarchy is created.
Upon clicking Finish, you return to the main Hierarchy dialog.

Import an FSG

Oracle EBS customers can import a row set from EBS.

From within the Hierarchies, click Import FSG.
Going through the wizard, you can import a single FSG row set or make multiple selections from the Import from FSG dialog by using CLICK, SHIFT + CLICK or CTRL + CLICK to make selections.

Note: The default checkbox at the bottom of the window imports the row set formats as defined in EBS; uncheck to remove predefined formats.

Upon clicking OK, you return to the main Hierarchy dialog.

Create a New User-defined Hierarchy

A hierarchy can be built on any filter dimension (e.g. business unit, object account, category code). If it is built on multiple fields or elements, such as Object Account and Subsidiary, it is called a multi- dimensional hierarchy. To build hierarchies on group filtered items such as category codes or subledgers, you must first select the appropriate group in the filter before creating the hierarchy.

From the Inquiry Objects menu, click Hierarchies.
Click New to create a new hierarchy.
Provide a unique name for the hierarchy and select the fields (called “elements” in the hierarchy) to include by moving them from the left to the right panel. It is important to note that the fields must be displayed as columns in the inquiry in order to choose them from this list. Also, on some dimension fields, there may be further selections due to that field’s ability to have subtypes.

Note: If you choose subledger, you must define on which subledger type the hierarchy should be based.

Once you have selected all the dimensions you wish to use in the hierarchy structure, click OK to go to the Edit Hierarchy dialog to design your hierarchy.

Hierarchy Node Types

When creating the hierarchy, you can use the use the left panel to assist in determining data. The right panel shows the structure as you build it. The bottom left-hand panel shows your current selections; this is designed to assist users who are building multi-dimensional hierarchies.

The hierarchy is built as a tree-like structure, with the name of the hierarchy appearing at the pinnacle of the tree. This is known as the Root Node. You can now create nodes below the Root Node to form the structure of the hierarchy.

Nodes can be entered in any combination of three ways:

Double-clicking a value from the left-hand panel (note that there will be no values in this panel until the Find button is used - see below)
Making multiple selections from the left-hand panel using the CTRL and SHIFT keys
Adding a node manually

Edit Hierarchy Dialog - Choosing Values from the Left-hand Panel

Click on the Find button to return the available selections from the fields on which the hierarchy is based. If necessary, prior to clicking on the Find button, further filtering criteria can be applied by using Query By Example (QBE) to restrict the list of possible selections.

In the below example, we have narrowed down our results by entering Company 3 in the QBE field:

Double-clicking on a value will populate the value in the right-hand panel of the dialog, as does highlighting the value and then using the arrow in the middle to move it to the right. In the example below, the hierarchy node shows both dimensions that you have chosen, in this case Business Unit and Object Account. Note that the system will automatically default any unspecified dimensions as an asterisk, for example 302-*-Denver. This indicates ALL values for that dimension are chosen by default. So in this case, all object accounts are included.

Note: The default setting is set so that an asterisk represents “all”. To change this so a blank value represents “all,” change the setting at the bottom of the screen:

Edit Hierarchy dialog: Making Multiple Selections

You can select multiple values using the CTRL+ LEFT CLICK or SHIFT + ARROW keys. As you select the values, they populate the panel at the bottom left-hand side of the dialog.

The benefit of this is that when you click on another dimension, you can still see what you have previously selected under the other tab. Below you see that after clicking on the Object Account dimension, the Business Units are still visible at the bottom, easing the hierarchy creation.

The value under Object Account in the selections field is still an asterisk or wildcard. This is because we have yet to define which object accounts we want to include.

When choosing the second dimension, you can also select multiple values using the same method as before. The below example shows the selections screen after choosing several objects. The Currently Selected Combinations is 9 (3 business units x 3 object accounts). Once you have specified all values, click on the double arrow to the right of these entries to show all the value combinations:

The Add Hierarchy Items dialog shows all the potential combinations of the values you selected. From here you can select all of the combinations required to add them to your hierarchy. If you require all selections, the easiest method to achieve this is to click Select All at the bottom right-hand side of the dialog.

The results of the above selection are shown here:

Edit Hierarchy Dialog: Removing Selections within a Hierarchy Node

The previous example showed the generation of a small number of hierarchy nodes. The Hierarchy Editor also provides a safety feature to prevent too many rows from being automatically generated by accidental dimension combinations. Below is an extreme example, where numerous Business Unit and Object Account nodes have been selected:

If you try to add that many node combinations to the hierarchy, a warning appears, asking if you want to continue. This warning message is controlled by the Settings section of the Add Hierarchy Items dialog. The default for this is 1000, but this can be adjusted depending on the hierarchy size requirements.

Edit Hierarchy Dialog: Manually Adding a Hierarchy Node

There are two ways to manually add a new node:

Highlight the item within the hierarchy under which you want to place the new node, right-click and select New Entry. In the case where you are adding a node for the first time, the name of the hierarchy itself should be selected in the right-hand panel.
Click on the New Entry button in the upper left-hand corner of the dialog:

Both ways bring up the New Hierarchy Entry dialog. Click the drop-down list next to Choose the type to select the entry type:

There are three types of node entries that can be created in the hierarchy:

Normal Entry – Specify actual values in the hierarchy dimension.
Label Entry – Create a label or header node to roll up data into a parent node.
Calculated Entry – Create a row-based calculation.

Normal Entry

Literal values are specified in normal entries for the fields/elements specified when first setting up the hierarchy.

Name: Unique name (name given by the system upon setting the field values).
Description Override: Name displayed in hierarchy results.
Display: Choose to display this entry always, never, or only when there is a balance.
Reverse Signs: Reverse signs for entries under this node.

Note: The Reverse Signs setting is only recommended for Oracle ERP system users; for JD Edwards ERP system users it is recommended to reverse signs through Formatting rather than through this setting.

Roll values up into this one: Use this as a rollup level or parent node.
Field Values: Specific values are entered here and can include a single data item, range of items, or wildcard (*). You can either manually type in the values or use the Visual Assist to select them.
Expansion Setting: If multiple values are defined, you can show the Total (total of these items in 1 line), Expanded (each line shown individually), or Both (total and expanded).

Label Entry

Label nodes do not contain data themselves, but rather are used to group together selected items or other nodes that are aggregated, with the resulting calculation stored at this level.

Name: Unique name.
Description Override: Name displayed in hierarchy results.
Display: Choose to display this entry always, never, or only when there is a balance.
Reverse Signs: Reverse signs for entries under this node (note that this setting is only recommended for Oracle ERP system users; for JD Edwards ERP system users it is recommended to reverse signs through Formatting rather than through this setting).
Roll values up into this one: Use this as a rollup level or parent node.

Calculated Entry

The row-based calculations feature allows you to generate new rows in your inquiry that are derived from existing rows or from existing rows and columns.

Note: It is important to note that calculations do not roll up to other nodes as do other items in the hierarchy.

Name: Unique name.
Description Override: Name displayed in hierarchy results.
Display: Choose to display this entry always, never, or only when there is a balance.
Calculation Expression: Definition of the calculation once it has been defined.

Define a Hierarchy Calculation

The following steps define a hierarchy calculation:

Create a new hierarchy node, selecting the Calculated Entry type.
Click Define to set the default and/or conditional calculation.
This functionality mirrors our standard column calculation functionality. The only functionality not present is Execute Calculations for totals, due to the way that totals often duplicate the par- ent records in a hierarchical structure.

Here you set a default calculation and/or Conditional Overrides. In this example, we will add a default calculation for Product A Percentage.

After clicking Define, add elements to the calculation and expand the tree view until you can see the item(s) on which to build the hierarchy.
Double-click an item to add it to the calculation panel and click the mathematical symbols to add them to the calculation. You can also input numbers by typing them directly into the panel.

Once selected, items appear in the definition in the top portion of the dialog. In this example, we are taking the Product A Revenues (Object Account 5002) divided by the Product Revenue node and multiplying by 100:

Click OK to return to the Edit Calculation dialog. You see the default calculation has been saved.
Click OK to return to the Edit Hierarchy dialog. Now we see the calculated node within the hierarchy structure:

Continuing in this example, we will add three more calculations:
1. Product B % = ({Revenue Analysis.5003.*} / {Revenue Analysis.Product Revenue.}) *100
2. Product C % = ({Revenue Analysis.5004.*} / {Revenue Analysis.Product Revenue.}) * 100
3. Percentage Reconciliation = {Revenue Analysis.Product A %.} + {Revenue Analysis.Product B%.} + {Revenue Analysis.Product C %.}

You see the calculations once the inquiry is run:

Note: The Product Reconciliation calculation was added to verify that the other calculations add up to 100%.

Referencing a Column in a Hierarchy Calculation

Hierarchy calculations can also be linked to specific columns in the inquiry. Within a GL Balances inquiry, these would normally be Ledger, Period or Year. However any column can be referenced as long as it is pivoted.

In the following example, Periods 1st Half (H1) and 2nd Half (H2), Year 2006 and Ledger AA are selected via their respected filters.

To create the hierarchy calculation, complete the following steps:

Create a new hierarchy node, selecting the Calculated Entry type.
Click Define to set the default and/or conditional calculation. You will use the period in the calculation definition.
In this example, the calculation is defined as follows. To define the period, use the drop-down list, which currently shows Revenue Analysis, to select Period and then double-click on Period H1. Be aware that there is no mathematical symbol between {Revenue Analysis.5002.*} and {Period.H1}.

Note: If you had not selected any specific periods in the inquiry filters, the periods offered in the Edit Default Calculation dialog would be Current and Cumulative. You would just need to click on the Search button to search for other periods that are not currently included in your filter.

Click OK to finish the calculation. The new calculation will appear at the bottom of the result set:

The calculation value in the H1 column will equal 100% as it reflects the node being divided by itself. The calculation value in the H2 column will reflect the intersection of Revenue Analysis.5002.* and H2 Divided by Revenue Analysis.5002.* and H1 Or (-24,785,199.08 /-20,362,419.46) *100 = 121.72

Example: Create a Column Calculation to Calculate Percent of Sales

The following example outlines the steps to create a column calculation and reference a hierarchy node in order to calculate % of Sales.

Make sure that the applicable hierarchy is selected in the Grid Hierarchy filter.
From the Inquiry Objects menu, click Calculations.
Click New to open the Define New Calculation dialog.
Enter a name, caption and, optionally, a category.

Click Define to open the Edit Default Calculation dialog.

When defining the calculation, use the drop-down control to select the hierarchy:
In this case, the calculation definition is:

({Period.H1} / {Period.H1}{Business Unit Revenue Analysis.Total Sales.})*100

Click OK to return to the Define New Calculation dialog.
Click OK again to return back to the Calculations dialog.
In the Calculations dialog, check the box next to your new calculation to make it active and then click OK to exit.
Run the inquiry, and you will see an additional column with the calculation caption of “% of Total H1:
The new column will display every H1 Period value divided by the Total Sales for the 1st Half of 2006.

Conditional Row-based Calculation

In a hierarchy calculation node, you can set a conditional override to be used when the calculation is to be performed under certain conditions.

In the following example, we will show how to set a calculation definition depending on the ledger type in the column. For the AA or General Ledger, we will bring back the AU or Actual Units. For the BA or Budget Ledger, we will bring back the BU or Budget Units.

To add a conditional row-based calculation, follow these steps:

From the Inquiry Objects menu, click Hierarchies.
Select the appropriate hierarchy and click Edit.
Create a new entry, modifying the type to Calculated Entry and using a descriptive name:
Click Define to open the Edit Calculation dialog. Conditional row-based calculations can include the Default Calculation, however for this example we will be using Conditional Overrides. Disable the Default calculation and enable the Conditional Overrides check box.
Click New to open the Define Calculation Condition dialog.
Specify the condition where Ledger is equal to AA:
Click OK to proceed to the Calculation dialog. Select Ledger from the drop-down control. The specific ledger we need is not included within the previously defined filters, so click Search to find the AU Ledger:
Double-click on the AU Ledger and then add the Product Revenue node to the calculation. The combination of the two means that the calculation will display the total for all units associated with Product Revenue.
Click OK to return to the main Calculation dialog.
With the first condition complete, now the Budgeting Unit condition needs to be added. Within the Calculation dialog, click New to create a new Conditional Override.
Within the Define Calculation Condition dialog, create a new condition where Ledger = BA:
Following the same steps as the previous condition, create a calculation which is based on the BU Ledger and Product Revenue:
Click OK to return to the main Calculation dialog. Both conditions are displayed in Conditional Overrides:
Click OK through the various dialogs to return back to the main result set. Once you run the inquiry you will see that the AU (General Ledger Unit) results are appearing in the AA Ledger column. Likewise the BU (Budget Ledger Unit) results are appearing in the BA Ledger column.

Editing Hierarchy Elements

Once a hierarchy is created, you can still change the elements or fields on which the hierarchy is based. To do this, go to Hierarchies on the Inquiry Objects menu. Highlight the hierarchy you wish to edit and select Edit to launch the Edit Hierarchy dialog.

The toolbar is located in the upper left-hand corner of the dialog.

Note: You can hover over each button to read the help text for that particular function.

Clicking on the first button allows you to edit the hierarchy fields. Using the arrows in the middle, you can remove or add selected fields to the hierarchy. The fields on the left panel are the available fields to use, and those on the right panel are the fields that have been selected to be used in the hierarchy.

Editing or Deleting a Hierarchy Node

There are three ways that a node can be edited or deleted:

Right-click on the relevant node and selecting the Edit Entry or Remove Entry option.
Highlight the node you wish to remove and click the Remove Hierarchy Entry button in the upper-left corner of the screen:
Highlight the node you wish to remove from the structure, and then click the left arrow in the middle of the screen to move it from the right to the left panel.

Re-positioning Hierarchy Nodes

Nodes can be reorganized at any time either by changing the level of detail at which a node resides, or the order in which nodes are presented within a level. You can either drag and drop nodes, or highlight the node to be moved and then click on one of the following buttons at the bottom right of the dialog:

ICON	EXPLANATION
	Moves the selected node up the hierarchical structure, e.g. from level of detail 2 to 1
	Moves the selected node down the hierarchical structure, e.g. from level of detail 1 to 2
	Moves the selected node to a position before the previous node within the hierarchical structure
	Moves the selected node to a position after the next node within the hierarchical structure

Searching within a Hierarchy

The Hierarchy dialog contains a search field in the top right, allowing for quick retrieval of nodes on large hierarchical structures. In the example below, searching on “Cost of Sales” will highlight that node in the hierarchy:

Export a Hierarchy Structure

From the Inquiry Objects menu, click Hierarchies.
Highlight the selected hierarchy.
Click Export.
You will be prompted you to save the file as a .csv file.

Hierarchy Grid Options

Options Tab

Within the main Hierarchy dialog, click the Grid Options button to set the following options within the Options tab:

Indentation - in the result set, each level of the hierarchy will be indented to illustrate the different levels. The default setting is Indent Children, where the bottom level items get indented the most; however this can be changed to No Indentation or Indent Totals.
Expand/Collapse - setting that allows you to expand and collapse the nodes in a hierarchy. This is an example of all nodes in the hierarchy rolled up to the top level:
By expanding the hierarchy, we see the children and descendant nodes:
It is important to note that the Expand/Collapse functionality will only work when:
- Fields/elements that are part of the hierarchy are columns within the inquiry.
- Subtotals are disabled (grand totals can be displayed however).
- The hierarchy dimension is the lowest in the label sort order. This means that within Column Sorting and Grouping, in the Sorting & Grouping tab, the hierarchy dimension is below any other label columns in the sort order).
Show Zero Headers - by default, when you are not displaying Zero Balances in the inquiry, parent nodes in a hierarchy that are equal to zero are suppressed. You can enable this option to force them to be displayed.

Consolidation Tab

Within the Consolidation tab in Grid Options, a custom column aggregation such as total, count, average, minimum, and maximum can be consolidated on the parent node of a hierarchy.

In the following example, a hierarchy was created in the Sales Module to show the different customer address numbers with sales records for various branch/plants. Then a calculation was created to count the sales orders for each customer within the respective branch/plant.

When the consolidation option is turned on for the count calculation, the hierarchy parent node totals up the number of sales orders:

If you turn off this option, a parent node is created for each value in the count column since this column is not an element in the hierarchy:

Hierarchies Dialog Settings

There are four items under Hierarchy Settings:

State – Select whether the hierarchy is a filter hierarchy (active or inactive) or grid hierarchy
Dynamic Update – If the hierarchy is dynamic, this option determines whether it will be updated after loading or before running the inquiry.
Starting Level – Set the starting level of the hierarchy that displays upon running the inquiry
Parent First – Set whether the top or parent node in the hierarchy displays first in the inquiry

Hierarchies and Calculation Precedence

As Hubble gives you the option to define calculation intersections, it is important to specify in which order calculations should be executed. The Calculation Precedence feature allows you to control the sequence of calculations.

To change the sequence of calculations:

From the Inquiry Objects menu, select Calculations to open the Calculations dialog.
Click Calculation Precedence and this will open the dialog:
The default settings for calculation precedence ensure that calculated hierarchy items are run before column calculations. To override this setting, uncheck the Automatic checkbox.
Use the blue up and down arrows to rearrange your sequence.
Click OK to accept the sequence and exit the dialog.

Hierarchy Filter

Once your hierarchy is created, select it in the Grid Hierarchy filter as shown in this example:

If you have Grand Total or Totals enabled in your inquiry, the Conflicting Features dialog displays, asking if you would like to turn off totaling. Having both totaling turned on as well as displaying a hierarchy can result in duplicated rows, so it is recommended to click Yes to disable the totaling functionality.

When the hierarchy is selected, the hierarchy filter is displayed to the right of it. In this field you can designate an asterisk (*) to display all hierarchy levels or, if you click in the filter, the Visual Assist appears.

The green button to the right of the hierarchy filter is a quick status change feature. Clicking this will disable the hierarchy and the filter is grayed out.

Within the Hierarchy Filter Visual Assist, there are three methods of filtering, controlled in each of the tabs:

Search
Levels
Hierarchy

Click on the Search tab to view this filter and then click on the Find button to reveal the associated data. The Search tab reveals the individual nodes of the hierarchy.

In the Search tab, the Level column indicates the placement of the node within the hierarchical structure. The Sequence Number is an internal code that is used to represent the nodes.

Hierarchy filter: Levels tab in Visual Assist

Click on the Levels tab to view this filter and then click on the Find button to reveal the associated data.

The selections that are available within the Level of Detail filter are dynamic and specific to the hierarchy with which you are working. Examples of the top 3 levels in the Business Unit Revenue Analysis hierarchy are as follows:

LEVEL OF DETAIL	NODE REPRESENTED	EXAMPLES
1	Parent Node	Total Sales
2	Nodes below Parent Node	Product Revenue
3	Nodes below Level 2 Nodes	5002 - Product A Revenues

As an example, select Levels 1 and 2 in the filter:

The hierarchy filter now looks like this:

After re-running the inquiry, your displayed data is narrowed down to levels 1 and 2 within the hierarchy:

The Levels filter can be used to select a set of levels within a hierarchy by using a colon such as this: LEVEL(1:3). Other available operators that can be used are =, <, > <=, >= and <>. For example, you can search on everything except for Level 1 like this: LEVEL(<>1). Likewise LEVEL(>4) would use all levels deeper than 4. The default operator = means that LEVEL(3) and LEVEL(=3) are equivalent and use all items at level 3 in the hierarchy.

Hierarchy Filter: Hierarchy Tab in Visual Assist

The Hierarchy tab is an ordered view of the Search tab data that matches the original hierarchical structure.

You can select items to be displayed in the hierarchy by moving them to the right panel.

Advanced Hierarchy Filtering: Use of Hierarchy Selectors

The Search and Hierarchy tabs found in the Hierarchy filter have an activated control that allows for greater selection of hierarchy nodes. When a hierarchy node has been selected, this control is enabled:

It is possible to specify a subset of the hierarchy to use in the inquiry with combinations of the keywords below:

SELECTION	HIERARCHY LEVELS
Descendants Only	Use all levels below the item
Children Only	Use next level down from the item
Item Only	Use a single element on the hierarchy
Item & Descendants	Use item and all levels below
Item & Children	Use item and the next level down
Level	Use items from particular levels

Note: It is possible to use combinations of selectors for different hierarchy nodes.

Adding a Drop-down Filter for a Hierarchy

Users with a Configurator License can add a drop-down filter for a specific hierarchy.

From the Configurator menu, click on Filter Layout.
Expand Controls in the left-hand corner.
In a blank area within the Workspace Area, drag and drop the Drop Down Filter item.
Expand Filters, then Hierarchies, then either Grid or Filter Hierarchies. (depending on which one you are using in your current inquiry.)
Drag and drop the specific hierarchy onto the blank area that already has the Drop Down Filter item.
Click OK to apply the changes and exit the dialog.
Back in the main inquiry screen, you see the hierarchy filter. By default, the hierarchy setting defaults to display Item and Descendants; to change this, click the Hierarchy Filter Query Assist:
Here you can change the current selection(s) as well as change which items are to be displayed using the Selector drop-down menu in the bottom right-hand corner of the dialog:

Filter Hierarchy

While grid hierarchies are used to display data in a specific structure, filter hierarchies are used to display a chosen subset of information within an inquiry.

By default, all hierarchies are Grid Hierarchies. They can be changed to be Filter Hierarchies through the State setting, which is displayed within the main Hierarchies dialog.

A hierarchy may be selected as a Filter Hierarchy, but only one Filter Hierarchy can be active at one time. It is also possible to use a hierarchy as a filter on another hierarchy.

The hierarchy filter has a quick status change feature, where a green button is displayed for enabled hierarchies. To disable the hierarchy, click on the green button:

Note: The ability to add new filter hierarchies using Filter Layout requires a Configurator License. Filter Layout is accessed through the Configurator menu.

Below is an example of using a filter hierarchy in a purchase order report for expected items. The hierarchy is based on type of bike. By selecting various nodes, the result set will reflect the bike type selected. In this example you can filter on All bikes, Sport Bikes, Road Bikes, or accessories. You can even limit the selection to display purchase order data for Blue Road Bikes in particular:

Hierarchies and Formatting

There are two types of hierarchy formatting:

Hierarchy Levels – formatting is applied to general levels within the hierarchy.
Hierarchy Rows – formatting is applied to specific rows within the hierarchy.

Hierarchies and RIO

A user with a Configurator License can add a hierarchy to the RIO, or Reusable Inquiry Objects, making it available to other users in order to use it in their inquiries.

Add a Hierarchy to RIO

Open the inquiry where the item exists.
From the Inquiry Objects menu, click Reusable Inquiry Objects.
Highlight the hierarchy on the left panel to be moved into Reusable Inquiry Objects.
On the right panel, highlight the folder under which you want the hierarchy.
Click the arrow in the middle of the screen to move the hierarchy over to the right.

Subscribe to a Hierarchy from RIO

Open the inquiry in which you want to subscribe to the hierarchy.
From the Inquiry Objects menu, click Reusable Inquiry Objects.
In the right panel, subscribe to the hierarchy by checking the box to the left of it.
Click either Apply to apply the hierarchy or OK to apply the item and exit the dialog at the same time.