Web Intelligate Summer Report drill down and drill up problem

Question

I use summary table and @aggreage_aware function to design a universy.  I want WI report shows highest level summary table data first, then drill down to next high summary table data.  But when I drill up back,  it still shows be next high summary table data.  I don't use the report to do any calculations.  I just want it shows different level data.
Detail:
I have three tables:
1.  Month_Data table:  - Base fact data table.
Year
Quarter
Month
Department ID
Supplier ID
Score          -- Measure type
2.  Quarter_Data table: - High level summary table.
Year
Quarter
Department ID
Supplier ID
Score          -- Measure type
3.  Year_Data table:  - Highest level summary table.
Year
Department ID
Supplier ID
Score          -- Measure type
I like to create a web intelligence report that shows data from year_data table:
Year          Score
2008          105
2007          99
2006          90
If I drill one level down, It will show data from quarter_data table:
Year (example 2007)
Quarter1     Score
Quarter2     Score
Quarter3     Score
Quarter4     Score
If two level drill down, it will show data from month_data table:
Quarter1
     Month1          Score
     Month2          Score
     u2026
     Month12                     Score.
No calculation needed on the report.
I will use follow steps to create a universe:
1.  Three tables will be three classes.  The classes order is:
     Year_Data class;  Quarter_Data class; Month_Data class.
2.  When I create universe, I join:
Year_Data  class to   Quarter_data class:
Year to year                 1 to n               
Department ID to Department ID          1 to n
Supplier ID to Supplier ID          1 to n
Quarter_Data class to Month_Data class:
Year to Year               1 to n
Quarter to quarter               1 to n
Department ID to Department ID          1 to n
Supplier ID to Supplier ID          1 to n
3.  Create a filter class with object Department ID and supplier ID.
4.  I create two aggregate aware classes:
Agg_dimension class:
     Year:    aggregate_aware(year_data.year, quarter_data.year, month_data.year)
     quarter: aggregate_aware(quarter_data.quarter, month_data.quarter)
     Month:     aggregate_aware(month_data.month); 
Agg_Measure class:
     Score: aggregate_aware(year_data.score, quarter_data.score, month_data.score)
5.  I may re-define year, quarter, month and score as aggregate_aware function for objects in all classes:
     Year:     aggregate_aware(year_data.year, quarter_data.year, month_data.year)
     quarter: aggregate_aware(quarter_data.quarter, month_data.quarter)
     Month:     aggregate_aware(month_data.month); 
     Score:   aggregate_aware(year_data.score, quarter_data.score, month_data.score)
6.  create user hierarchies: 
agg_dimension.Year
agg_dimension.quarter
agg_dimension.month 
7.  Figure out Aggregate Navigation  -- it is easy.
Then create a report.  I put follow objects on report:
Agg_dimension.year          agg_measure.score
When I run report, it shows right data:
Year_data.year          Year_data.score
On the report. I drill down on year, it shows right data.
Quarter_data.Year:
Quarter_data.quarter1                quarter_data.score
Quarter_data.quarter2                quarter_data.score
Quarter_data.quarter3                quarter_data.score
Quarter_data.quarter4                quarter_data.score
But when drill it up back on quarter, it shows:
Quarter_data.year     quarter_data.score1
Quarter_data.year     quarter_data.score2
Quarter_data.year     quarter_data.score3
Quarter_data.year     quarter_data.score4
Not
Agg_data.year          agg_data.score.
It has drill up back problem on my report.
Please help.
Thanks
Frank Han

Answer 1

and keyfigures are coming frm 2lis_03_bf..But when i drill down on purchase organization, purchase grou , vwndor account group and planning group then # is coming instead of value....i dont the reason for this..
Did you chk if you have vendor, purchase org, all this coming from 2LIS_03_BF??
Can you chk in listcube transaction what is the output by putting the same restrictions as in the query?
Edited by: mansi dandavate on Jul 10, 2009 11:37 AM