Navigation Attribute
Use
Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In this case, a new edge/dimension is added to the InfoCube. During the data selection for the query, the data manager connects the InfoProvider and the master data table (‘join’) in order to fill the Query.
Costs of the cost center drilled down by person responsible:
You use the attribute ‘Cost Center Manager’ for the characteristic ‘Cost Center’. If you want to navigate in the query using the cost center manager, you have to create the attribute ‘Cost Center Manager’ as a navigation attribute, and flag it as a navigation characteristic in the InfoProvider.
When executing the query there is no difference between navigation attributes and the characteristics for an InfoCube. All navigation functions in the OLAP processor are also possible for navigation attributes.
Extensive use of navigation attributes leads to a large number of tables in the connection (‘join’) during selection and can impede the performance of the following actions:
· Deletion and creation of navigation attributes (construction of attribute SID tables)
· Change of time-dependency of navigation attributes (construction of attribute SID tables)
· Loading master data (adjustment of attribute SID tables)
· Call up of input help for a navigation attribute
· Execution of queries
Therefore, only make those attributes into navigation attributes that you really need for reporting.
See also Performance of Navigation Attributes in Queries and Input Help.
See also: