February 2, 2012

Why Navigational attribute work as characteristic in Reporting and Modelling in SAP BI


We all know that Fact table is surrounded by dimension table and master data in connected to dimension tables using SID's.

So any master data object which has SID can act as characteristic in reporting or in Cube.

If you add an attribute to any characteristics, we know what are all the tables will generate.

Display time independent -- P Table

Display time depended -- Q Table

Navigational time independent -- X Table

Navigational time dependent --- Y table.

If you check P and Q table in BI system, it will not contain SID values. But if you check X and Y values, it will contain SID values for this characteristic and we will have SID values of main characteristic(to which this is navigational attribute).

The following figure illustrates the relationship between X table and the SID table of navigational attribute

Let’s take we have defined LOCATION as navigational attribute for 0CUSTOMER.





As navigational attributes contains SID values, it will act as characteristics in reporting and Cube.

you can refer the below document for characteristic tables structure.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10db929a-7abb-2e10-6fa5-d8d45ca028ed?QuickLink=index&overridelayout=true

Hope it helps..
Posted by at
Labels: , ,

5 comments:

  1. ravichandraMarch 28, 2012 at 11:21 PM

    Hi venky,

    I have a query, Now will the SID table(location ) is connected to the dimension table or to any other table . Plz can u explain a little bit more about this.

    Thanx & Regards,
    RaviChandra Tanka

    ReplyDelete
  2. UnknownMarch 29, 2012 at 10:06 PM

    Hi Ravi,

    Navigational Attributes are not part of Dimension tables. There will no joining to the SID table of location.

    No DIM ID's for Navigational Attributes.

    Regards,
    Venkatesh

    ReplyDelete
  3. ravichandraApril 20, 2012 at 11:55 PM

    Hi venky,

    I have a doubt regarding the length of the characters in one of the fields in the source system , here the length is 240 characters long and now i would like to divide this field into 4 IO and then would like to merge this 4 IO into the single IO at the BEx query level .
    How to achieve that.

    Plz reply..
    I know that this questions doesn't match the above requirement .
    Plz reply,
    Thanx & Regards,
    RaviChandra

    ReplyDelete
  4. NaniJuly 19, 2012 at 6:42 PM

    hi venky,

    i think there will be seperate dim table for nav.attr.(guessing)

    Anyways,here my doubt is i heard that one option is there to select the nav.attr while we create the multiprovider.

    Can u plz guide whr will be the option..

    Thanks in advance
    Nani

    ReplyDelete
  5. UnknownAugust 11, 2012 at 4:31 PM

    Hi Beverly,

    Thanks for visiting my blog. I have created website www.sapanalyticsguru.com

    I am in process to migrate all the data in this blog to new website and I will be posting new articles in website instead of this blog.

    Please visit my new website www.sapanalyticsguru.com

    Regards,
    Venkat

    ReplyDelete

Subscribe to: Post Comments (Atom)