Which Schema used

  1. Look at the universe structure and see if you have central fact tables with dimension tables surrounding the fact-tables, keyword: dimensional modeling, R. Kimball

  2. No, @aggregate_aware is not necessary per se in a universe. @aggregate_aware allows you to transparently switch between tables, for example between a detail fact table (w/ each single bank transaction e.g.) and a summary table (bank transactions aggregated at a monthly level). This is typically done for performance reasons. The summary table must be created at the database level though.
    One must define aggregate navigation whenever using @aggregate_aware!
    I would recommend using query rewrite option in Oracle instead (other DBMS have similar functionality), this is totally transparent to BusinessObjects and does not require the use of @aggregate_aware at all. The switching to summary tables is handled completely by the DBMS (Database Management System).

Note:
All measures should use a SQL aggregate function (such as SUM, COUNT, etc.) in addition to setting the correct projection, see also here.

Otherwise, I kindly suggest to attend an official training class, topic: Designer.


Andreas :de: (BOB member since 2002-06-20)