WebFOCUS Online Help > InfoAssist > Hierarchical Reporting in InfoAssist > Creating a Report With a Multi-Dimensional Data Source
In this section: |
You create a report using a multi-dimensional data source in InfoAssist the same way you would if you were reporting from any other type of data source. For both level and parent/child hierarchy models, most reporting functionality is available. One of the differences between reporting against a multi-dimensional data source and reporting against another type of data source is that you have additional folders that group related fields in the Data pane. These cube-related folders are Variables (SAP BW), Measures, Characteristics, Hierarchies, and Properties. See Viewing the Field Lists.
In addition, the following features are available for hierarchies that use the parent/child model. (If you are working with the level hierarchy model, you can still sort and screen data using the traditional methods.) These include:
There are specific reporting rules that apply to multi-dimensional data (parent/child and level). When you use InfoAssist these rules are automatically enforced. See Summary of Reporting Rules For Multi-Dimensional Data Sources for more information.
When you are creating a report with a multi-dimensional data source, you see the following additional folders in the data pane field lists.
Variables can appear in your fields list as optional or mandatory. Variables cannot be used as a field in a report with other elements like Characteristics and Measures. Variables cannot be used in a When phrase. For information on mandatory variables, see Using Mandatory Variables (SAP BW).
Note: Variables are only applicable for SAP BW data sources.
A Measure can also be a formula where a simple aggregation function, such as sum, can combine several Measure values into one. A formula can also be based on references to a point within a Characteristic.
Characteristics or Dimensions can have multiple organized hierarchies that describe similar sets of members upon which to base an analysis. For example, a characteristic named Customer can have a hierarchy that groups customers according to their geographic locations, as well as another hierarchy that groups them according to their industries.
Variables, Measures, Characteristics or Dimensions, Properties, and Hierarchies are organized in folders that contain the fields you can use in your report. The following image shows these categories and what they contain for a SAP BW and Essbase data source.
The following image shows these categories and what they contain for a Microsoft Analysis Server data source.
When the synonym for the data is created, it is set up as either a parent/child hierarchy or level hierarchy. Hierarchies appear in the Characteristics category. The following image shows the difference between the parent/child and level hierarchy display. Both field lists show the Material class hierarchy expanded in the tree. The list on the left shows a parent/child hierarchy while the list on the right shows a level hierarchy.
The parent/child and level hierarchies contain the same data but are represented differently. For example, in the parent/child hierarchy shown in the previous image you have one field (Member Caption) that contains all the members of the hierarchy. In the level hierarchy, the members of the hierarchy are listed as separate fields.
Note: The parent/child hierarchy also contains virtual (or define) fields (for SAP BW). See Fields in a Parent/Child Hierarchy for details.
By default, the following fields are shown for each hierarchy in the field lists when you select the Dimension view (this is the default view for SAP BW metadata):
These fields show all combinations of Caption and Key that you can use in your report. The last three fields you see in a parent/child hierarchy represent Key, Key-Caption, and Caption-Key. These are virtual fields that are defined during synonym creation for SAP BW.
Name or Key is the technical name and Caption is the user-friendly name (description) for the cube item. Caption cannot be used as a By field unless a field representing either the Name (Member Name) or Member Unique Name is included in the report. The reason for this is since it is possible for more than one item to have the same Caption, if you do not identify the Name or Member Unique Name then there is potential for aggregation of data at different levels. When you include the Name or Member Unique Name, then Caption can be uniquely identified and it can be used as a By field.
The fields listed for a parent/child hierarchy are:
The following table describes the icons that appear in the Object Inspector and in the field lists when you are creating a report using a multi-dimensional data source. The first column shows the icon and the second column provides a description of the icon.
Icon |
Description |
---|---|
Characteristics contains the Properties and Hierarchies folders. | |
Optional variable. | |
Mandatory variable that is not satisfied (selection criteria has not been created). | |
Mandatory variable that is satisfied (selection criteria has been created). | |
Measure. | |
Hierarchy. | |
Attribute. | |
Represents a leaf node in a parent/child hierarchy. A leaf node is a member of a hierarchy that does not have any children. Represents Level 1 in a level hierarchy. | |
Represents Level 2 in a level hierarchy. | |
Represents Level 3 in a level hierarchy. | |
Represents Level 4 in a level hierarchy. | |
Represents Level 5 in a level hierarchy. | |
Represents Level 6 in a level hierarchy. | |
Represents Level 7 in a level hierarchy. | |
|
Represents Level 8 in a level hierarchy. |
Represents Level 9 in a level hierarchy. | |
Represents Level 10 in a level hierarchy. | |
Represents Level 11 in a level hierarchy. | |
Represents Level 12 in a level hierarchy. | |
Represents Level 13 in a level hierarchy. | |
Represents Level 14 in a level hierarchy. | |
Represents Level 15 in a level hierarchy. | |
Represents Level 16 in a level hierarchy. |
WebFOCUS |