To fix this, go to the semantics node and under the “View Properties” tab, switch the data category to DIMENSION as shown below.īefore we do a data preview on the entire view, let’s data preview the output of the first Projection node. This is due to the fact that the data category chosen while creating this view was CUBE and now it has no measure since we have taken SCORE field out of the output. This error says that “No measure defined in a reporting enabled view”. It may throw the below error if you have been following the same steps I’ve been doing.
![sap hana studio nvarchar non standard characters sap hana studio nvarchar non standard characters](https://www.todaysoftmag.com/images/articles/tsm53/ss15.png)
![sap hana studio nvarchar non standard characters sap hana studio nvarchar non standard characters](https://html.pdfcookie.com/02/2019/12/24/g27o0qxxg0v0/bg14.jpg)
In the aggregation node also, let’s select this field as shown below. For example, from Projection_1 let’s disable all fields except EMP_ID. When two rows in the incoming data set contain the same data, the aggregation node also works as a duplicate row remover. The aggregation node also helps remove duplicates. Measures aren’t the only fields capable of getting aggregated. Since SCORE was an INTEGER datatype field, no decimals were retained in the output. As seen below, an average value has been displayed in the output. Let’s set this value to Avg (Average) as per our requirement. VAR and STDDEV are Variance and Standard deviations for advanced statistical analysis in rare cases. The common ones are COUNT, MIN, MAX, AVG which are used to find the count, minimum value, maximum value and average values of measures respectively. All the available values for aggregation types are as shown below. Let’s channel our curiosity and try to switch this setting so that we get the average of all available SCORE values for each employee. Thus, whenever values aggregate, they add up according to this default setting. This is by default set on to SUM as explained earlier. At the far bottom, you find an Aggregation setting. At the bottom, now the properties section opens up. Let’s look at the different types of aggregations.Ĭlick on the aggregation node and then clock on the SCORE measure. But there are other types of aggregations that can also be performed. This is because the default aggregation setting is SUM. Press “Yes”.Īs seen below, since the date field was removed the score gets aggregated and summed up. Click on the orange circle as always to remove the DATE field as shown below.Ĭonfirm the removal of this field. Now, come back to the Aggregation view and click it. This is just to see the data we will be working with. Let’s first check the data preview for this simple view. It takes all the data from EMP_SCORE_FINANCE table and sends it to the output without any additional logic. Let’s start with a basic view that is already built. Additional aggregation nodes can be added if required. An aggregation node is usually attached to the semantics node by default if you are building a transaction calculation view(This means that the data category CUBE was selected when initially creating the view). Welcome again good folks to the next SAP HANA tutorial where we learn about the humble Aggregation node in SAP HANA.
![sap hana studio nvarchar non standard characters sap hana studio nvarchar non standard characters](https://docplayer.net/docs-images/71/64395125/images/243-0.jpg)
Aggregation node in SAP HANA Calculation View