Proposals from BW Statistics 
Proposals from BW Statistics
Use
If you have activated the collection option for OLAP statistical data, every navigational step that requests data from the database, is saved. This includes what characteristics, navigation attributes and hierarchies were involved. This statistical data is saved in database tables at first. You can then load this data into the BW statistics InfoCube for evaluation.
You can also use this data for optimizing aggregates. The advantage of having proposals from BW statistics as opposed to proposals from queries, is that the actual user capacity is taken into account here.
Use this function if there is already representative statistical data. Also, use the function at regular intervals to adjust the aggregates against the changes in user actions.
You can evaluate the saved data over the menu path Proposal ® Proposal from BW Statistics (tables) or Proposal from BW Statistics (InfoCube). You can restrict the analysis to a sub-quantity of the data, where an interval for the start-time or the run-time of the query is specified.
After the data has been read from BW statistics, the current ideal aggregate is determined for every navigation step, and a list of the different aggregates is made.
For aggregates that vary in one component only on the aggregation level, all those with an aggregation level hierarchy (‘H’), or fixed value (‘F’), are replaced with an aggregate (‘*’) grouped according to characteristic values, as long as this has already been proposed.
The list of proposed aggregates has the same structure as the
Proposal from Queries. However, the list is generally longer.You can modify or delete the proposed aggregates.
See also:
Optimizing Proposed Aggregates