Skip to Content
author's profile photo Former Member
Former Member

HANA Live - Attribute Views??

Hello Experts,

We recently installed HANA Live content, virtual data models, HANA live browser (all the good things) and started replication with SLT in side-by-side scenario with Enterprise edition.

I was surprised to see, there are no attribute views which came as part of virtual data models. Everything is a calculation view and seems to have number of joins (at times 10+) for simpler data models.

I'm wondering why SAP didn't deliver not a single "attribute view" and has modelled everything in calculation view.

Even to get some of the basic master data, we need to do enhancement and could be a pain.

Any insight?



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Posted on Oct 03, 2013 at 04:43 PM

    Hi Abhijeet,

    I do not have any experience on HANA Live. But from the perspective of modeling, I can say that even the current modeling from SAP regarding BW objects to HANA generate Analytic views (for DSOs) and Calc views (for InfoCubes).

    Attribute views are good from the perspective of maintenance and development standards / reusability, but from the performance perspective, when the attribute views are used in Analytic views and Calc views, they are resolved to table joins. Hence it doesn't matter if the HANA views use Attribute views or tables in the view definitions.

    Regarding the joins, I think not all the joins will be executed when you fire a query against the model. You may see that yourself in the visual plan.

    Well, I am sure you will get more technical reasoning behind this modeling from SAP itself, I just put in my two cents..



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 03, 2013 at 05:16 PM


    Did you review HANA live docs model documentatioin @ . Which module (CRM / Core ECC , etc..) of HANA live are you implementing? Since General Availability was only last month, you might want to get latest documentation links via OSS customer message or your internal SAP account manager.

    Hope this helps.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 09, 2014 at 10:55 AM

    Great thread guys. I am wondering though why SAP does not come back with an answer on the question which is raised a couple of times:

    Why are Hana Live views build exclusivley in graphical calculation views.

    I'm guessing there is no answer to the question?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I took a look at this specific view. It has 5 projections, 9 joins, 1 union and 2 different aggregations, so I wouldn't say it's very simple. Obviously SAP intended this to be used over a number of Sales Orders, not just a single or handful chosen via input parameter, and obviously it doesn't scale.

      Also of note - these are all set to execute in the SQL Engine, I wonder if switching to blank (so that it executes in the Calc engine) has any effect. Why don't you try this out?

      Otherwise, I would think about implementing the functionality you need in an Analytic View if you can pull it off.



  • Posted on Nov 06, 2013 at 01:06 PM

    I did not read all postings:

    However, back to the original question: Hana Live views are build exclusivley in graphical calculation views, even scripted views are exceptions, analytical and attribute views are not allowed.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks everyone for great discussion.

      Now having used HANA live for couple of months and several enhancements, I find it extremely annoying to have everything as calculation view especially from classic BW master data perspective.

      1. Modeling texts and master data both gets too complicated. With classic BW, we can add attributes and they show up easily on all queries. In HANA live, we if add any attributes, we need to specifically promote them to individual views and that doesn't seem very "re-usable".
      2. In some projections and aggregations, we completely lose ECC fields tech names. So in lower level views (COM structures - e.g. VBAK_COM), we may have fields with tech names, but in higher level we lose the tech names. Managing everything with just descriptions is highly inefficient.
  • author's profile photo Former Member
    Former Member
    Posted on Mar 17, 2014 at 07:21 PM

    for some reason, after launching the view for two days the results now got better, to around 2 seconds for 1000 rows. I increased the entries number to 10000 and it's taking 7 seconds. Still not really good for an In-Memory.

    I checked the other HANA Live views and they give me roughly the same numbers...

    I switched from SQL Engine to BLANC, but the result is still the same.

    Add a comment
    10|10000 characters needed characters exceeded

    • Ok, cheeky answer, but aggr/s/core is not a response time.

      It's a very low level performance characteristic that is only partly relevant for information models.

      For complex information models data is aggregated, projected and transformed multiple times in a stacked fashion. Stacked means that some of the processing needs to wait for earlier steps to be finished leading to staged processing scheme. In short: you won't get all cores to work in parallel in all processing steps.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.