Default aggregation

Hi all,
Is it possible to have "multiply" as the default aggregation for a measure in OBIEE 11g? Any workaround solution if this is not supported? Thanks.
Regards,
Gerd

If you didnt set content tab that would be default aggregation, means based on the columns pull in the criteria SUM changes like drill down or roll up.
'Group by' clause keep on changes as per the column in the criteria.
When you set any level for a metric then it alway aggregated to that level, values will not change as per column selection.
Pls mark if helps
Edited by: Srini VEERAVALLI on Nov 1, 2012 4:48 AM
Any updates on this?
Edited by: Srini VEERAVALLI on Jan 7, 2013 1:56 PM

Similar Messages

Default Aggregation Rule

Can someone explain me as to how BI interprets the default aggregation rule.
Say when we say the defualt aggregation rule on the sales fact table column revenue is SUM. what does it actually imply.
Similarly when we use the Aggregation Content tab in the Logical table source and set aggregation content group by what does it actually mean.
Thanks,
Chan

If you didnt set content tab that would be default aggregation, means based on the columns pull in the criteria SUM changes like drill down or roll up.
'Group by' clause keep on changes as per the column in the criteria.
When you set any level for a metric then it alway aggregated to that level, values will not change as per column selection.
Pls mark if helps
Edited by: Srini VEERAVALLI on Nov 1, 2012 4:48 AM
Any updates on this?
Edited by: Srini VEERAVALLI on Jan 7, 2013 1:56 PM

What is Default Aggregation in Web Intelligence ?

In WebI, when I click on the Sigma (Sum) icon, the last option is "Default aggregation". What are the uses of this function?Also, what is the difference between Sum and Default Aggregation?

I am using BEx.
My problem is col1 is showing 85.5 in BEx.
In Webi, when i select "Sum" it is showing 13.5, but when i select "Default Aggregation" it is showing 85.5
When is checked "Duplicate Row Aggregation" there are only 8 records in col1 which sum upto 13.5. I dont know how 85.5 is arrived while using "Default Aggregation" ?

Customizing default aggregation

I have a cube (based on G/L Balances) which has 9 flex field segments, time, currency and set of books. These segments have altogether approx 25 hierarchies. My issue is, using AWM how does one specify PRECOMPUTE(NA) for some of these dimensions in an aggregation plan? All of these hierarchies a value based. I know how to do this by editing an AGGMAP, but I am having trouble figuring out how something like this should be implemented. Perhaps I shouldn't be using AWM at all? Then what?
Any thoughts and ideas would be helpful.

You should be able to do it with the Oracle OLAP Analytic Workspace Java API (AWXML). The default Model View in AWM uses this API. For more details, please refer to the reference guide on OTN:
http://www.oracle.com/technology/products/bi/olap/index.html

Default aggregation on Items

In Discoverer 9i Plus, I do not see the COUNT, MAX, and
MIN aggregations on an axis item unless I have defined
an Item Class and a List of Values for the item.
This is different from 9i Desktop, where I see those same
aggregations on axis items whether or not there is an
LOV.
Is this another one of the differences between Plus and
Desktop?
Is there some way in the Admin Edition for me to make
COUNT, MAX, and MIN visible on axis items all the time?
--- Steve

hi scott,
one thing you could do is using the content management APIs and update the affected items in bulk. e.g. change their display name so that the file extension is included in the name.
Portal Developer's guide - Part III
http://download.oracle.com/docs/cd/B14099_18/portal.1014/b14135/toc.htm
hope this helps.
regards,
christian

Member Formula: IF ... ELSE do outline aggregation

Hi experts,
How to write a formula for a parent entity member like this:
IF (@ISMBR("Account member"))
do something
ELSE
do default outline aggregation from its descendants
ENDIF
Because I just want the "Do something" execute for some account member. If there is not ELSE statement, the formula will override default outline aggregation. The problem is I can not find any function that manually do default aggregation.
Please ask if my question not clear.
Many thanks!

Huy Van
I tried to replicate it in Sample Basic, I loaded sample data and below is the result
     Cola     Actual
     East     East     East     East     New York     New York     New York     New York
     Sales     Margin     Profit     Measures     Sales     Margin     Profit     Measures
Jan     1812     1213     837     837     678     407     262     262I've a script where I've fixed on East (Parent member of Market)
FIX(East,Actual,"100-10")
Jan(
IF(@ISMBR(Sales))
100;
ENDIF)
ENDFIXBelow are the results after running the script
     Cola     Actual
     East     East     East     East     New York     New York     New York     New York
     Sales     Margin     Profit     Measures     Sales     Margin     Profit     Measures
Jan     100     -499     -875     -875     678     407     262     262I don't see anything else changes (Only Sales of East is changing).
Now that you are writing to Parent member, then aggregation from Parent1's descendants will overwrite what you script just populated.
Regards
Celvin
http://www.orahyplabs.com
Please mark the responses as helpful/correct if applicable

Aggregation rule ignored for Logical sources

Hi,
We are using materialized views as logical sources for our logical tables. These logical sources contain aggregated data at higher level for dimensions. However, we have a logical source at the most detailed level for the dimensions.
Problem: We OBIEE hits the correct logical source based on dimensions selected in answers, it does not apply the default aggregation rule.
For instance, if a measure has aggregation as AVG, then when the logical sources corresponding to aggregated tables are queried, OBIEE does not apply AVG function. However, it does apply the aggregation rule when it uses the logical source at the most detailed level.
I have specified the aggregation content properly for every dimension.
Any pointers to debug the issue will be helpful.
Thanks,

Click on LTS of Table - Column Mapping - Select the logical column - click on expression - Put your logic here. You will get Aggregation rule is enalbed for the column.
Why ? -- Reason could be nested aggregation is not allowed. Aggregation on the normal column applied during query generation at run time. If you use that Agg.Measure to derive another Agg.measure server could not recognize it during runtime.

Logical column levels and aggregation

Hi all,
In order to have reliable results, I had to specify a dimension level in a logical column properties.
As a consequence, the generated query includes this level in the query (that's great), but no aggregation is performed afterwards. Therefore, when I display this measure alone in a flat table or a ticker, I have a set of detailed value instead of an aggregated value. The only place where I can see my aggregated value is in a pivot table.
In answers, I tried to :
- replace the default aggregation by an explicit SUM, or
- add a SUM() in the measure formula
but neither solved the issue.
Does anyone know how to solve it?
Thanks in advance.
Ced.

Hi,
What is the source for AGO measures PriorDollars and PriorUnits?
AGO(CurrentUnits, '?',?)
AGO(CurrentDollars, '?',?)
Have you set up hierarchy correctly (because you said that the granularity in your fact table is at week grain) and it should be like this:
Fiscal Year > Fiscal Quarter > Fiscal Month > Fiscal Week
It depends on how did you define your TIME dimension.
Try maybe like this:
PriorYEARDollars = AGO(CurrentUnits, 'YEAR',1)
and the same for
PriorYEARUnits =AGO(CurrentDollars, 'YEAR',1)
Now, if you put in the report
YEAR
CurrentUnits
CurrentDollars
PriorYEARUnits
PriorYEARDollars
you'll get only three rows (for 3 years) with PRIOR YEAR measures.
Try it.
A good reference for understanding AGO:
http://obiee101.blogspot.com/2008/11/obiee-ago-and-todate-series.html
Also you need to set chronological key correctly for TIME dimension.
Regards
Goran
http://108obiee.blogspot.com

Multiple fact tables, aggregation and model problems

Hi,
I am developing a OLAP Application with 2 dimensions (product,location) and a few measures (sales_qty, sales_value, sale_price, cost_price, promotion_price, average_market_price, etc). I also have a BiBean Crosstab to explore the data.
I'm having the following problems:
- The measures are in different fact tables.
When using cwm2_olap_table_map.Map_FactTbl_Measure, I can only map the measures from the first fact table, the others return "Exact fetch returns more than the request number of rows".
- The 'price_' measures shouldn't aggregate to higher levels of the dimension hierarchies. I have changed the default aggregation plan, but in the crosstab data is still shown in the higher levels. Is there any way to show N/A in levels that I don't want to aggregate?
- How can I add a calculated field that is the result of a complex set of business rules (with IF/THEN/ELSE statements and calls to existing oracle functions) and precalculate it during batch?
Thanks,
Ricardo

Keith, thanks for the quick answer!
Some questions regarding your comments:
1) The measures are in different fact tables
- My application will show all the measures in the same report. My question is, will performance be affected by creating separate cubes or creating one cube? I believe that if I don't use an AW, it shouldn't, but I will have an AW. Performance is the main reason why I'm using Oracle OLAP. I need fast access to measures in different fact tables in one report. Those measures will be used in complex calculated fields, and probably in 'what if' analysis.
2) When using cwm2_olap_table_map.Map_FactTbl_Measure, I can only map the measures from the first fact table, the others return "Exact fetch returns more than the request number of rows".
Here is the complete script I am using to create the cube:
execute cwm2_olap_cube.Create_Cube('OLAP','CUBE_REL_3','CUBE_REL_3','MY_CUBE','MY_CUBE');
execute cwm2_olap_cube.add_dimension_to_cube('OLAP', 'CUBE_REL_3','OLAP', 'DIM_STORE');
execute cwm2_olap_cube.add_dimension_to_cube('OLAP', 'CUBE_REL_3','OLAP', 'DIM_ITEM');
-- MEASURES - FACT TABLE 1 (F_SALES)
execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_MARGIN', 'Sales Margin','Sales Margin', 'Sales Margin');
execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_QTY','Sales Quantity','Sales Quantity','Sales Quantity');
execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_VALUE', 'Sales Value','Sales Value', 'Sales Value');
-- MEASURES - FACT TABLE 2 (F_PVP_MIN_MAX)
execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','PVP_MIN','pvp min','pvp min','pvp min');
execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','PVP_MAX', 'pvp max','pvp max', 'pvp max');
-- FACT TABLE 1 MAPPINGS
execute cwm2_olap_table_map.Map_FactTbl_LevelKey('OLAP','CUBE_REL_3','OLAP','f_sales','LOWESTLEVEL','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_MARGIN','OLAP','f_sales','SALES_MARGIN', 'DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_QTY', 'OLAP', 'f_sales', 'SALES_QTY','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_VALUE', 'OLAP', 'f_sales', 'SALES_VALUE','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
-- FACT TABLE 2 MAPPINGS
execute cwm2_olap_table_map.Map_FactTbl_LevelKey('OLAP','CUBE_REL_3','OLAP','f_pvp_min_max','LOWESTLEVEL','DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','PVP_MIN','OLAP','f_pvp_min_max','PVP_MIN', 'DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','PVP_MAX', 'OLAP', 'f_pvp_min_max', 'PVP_MAX','DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
-- CUBE VALIDATE
execute CWM2_OLAP_VALIDATE.Validate_Cube('OLAP','CUBE_REL_3');
The error is in the cwm2_olap_table_map.Map_FactTbl_Measure command for the first measure of the second fact table. Am I doing something wrong?
Regarding issues 3) and 4), I will follow your sugestions. I'll get back to you on this later.
Once again, thanks for the help, it is being most helpful.
Ricardo Sá

Direct Database Request Aggregation Rule

How can I do aggregations on a report created with a direct database request? While I can set the default aggregation rule in the fx formula, the aggregate E sign does not appear in the table view. How do I actually get to do a summation of the column?
Thanks,
Dinesh.

I guess I celebrated too soon. Now I lost the ability to display Columns & Table headings as separate rows. How can I accomplish the grouping of different columns under headings the way I accomplished with 'Columns & Table headings' as separate rows?
Thanks,
Dinesh.

Different Aggregation rule while aggregating

Hi Folks
in OBIEE 10.1.3.4.1 and BI Apps 7.9.6, using answers, i developed a report which has Organization division dimension and active headcounts as fact. while the report is created, the default aggregation( Server determined) rule that the server is using gives wrong results i.e. the grand total of the active Headcounts results to 9603 where as when i explicitly give "sum" as aggregation rule, i get the summation of the headcounts in the active headcount column which results in 25000. i checked this physical queries and couldnt get a clear understanding of the physical db queries. there is an aggregation rule on the Active headcount in the rpd which is like this
:- LAST(Core."Fact - HR - Operation (Workforce)"."Active Headcount") with time dimension
:- SUM(Core."Fact - HR - Operation (Workforce)"."Active Headcount") with any other dimension
and there is a case statement in expression builder like this:
CASE WHEN "Oracle Data Warehouse"."Catalog"."dbo"."Dim_W_EMPLOYMENT_D"."W_EMPLOYMENT_STAT_CODE" = 'A' THEN "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_WRKFC_EVT_MONTH_F_Snapshot"."HEADCOUNT" ELSE 0 END
btw, i did not create the same report with time dimension first and when i combined it with time dimension, i get the same results as before.
here are the different queries from log:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>
With out aggregation:
WITH
SAWITH0 AS (select T334016.ORG_HIER13_NAME as c2,
T334016.ORG_HIER13_NUM as c3,
sum(case when T264890.W_EMPLOYMENT_STAT_CODE = 'A' then T535616.HEADCOUNT else 0 end ) as c4,
T277242.PER_NAME_YEAR as c5
from
W_INT_ORG_DH T334016 /* Dim_W_INT_ORG_DH_Employee_Org */ ,
W_EMPLOYMENT_D T264890 /* Dim_W_EMPLOYMENT_D */ ,
W_YEAR_D T277242 /* Dim_W_YEAR_D */ ,
W_WRKFC_EVT_MONTH_F T535616 /* Fact_W_WRKFC_EVT_MONTH_F_Snapshot */
where ( T264890.ROW_WID = T535616.EMPLOYMENT_WID and T277242.ROW_WID = T535616.EVENT_YEAR_WID and T334016.ORG_WID = T535616.HR_ORG_WID and T535616.SNAPSHOT_IND = 1 and T535616.DELETE_FLG <> 'Y' and T277242.CAL_YEAR_START_DT >= TO_DATE('2004-01-01 00:00:00' , 'YYYY-MM-DD HH24:MI:SS') and (T535616.SNAPSHOT_MONTH_END_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and (T535616.LAST_MONTH_IN_YEAR_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and (T334016.ROW_WID in (0) or T334016.HR_ORG_FLG in ('Y')) and (T334016.ROW_WID in (0) or T334016.W_HIERARCHY_CLASS in ('HR-ORG')) and (T334016.ROW_WID in (0) or T334016.CURRENT_VER_HIER_FLG in ('Y')) and T535616.EFFECTIVE_START_DATE <= TO_DATE('2009-10-12' , 'YYYY-MM-DD') )
group by T277242.PER_NAME_YEAR, T334016.ORG_HIER13_NUM, T334016.ORG_HIER13_NAME)
select distinct SAWITH0.c2 as c1,
LAST_VALUE(SAWITH0.c4 IGNORE NULLS) OVER (PARTITION BY SAWITH0.c3 ORDER BY SAWITH0.c3 NULLS FIRST, SAWITH0.c5 NULLS FIRST ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as c2,
SAWITH0.c3 as c3
from
SAWITH0
order by c1
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<With aggregation:
-------------------- Sending query to database named Oracle Data Warehouse (id: <<8194579>>):
WITH
SAWITH0 AS (select T334016.ORG_HIER13_NAME as c2,
T334016.ORG_HIER13_NUM as c3,
sum(case when T264890.W_EMPLOYMENT_STAT_CODE = 'A' then T535616.HEADCOUNT else 0 end ) as c4,
T277242.PER_NAME_YEAR as c5
from
W_INT_ORG_DH T334016 /* Dim_W_INT_ORG_DH_Employee_Org */ ,
W_EMPLOYMENT_D T264890 /* Dim_W_EMPLOYMENT_D */ ,
W_YEAR_D T277242 /* Dim_W_YEAR_D */ ,
W_WRKFC_EVT_MONTH_F T535616 /* Fact_W_WRKFC_EVT_MONTH_F_Snapshot */
where ( T264890.ROW_WID = T535616.EMPLOYMENT_WID and T277242.ROW_WID = T535616.EVENT_YEAR_WID and T334016.ORG_WID = T535616.HR_ORG_WID and T535616.SNAPSHOT_IND = 1 and T535616.DELETE_FLG <> 'Y' and T277242.CAL_YEAR_START_DT >= TO_DATE('2004-01-01 00:00:00' , 'YYYY-MM-DD HH24:MI:SS') and (T535616.SNAPSHOT_MONTH_END_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and (T535616.LAST_MONTH_IN_YEAR_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and (T334016.ROW_WID in (0) or T334016.HR_ORG_FLG in ('Y')) and (T334016.ROW_WID in (0) or T334016.W_HIERARCHY_CLASS in ('HR-ORG')) and (T334016.ROW_WID in (0) or T334016.CURRENT_VER_HIER_FLG in ('Y')) and T535616.EFFECTIVE_START_DATE <= TO_DATE('2009-10-12' , 'YYYY-MM-DD') )
group by T277242.PER_NAME_YEAR, T334016.ORG_HIER13_NUM, T334016.ORG_HIER13_NAME),
SAWITH1 AS (select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3
from
(select LAST_VALUE(SAWITH0.c4 IGNORE NULLS) OVER (PARTITION BY SAWITH0.c3 ORDER BY SAWITH0.c3 NULLS FIRST, SAWITH0.c5 NULLS FIRST ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as c1,
SAWITH0.c2 as c2,
SAWITH0.c3 as c3,
ROW_NUMBER() OVER (PARTITION BY SAWITH0.c3 ORDER BY SAWITH0.c3 ASC) as c4
from
SAWITH0
) D1
where ( D1.c4 = 1 ) ),
SAWITH2 AS (select sum(case when T264890.W_EMPLOYMENT_STAT_CODE = 'A' then T535616.HEADCOUNT else 0 end ) as c2,
T277242.PER_NAME_YEAR as c3
from
W_EMPLOYMENT_D T264890 /* Dim_W_EMPLOYMENT_D */ ,
W_YEAR_D T277242 /* Dim_W_YEAR_D */ ,
W_WRKFC_EVT_MONTH_F T535616 /* Fact_W_WRKFC_EVT_MONTH_F_Snapshot */
where ( T264890.ROW_WID = T535616.EMPLOYMENT_WID and T277242.ROW_WID = T535616.EVENT_YEAR_WID and T535616.SNAPSHOT_IND = 1 and T535616.DELETE_FLG <> 'Y' and T277242.CAL_YEAR_START_DT >= TO_DATE('2004-01-01 00:00:00' , 'YYYY-MM-DD HH24:MI:SS') and (T535616.SNAPSHOT_MONTH_END_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and (T535616.LAST_MONTH_IN_YEAR_IND in (1) or T535616.EFFECTIVE_END_DATE >= TO_DATE('2009-10-12' , 'YYYY-MM-DD')) and T535616.EFFECTIVE_START_DATE <= TO_DATE('2009-10-12' , 'YYYY-MM-DD') )
group by T277242.PER_NAME_YEAR),
SAWITH3 AS (select distinct LAST_VALUE(SAWITH2.c2 IGNORE NULLS) OVER ( ORDER BY SAWITH2.c3 NULLS FIRST ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as c1
from
SAWITH2)
select SAWITH1.c2 as c1,
SAWITH1.c1 as c2,
SAWITH1.c3 as c4,
SAWITH3.c1 as c5
from
SAWITH1,
SAWITH3
Thank you in advance
kumr

Passing parameters from one report to another. If you go to Column Properties you will find 2 main types of Drills. One is a default drill which comes from the repository. The other is a navigation drill wherein you can specify a target report. So basically when you click on the column of your report that will navigate to another report and will also pass the parameter(value clicked) and will filter the target report. I am not sure which version of OBI EE you are on?
Thanks,
Venkat
http://oraclebizint.wordpress.com

Based on dimension aggregation

I have a fact table with 2 sources. One of these sources has only one measure and I am having problems with it.
This measure must use based on dimension aggregation, but it don't work. When I set this option, the measure shows a blank value in Answers, but when I switch to a default aggregation rule (not based on dimension), like sum or max, the value is shown correctly in Answers.
My doubt is: is it necessary any other configuration on dimensions or fact tables in order to use based on dimensions aggregation? I just change the value in the aggregation tab of the measure, is there any other step necessary?
Thanks

I found this text on the help, but I didn't understand, because when I check the "based on dimensions" check box, I can choose aggregation rules for each dimension, not only the time dimension.
Also, I found in the help menu:
"In the Aggregation tab, select the Based on dimensions check box.
The Browse dialog box automatically opens.
In the Browse dialog box, click New, select a dimension over which you want to aggregate, and then click OK.
In the Aggregation tab, from the Formula drop-down list, select a rule."
I did the same steps suggested by the text above, but it didn't work.

10:1 rule for skip - level aggregation

Hy.
I'm new in OLAP. I'm using AWM on 10gR2 and could somebody explain to me what does mean 10:1 rule. I know that is ratio of children to parent level which is 10:1, but example that i study doesn't show me that.
Example:
(from Oracle 10g documentation, data warehousing, OLAP Application Developer's Guide, part 7 Aggregating Data, Case Study: Aggregating a Moderately Sparse or Dense Cube)
SELECT COUNT(DISTINCT ship_to_id), COUNT(DISTINCT warehouse_id),
COUNT(DISTINCT region_id),COUNT(DISTINCT total_customer_id),
COUNT(DISTINCT account_id), COUNT(DISTINCT market_segment_id),
COUNT(DISTINCT total_market_id), FROM global.customer_dim;
Global is a very small data set, so few adjacent levels have the desired 10:1 ratio of children-to-parent dimension members. Table 7-4 and Table 7-5 identify the appropriate levels to be calculated and stored for the two hierarchies. Only eight members are stored out of a total of 45 aggregate members.
On the Summarize To page for the Units Cube, select the precalculated levels for Customer, and select all levels for Time, Product, and Channel.
Table 7-4 Precalculated Levels in the Customer Shipments Hierarchy
Level Members Precalculate?
Total_Customer 1 No
Regio 3 Yes
Warehouse 11 No
Ship_To 61 Yes
Level Members Precalculate?
Total_Market 1 No
Market_Segment 5 Yes
Account 24 No
Ship_To 61 Yes
If I use rule 10:1 child to parent member why Warehouse and Account doesn't have precalculate set to Yes If they have 10 or more child values below.
Please help!!!!

It is a long time since I used the global schema and at the moment I am using the BI common schema so I am trying to quote from memory here regarding the data. The figures you have outlined below are number of members at each level, a better calculation would be the average number of children that would be returned when drilling from one level to the next. In this case there are 3 regions and 11 warehouses, so drilling from region to warehouse is likely to return at most 4 warehouses on average.
To quote from the OLAP documentation:
This 10:1 rule is best applied with some judgment. You might want to permit a higher
ratio for levels that you know are seldom accessed. Or you might want to store levels
at a lower ratio if you know they have heavy use.
The key for pre-aggregation is understanding expected usage patterns of your users. In this case for the global schema I expect it is optimised for demo purposes and the levels that are precomputed are those most likely to be used in a demo.
In your case you need to understand where your users will most likely start there analysis and make sure that combination of levels is precomputed to ensure fast response times for the first query and then monitor usage patterns and get feedback from users over time.
If you are using Discoverer OLAP Plus client you could export the Discoverer catalog and analyse the XML for each report to determine which values are being created. I don't think there is an easy way to monitor OLAP queries at the moment (I could be wrong but I have not seen anything in Enterprise Manager that would help in this area). You could quickly create a program in PL/SQL or OLAP DML that would help analyse the XML for Disco reports. If you are using BI Beans you can scan the XML from the BI Beans catalog for each report.
For the OLAP Spreadsheet Addin it might be necessary to create a program to scan the $V_SQL/V$SESSION tables to work out which data points are being requested by users.
Of course you could just try pre-computing every other level which I think was/is the default aggregation plan generated by OWB and AWM.
Hope this helps
Keith

Difference between aggregation rule and column formula in edit formula

Anybody please help what is the use of aggregation rule and column formula in edit column option.
What is the difference if I apply sum in aggregation rule with apply sum(column name) in column formula.
When do I need use which one.
Thanks in advance

When you build a column in the rpd, you have the option of determining if the column should be aggregated in some way or not. For dimension columns, you wouldn't put aggregation. For say, an accoun ledger balance column, you might put the aggregation SUM or AVERAGE. Whatever aggregation you put on this column will be the "default" aggregation of the column in Answers.
So in Answerrs, if you use the Account Ledger Balance column and you only have Region as the dimension, OBIEE will aggregate or SUM the ledger balances so you have a SUM for the region level. If you had district, than the ledger balance column will aggregate to the district level. This is a convenient way to build reports without having to specify what the aggregation should be.
However, OBIEE gives you the ability to override what the default aggregation is for a particular column. This is the purpose of the drop down in the bottom left of a column when you click the fx button.
Say the default aggregation of ledger balance is SUM in the rpd, but for the report you are building, you want the average, you can apply the AVERAGE function in the fx window and it will overridge the SUM aggregation rule that was in the rpd.
Got it?

EDIT AGGREGATION RULE IN ANSWER FOR A MEASURE

Hello Experts,
I have a measure in my fact table which is a "price" and I don't want to set up a default aggregation (sum, avg, max, min...etc) in my Business Model (Administrator). I want the user to be able to set an "Aggregation Rule" in Answers to that measure.
So, I go into Answer, select my measure from my model and then click on Edit formula and change the Aggregation Rule to "Avg" this seems to don't work.
I think I'm missing something, a setting or option.
I'll appreciate if you guys can help me with this...thanks.

Hey mma,
I'm referring to the "Edit Column Formula" option and then I click on "Column Formula". At the bottom of that tag there is a section that says "Aggregation Rule" with a drop down box that shows; Avg, Max, Min...etc. Thats where I make the change to "Avg" and it doesn't work.
Edited by: PabloC2 on Sep 18, 2008 3:57 PM

Default aggregation

Similar Messages

Maybe you are looking for