Skip to Content
avatar image
Former Member

Navigation Attributes & Planning Characteristics


We plan to maintain some of the characteristics as Navigation Attributes. We understand that there are performance issues if we use navigation attributes in planning area.

I have a query: If we do not navigate data based on navigation attribute in interactive planning, even then the performance be low or only when we select navigation attribute in interactive planning?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 30, 2013 at 03:59 PM

    By definition, nothing is stored in live cache against navigation attributes. So if you load a selection containing navigational attribute or drill down by navigational attribute, in theory this should be much faster vis a vis reading from live cache (not withstanding the general computing theory of memory resident processing). This statement (of mine) is contra positive to SAP warnings on performance when using navigational attributes. There are a dozen notes on this to scare users.

    There is no definitive answer I guess... at least empirically. It depends eventually on the query size. When query is large, it is hard to blame navigational attributes alone (if you are using some). It can be more so because of transaction time (SQL>LC routine > SQL) in the live cache as well. Sometimes reading a simple relational table (if indexed) can be much faster than reading non-relational (live cache) tables.

    I am not a techspert and authority on this. This response is based on my painful experiences. For me anything more than couple of seconds on interactive DP is a waste of time.



    Add comment
    10|10000 characters needed characters exceeded