We had a subject area where BI was pulling an attribute column (row wids of dimension) in select clause automatically even though we were pulling only measures in Answers. This was making incorrect aggregates in report or in other word aggregates at lower levels of granularity.
One of the measure columns was a calculated column in RPD where we were multiplying a column from fact to a numeric column in dimension. We had included dimension as one of the sources of fact table and then applied the calculation at logical level of fact table.
To fix this issue, we found that the dimension where numeric column was present had that numeric column in one of the levels of dimensional hierarchy. So when we deleted the numeric column from dimension hierarchy, the query was fine. The numeric column was still present in dimension itself but just removed from hierarchy.
OBIEE Answers, Publisher, Installation, Configuration and work around tips. I record all issues and finding in oracle BI, that I can refer back later, or others can use for troubleshooting. I have extensive experience on OBIEE 10g version previously although currently I am on OBIEE 11g
Thursday, April 9, 2009
Default attribute column in select clause causing incorrect aggregate
Labels:
AGGREGATES,
DIMENSIONAL HIERARCHY,
LEVELS
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment