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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

○ Name Path - the unique node ID is composed of the result node name and the names of all<br />

ancestors apart from the (single physical) root node. For example "[A1].[B2]".<br />

9. Add the required attributes from the drop-down list.<br />

Note: You can select attributes from the required table columns in the drop-down list to add to the<br />

view.<br />

10. Select the required Level Type.<br />

11. Choose OK.<br />

Note: The level type is used to specify formatting instructions for the level attributes.<br />

For example, a level of the type LEVEL_TYPE_TIME_MONTHS can indicate that the attributes of the<br />

level should have a text format such as "January", and LEVEL_TYPE_REGULAR indicates that a level<br />

does not require any special formatting.<br />

Creating a Parent/Child 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, choose Parent Child 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 to have one for reporting use case, set the<br />

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

8. Select the Parent Node and Child Node from the dropdown list.<br />

9. Choose OK.<br />

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

Setting Up the Analytic Model<br />

P U B L I C<br />

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

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

Saved successfully!

Ooh no, something went wrong!