28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

For example: an address hierarchy comprised of region, country, state, and so on.<br />

● Parent/Child Hierarchy<br />

A parent/child hierarchy is a hierarchy in a standard view that contains a parent attribute. A parent attribute<br />

describes a self-referencing relationship, or self-join, within the main table. Parent-child hierarchies are<br />

constructed from a single parent attribute.<br />

For example: a bill of materials hierarchy (parent and child) or an employee master (employee and manager)<br />

hierarchy.<br />

Procedure<br />

Creating a Level Hierarchy<br />

1. Select the Semantics node.<br />

2. In the Hierarchies panel, choose Create option .<br />

3. Enter a name and description for the hierarchy.<br />

4. In the Hierarchy Type dropdown, select Level Hierarchy.<br />

5. Select the required value in the Aggregate All Nodes.<br />

Note: This option indicates that data is posted on aggregate nodes and should be shown in the user<br />

interface. For example, if you have the members A with value 100, A1 with value 10, and A2 with value<br />

20 where A1 and A2 are children of A. By default the value is set to false, and you will see a value of 30<br />

for A.<br />

With the value set to true, you will count the posted value 100 for A as well and see a result of 130.<br />

If you are sure that there is no data posted on aggregate nodes you should set the option to false. The<br />

engine will then calculate the hierarchy faster as when the option is set.<br />

Note that this flag is only interpreted by the <strong>SAP</strong> <strong>HANA</strong> MDX engine. In the BW OLAP engine the node<br />

values are always counted.<br />

6. Enter a value for the default member.<br />

7. Select the required option in the With Root Node dropdown.<br />

Note: If a hierarchy doesn't have a root node but needs one for reporting use case, set the option to<br />

true. This will create a root node.<br />

8. Select the required value from the Node Style dropdown list.<br />

128<br />

Note: Node style determines the composition of a unique node ID. The different values for node styles<br />

are as:<br />

○ Level Name - the unique node ID is composed of level name and node name, for example "[Level<br />

2].[B2]".<br />

○ Name Only - the unique node ID is composed of level name, for example "B2".<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Setting Up the Analytic Model

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!