Aggregate Aware Objects & Conditions

building semantic layer
1

I have run into a problem using the aggregate aware feature in BusinessObjects. We are at 4.1.2. I have created several aggregate aware objects and also set up the incompatible objects. When choosing the objects everything works as expected choosing either the summary or the detail table as needed. Where my problem comes in is with the predefined conditions I have set up that are based on those objects. The predefined condition references the aggregate aware object using the @select syntax. The predefined condition works properly if I have the aggregate aware object that it references in the query also. If it is not in the query I get an SQL sentance error. When I look at the SQL, the @aggregate_aware syntx is in the sql instead of the table and column name. Wondering if anybody else has this problem and/or if they have a solution?

Glenn Fredericks
Data Warehouse Specialist
glenn_fredericks@aal.org
(920) 730-4700 x4236 or 1-800 CALL AAL

Aid Association for Lutherans
4321 N. Ballard Road
Appleton, WI 54919-0001
Visit our Web site at www.aal.org or e-mail us at aalmail@aal.org

AAL… Financial services. Lutheran heritage. A powerful combination.

Listserv Archives (BOB member since 2002-06-25)

2

Glenn,

I’m not sure you can use aggregate aware objects as an argument for @Select. I once tried to use @Select(AggregateAwareObject) in the SELECT part of an object, and I think “Parse…” whined something about this being illegal.

Maybe BO programmers forgot to check the same thing for the syntax of WHERE clause…

-Harri

Listserv Archives (BOB member since 2002-06-25)

3

Glen,

From my experience (up to BO 4.1.0) it is not possible to use the
aggregate aware function AT ALL in the WHERE part of the query. It simply doesn’t get translated and SQL doesn’t understand it off course.
From the white papers you can read between the lines that the function
was invented for measure object (like revenue coming from different aggregations). Probably that is why the WHERE part got left out.

However I would appreciate it if BO got it to work for the WHERE part as well.

Greetings,
Marianne Wagt
IDETA
The Netherlands

Listserv Archives (BOB member since 2002-06-25)