Please see below for the information on Navigation Attributes:
If there are levels on which the data is only displayed and no planning is performed, it is possible to model these levels as navigation attributes instead of characteristics. The planning is not possible because navigation attributes cannot be assigned to the forecast profile.
Navigation attributes have a reference to a characteristic, but are not part of the key for the data access.
The advantage of the navigation attributes is that their values can be changed very easily without the necessity to realign any data. They are therefore very well suited to represent entities with more frequently changing values, for example the assignment of a planner to a product. It is very easy to realign the planning objects since only the master record table of the affected InfoObject has to be changed.
Until only a handful of attributes are used, no performance restrictions are expected.
Note that for the standard characteristics 9ALOCNO and 9AMATNR it is not allowed to use navigation attributes.
The use of navigation attributes adversely affects performance during data selection and during navigation in the interactive planning. The number of used navigation attributes is important and not the different specifications of a navigation attribute.
Navigation attributes can not be used as a characteristic during the definition of a fixed aggregate.
Hope this helps,
Uthira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.