Showing posts with label hana-modeling. Show all posts
Showing posts with label hana-modeling. Show all posts

Friday, 5 August 2016

Generate Time Data in SAP HANA - Part 1

In this document, I tried to explain "Generate Time Data" functionality. Through this, I am trying  to provide the general functionality and idea about the "Generate Time Data" with calender type "Gregorian".
In order to better understand how to use “Generate Time Data”, we are going to use standard table for the examples.

Note: While using this option you need to replicate the standard table into SAP HANA that is T005T, T005U, T009, and T009B. If these standard tables are not available then you will not be able use the “Generate Time Data” function.

Monday, 1 August 2016

Table Valued - UDFs Vs Scripted Calculation Views - Rudimentary Exploration

'Use table functions instead of scripted calculation views (SP09)'

This sounded like, the coveted scripted calculation views, which were a part & parcel of any real-time customer implementation were facing an extinction threat! To fathom what that means, warranted some investigation and here's my attempt to get the basics in place w.r.t
User-defined Table-valued Functions (a.k.a TV-UDFs).

Wednesday, 8 June 2016

How to Migrate Attribute, Analytical & SQL script based Calculation views

As mentioned in the document SAP HANA Features that are Deprecated the Attribute views, Analytical views and SQL Script based Calculation views are now deprecated. SAP discourages from using them in new projects and suggests that you migrate them into the appropriate recommended alternatives mentioned in this blog.

This document aims to provide you with the steps to Migrate the earlier created views.
1.1 To launch the Migration tool you need to go to the Console View by accessing Windows -> Show View -> Quick View

Tuesday, 3 May 2016

Table Transpose in SAP HANA Modeling

Approach 1:
  • Analytic view will be built on each base table column which needs transposition.
  • In this case 6 columns need transposition, hence 6 Analytic views will be created.
  • Calculated Column (VALUE) is created in each Analytic view which derives the value of a particular month in a year.
  • Create Calculation View based on Analytic Views created above and join them together using Union with Constant Value.
  • No need to create Calculated Column (MONTH) in each Analytic view as this can be derived in Calculation View to improve performance.

Saturday, 30 April 2016

SAP HANA Modeling - Project Learnings and Tips

Key benefits of Data Modeling in SAP HANA:
  • Building analytics and data mart solutions using SAP HANA enterprise data modeling offers various benefits, compared to the traditional data warehousing solutions such as SAP BW.
  • Virtual data models with on the fly calculation of results, which enables reporting accuracy and requires very limited data storage – powered by the in-memory processing, columnar storage and parallel processing etc.
  • Ability to perform highly processing intensive calculations efficiently – For example identify the customers where the sales revenue is greater than the average sales revenue per customer
  • Real time reporting leveraging the data replication and access techniques such as SLT, Smart data access etc.
Apart from the HANA sidecar or data mart solutions, HANA modeling also plays an essential role in the BW on HANA mixed scenarios, S/4 HANA Analytics, Predictive Analytics and Native HANA applications etc.

Saturday, 19 March 2016

Input Parameter with Key and Text in view help ( F4)

This blog would explain how we can use both Key and Text in  view help ( f4 values) of  HANA Calculation View

***Now this functionality has been added to SPS10, if you are at SPS10 or above, you no longer need this work around ***

Scenario :

Users want to filter data by Customer and see Customer Text in view help along with number . As the table has billions of rows, to improve report performance , we want to use Input Parameter in Projection Filter .  Available types of Input Parameter in SPS9 cannot use Key and Text both directly in View Help or F4 values.

Our Data Model is Calculation View .  Input Parameter behaves differently in Calculation View and Analytic View.