Developing custom OLAP cube aggregations


Business problem: By default, OLAP cubes calculate aggregations at each possible intersection of levels in one or more dimensions. However, there are situations where aggregations cannot be completed on the fly for all intersections within the cube due to business rules for some data levels. Also, the source data table isn't a fully summarized table (which fits nicely into the OLAP Studio GUIs) and derived measures are not possible due to specific business rules.

Solution: Within the PROC OLAP code, you can specifically assign an individual table for each Aggregation. This option is defined in the online help at:
It is important to note that the individual aggregated tables must have columns that completely match those listed in the aggregation step & this table must have at least one column defined in the MEASURE AGGR_COLUMN= statement.

Contributed by:J. Alan Stark of Ashlind Consulting


About Author

Angela Hall

Senior Technical Architect

Angela offers tips on using the SAS Business Intelligence solutions. She manages a team of SAS Fraud Framework implementers within the SAS Solutions On-Demand organization. Angela also has co-written two books, 'Building BI using SAS, Content Development Examples' & 'The 50 Keys to Learning SAS Stored Processes'.

Leave A Reply

Back to Top