Navigational Attribute Vs Characteristic in a Dimension

[Former Member]

Hi All-

I have a basic question in the info Object Modeling. What is the difference between using info object as a navigational attribute to the other characteristic Vs. Info Object using in a dimension?

Thanks

Naga

[Former Member · Accepted solution]

In the backend, the relationship between tables are totally different.

For Dimension Characteristics, DIM table links all SID table directly and In Navigation Attribute, the navigation attribute is link to Char's SID table not Dimension table.

Because Navigation attribute are placed one level farther away from the fact table, query performance will be poor with this design. And you can not build Aggregate on Navigation attribute too

Usually, the decision for dimension characteristics or navigational attributes is based on business requirements rather than on performance considerations.

Try this one if you are really interesting in the inpact of different design to the business

http://help.sap.com/bp_biv270/documentation/Multi-dimensional_modeling_EN.doc

[former_member187400]

Dear Naga,

Well ..

Actually, it relates to star schema concept in the BI.

In the star schema, we can see dimension containing all attributes.

e.g. customer dimension: it contains e.g. address, zip code, etc.

In the BW, we can use master data in dimesion, so the information like address, zip code, etc can be categorized in one master data (e.g. customer master data).

Address, zip code can be classified as navigation attribute, so we can use it / navigate it in the report.

That for navigation attribute.

But for ordinary info object put in dimesion, we can use it like usuall.

We can summary:

Navigational attribute is the attribute in some master data that we're gonna use in the report.

Info object in dimesion, is the info object/information that's used in report.

For the detail, i have the good reference:

http://help.sap.com/bp_biv270/documentation/Multi-dimensional_modeling_EN.doc

Hopefully it can help you a lot.

Regards,

Niel.

[Former Member]

Hi Niel-

Thanks that helps. To understand better could you please elaborate with some good example.

Thanks

Naga

[Former Member]

Hi Naga,

Navigational attributes creates a performance issues due to more no of table joins. where are characteristic in cube not.

Ex: For any attribute we need if from master data then navigational attribute has to be used. Where as if we need data from transactional data then we need to add into infoprovider.

Please check these docs:

[Navigation Attribute|http://help.sap.com/saphelp_nw70/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/frameset.htm]

[Multi-Dimensional Modeling with BI|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84]

[Extended Star Schema|http://sapbwneelam.blogspot.com/2007/10/extended-star-schema.html]

Hope it Helps

Srini

[Dont forget to close the call by assigning poings.... - Food for Points: Make a Difference through Community Contribution!|https://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/007928c5-c4ef-2a10-d9a3-8109ae621a82]

[former_member187400]

Hi Naga,,

Tks a lot for ur appreciation ..

Well , actually for the example.. you can see in document given to u.

In over there, u r given example regarding relationship for sales person, customer, and material.

Hopefully it can help you a lot.

Regards,

Niel.

[Former Member]

Thank You All