SAP HANA Modeling complete Notes

in this post, i will cover:

1. Approaching SAP HANA modeling.
2. creating attribute views.
3. creating analytic views.
4. creating calculation views.
5. preparing documents - Auto Documentation.
6. Modeling with information composer.

once we create schemas and tables and load data to SAP HANA,we can start creating different types of views; that is,attribute,analytic,and calculation views according to our requirements.

1.Approaching SAP HANA modeling:

Getting ready: for this, we need SAP HANA studio and SAP HANA client (drivers for SAP HANA) downloaded and installed.these software are available both in 32 bit and 64 bit versions.

there are different types of models,such as attribute views,analytic views,calculation views and so on.

• we create attribute views an top tables.
• in analytic views,we join fact tables to the attribute views.
• Database tables or attribute views, analytic views or calculation views can be included in creating calculation views.
• Apart from these,we can also create store procedures.These procedures can also be used in SQLscript based calculation views.

Basically, data in SAP HANA is organised in the form of tables, in these tables,the respective fields are classified either as an attribute or a measure.

• An attribute in a data -warehouse scenario is called a dimension, and it qualifies something in the data; for example,country code,customer Name,and country.
• A measure is an entity that qualifies something; for example,order quantity,Cost,and sales Amount.

2.creating attribute views:

Attribute Views are similar to dimensions,but the only difference is that attribute views are reusable components as they are object -oriented throughout the information modeling.in simple terms,these are views on one or multiple tables that can be reused for multiple purposes.

For example, the attribute view customers can show Customer code,customer Name,Customer city and other customer master data.This attribute view can be used in both analytic and calculation views based on the relevance.Generally, attribute views represent the dimension data (master data).But technically,there are no limitations or restrictions as it's definitely possible to create attribute views on transactional data.


Authorization Required to create attribute views:

• MODELER role and SELECT authorization on the schema from which we are accessing the tables.
• in addition to this,the _SYS_REPO user must have the EXECUTE authorization with the GRANT option on the schema.

Note: in order to create attribute views, we must have a database table readily available.

We need a package. Packages are folder-like objects into which information views are organized structured.