SAP HANA: Interview Questions 131 through 140

131. Explain the process flow for modeling within SAP HANA?
On a high level, the process flow for modeling with SAP HANA works like this:

  • Import Source System metadata
    • Physical tables are created dynamically
    • 1:1 schema definition of source system tables
  • Provision Data
    • Physical tables are loaded with content
  • Create Infomation Models
    • Database Views are created
      • Attribute Views - Separate Master Data from Fact Data
        • Build the required master data objects as Attribute views
        • Join text tables to master data tables
        • If required, join master data tables to each other
          • Example, join Plant to Material 


      • Analytic Views - Create Cube-like view by joining attributes view to Fact data
        • Build a Data Foundation based on transactional tables
          • Select Measures (key figures)
          • Select attributes IDs (docking points for joining attributes views)
        • Join attribute views to data foundation
          • The Analytic View is a kind of star schema
      • Calculation Views - If joins are not sufficient, Create a Calculation View that is something that looks like a View and has SQLScript inside
        • Composite view of other views (tables, re-use join, OLAP views)
        • Consists of a graphical and script-based editor
        • SQLScript is an HANA-specific functional script language
          • Think of a 'SELECT FROM HANA' as a data flow
          • JOIN or UNION two or more data flow
          • Invoke other functions (built-in CE or generic SQL)
      • Analytic Privileges
        • Used for row-level security
        • Can be based on attributes in analytic views
        • Can specify values for a particular role 


  • Deploy
    • column views are created and activated
  • Consume
    • consume with client tools - BICS, SQL, MDX
132. Explain the main steps to create an Attribute view?
Attribute View

  • Attributed add context to data
  • Can be regarded as Master Data tables
  • Can be linked to fact tables in Analytic views 
Steps:

  • Set Parameters
    • Enter a unique name (technical name) and description
      • The allow characters are: capital letters (A-Z), numbers(0-9), and Underscore(_).
      • There is no multi-language support for Description metadata
    • Select View Type
      • Attribute View
    • Select Subtype
      • Standard
      • Time - a time view created a master data view for time characteristics (calendar year, quarter, month, week, day, fiscal year/period, etc)
      • Derived (Read-only) - is a linked copy that allows usage of two Attribute views with exactly the same definition in the same Analytic or Calculation view.
        • An Attribute View cannot be used more than once in another view. If needed, you can create one or several Derived Attribute Views.


      • Copy From feature can be used to create a new Attribute view (independent) from an existing Attribute view (as a template). 


  • Table Selection
  • Table joins and properties
  • Select Attributes
  • Create Hierarchies
  • Save and Activate
  • Data Preview