Blogs

SAP HANA views organised in layers

17 augustus 2018

Getting structure in the new HANA environment is not as easy as it first seemed. It all started easy, just one model to combine some ADSO generated views and use it in Analysis for Office. But after these scenario’s some new requirements popped-up: the simple views needed an update and became more and more complex. Some logic from the ADSO was removed and put into HANA views, meaning that the previously used generated views had to be remapped. That got us thinking… We needed a more efficient way to avoid this in the future.

Every layer connects to the layer underneath with the use of a contract layer. This takes care of the mapping between two layers. A view in one layer does not care what happens in the other layer (and should NOT be used in another layer), the only thing they need to respect is “the contract” in between. A model can change to whatever is necessary as long as it respects the contract. In doing so everybody using the contract knows that anything being build on top of it will work after updates or changes down the line.

Analytic layer

Objective: Reporting layer, exposed views for the reporting tools.
Concept:

  • Business-reporting logic
  • Data Category: Cube
  • Small calculations
  • Replacement of BEx
  • Generic name, understandable for business users

Output layer

Objective: Contract between Analytic and Model.
Concept:

  • Contract layer
  • No logic, calculations, joins…
  • Data category: [blank]
  • Generic name, understandable for business users
  • Proper naming of fields
  • Translations

Model layer

Objective: Development layer: create / combine / apply company logic.
Concept:

  • Data category: [blank]
  • Building blocks
  • Apply logic and calculations
  • Create complete BI solutions

 

Input layer

Objective: Decouple the data from the system.
Concept:

  • Contract layer
  • No logic, calculations, joins…
  • Data category: [blank]
  • Generic name, explaining what data is inside
  • Remapping from SAP to Hadoop possible without breaking logic above

Raw data layer

Objective: Data from every source possible.
Concept:

  • Generated HANA views from SAP
  • SQL tables
  • Hadoop tables
  • Smart Data Access
  • Blogs

    so.. SAP Lumira is dead.. now What ?

    As a consultant I’m responsible for the Analytics environment for an Innovative Company in Natural Chemistry and innovative in their IT. Recently I was forced to ponder on the post-Lumira question “ Now what ? ”.

     

    Read more >
  • Blogs

    Fetching XML API data

    Fetching XML API data

    I recently finished a project for which I had to fetch public data of parking lots and load it to a multiprovider to use it in reporting.  The data that I needed to fetch was from an open data API. After successfully finishing this project I thought I would share how I did this as an easy guide for others.

    Read more >
  • Blogs

    Take on the fight with Python

    Take on the fight with Python

    Introduction

    If there is one thing common in everyone’s career than it is that at some point everyone said: “Can’t this be automated or made simple?”. On a given moment at my customer I was asked to do a data-compare of two data providers with over 50 characteristics each and containing millions of records in SAP HANA. At first I started to run queries against the SAP HANA-tables to check the data but soon enough I thought…

    Read more >