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.

● Attributes can be defined as key attribute and used when joining multiple tables.<br />

● The Drill Down Enabled property can be used to indicate if an attribute is available for further drill down when<br />

consumed.<br />

● Aggregation type on measures<br />

● Currency and Unit of Measure parameters (you can set the Measure Type property of a measure, and also in<br />

Calculated Column creation dialog, associate a measure with currency and unit of measure)<br />

6.2.5 Creating Analytic Views<br />

Analytic views are typically defined on a fact table that contains transactional data (as measures). Using analytic<br />

views you can create a selection of measures, add attributes and join attribute views.<br />

Analytic views leverage the computing power of <strong>SAP</strong> <strong>HANA</strong> to calculate aggregate data, e. g. the number of sold<br />

cars per country, or the maximum power consumption per day. They are defined on only one fact table, a table<br />

which contains for example, one row per sold car or one row per power meter reading, or some form of business<br />

transaction records. Fact tables can be joined to allow access to more detailed data using a single analytic view as<br />

long as the facts (measures) come from a single table. Analytic views can be defined in a single table, or in joined<br />

tables.<br />

Analytic views can contain two types of columns, attributes and measures, for which measures are of type simple,<br />

calculated, and restricted. Measures are attributes for which an aggregation must be defined. If analytic views are<br />

used in SQL statements then the measures have to be aggregated e. g. using the SQL functions SUM(), MIN(), or MAX(). Normal columns can be handled as regular attributes.<br />

They do not need to be aggregated.<br />

1. Set Parameters<br />

a) In the Modeler perspective, expand the Content node of the required system.<br />

b) Select the package in which you want to save your information object.<br />

c) From the context menu of the package, choose New Analytic View .<br />

Note: Once you have an analytic view in a package, you can also create another one from the<br />

context menu of the Analytic View node in the respective package.<br />

d) Enter a name and description for the view.<br />

e) If you want to create a view based on the existing one, choose Copy From option, and select the required<br />

view.<br />

f) Choose Finish.<br />

The analytic view editor opens. The Scenario panel of the editor consist of the following three nodes:<br />

○ Data Foundation - represents the tables used for defining the fact table of the view.<br />

○ Logical Join - represents the relationship between the selected table fields (fact table) and attribute views<br />

that is, used to create the star schema.<br />

○ Semantics - represents the output structure of the view.<br />

In the Details panel you define the relationship between data sources and output elements.<br />

2. Define Output Structure<br />

110<br />

a) Add the tables that you want to use in any of the following ways:<br />

○ Drag the required tables present in the Catalog to the Data Foundation node.<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!