Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Doug Berry on Dec 23 at 6:00 PM Not true,
When BEx query performance begins to suffer due to too many NavAtts then you can remodel the InfoProvider, compress data, rollup and so forth.
There is no hard stop on having only 4 NavAttributes.
And of course, now we have HANA so an InfoCube isn't even needed.
| | | ---------------Original Message---------------
From: SimonCrowder
Sent: Monday, December 23, 2013 11:08 AM
Subject: Limit Number of NavAttrs
I am aware of the performance impact of using NavAtts when running a query (additional joins etc), but someone mentioned to me that Best Practice is to restrict the number of Navigational Attributes within an Inforcube (or Query) to 4.
Now I can't see any documentation which states this, so I can't confirm this is the case, but has anyone else seen/heard this as a recommendation??? The guy who mentioned this to me is adamant but can't remember where he was told this.
We do use NavAtts within Queries so the users always have reports against the LATEST Master Data, and can actually run queries comparing Data against Latest Master Data and the Master Data as the data is loaded (stored as Characteristics).
I would easily maybe have 5-10 available NavAtts within a InfoCube/Query (e.g. 5 for Material, 5 for Customer) but probably not all used by users at the same time, but would be Free Characteristics.
Cheers
Simon |
| Reply to this email to post your response. __.____._ |   _.____.__ |
