I recently published the post 5 Reasons Why You Should Use an SAP BusinessObjects Universe to highlight some of the core benefits you’ll see when implementing the semantic layer for you organization. The post was derived from speaking with organizations new to the Business Objects world about the benefits of leveraging the semantic layer. Throughout those talks, I also get to hear a lot of misconceptions about SAP BusinessObjects Universes. Sometimes they are born out of a simple lack of understanding of the SAP BusinessObjects architecture, while other times they are propagated by competing business intelligence vendors. (Shocking, I know.)
Finally after three projects and three months later, we are back to finish up our Aggregate Awareness series. In part 1 of our blog, we discussed the definition of aggregates and how to create summary tables. Today we are going to finish the process by showing how to implement these items into a SAP BusinessObjects Universe.
In the SAP BusinessObjects community, when someone talks about “AA” they don’t mean the meetings people attend, they are talking about a pretty cool function that is available in Designer. Aggregate Awareness or @aggregate_aware is a term that we use to describe the ability of a universe to utilize aggregate tables in a database. Using the function correctly can greatly improve the performance and user experience. This will be the first of two blogs and will talk about Aggregation and Summary tables. The second post will show how to implement Aggregate Awareness into a SAP BusinessObjects Universe.