You should not use Obiee agents for that, Use Bi Publisher instead which is the tool of choice for that kind of tasks.

What is your exact requirement? Just transposing these columns to rows by itself makes no sense at all

Have a look at this: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=444427904736411&parent=DOCUMENT&sourceId=2108401.1&id=20…

Have you tried just adding the filters on the measure in the criteria filter section? That works for me.

You can perfectly meet the requirement If you design your data model like we told you. The client tells you WHAT they need you decide HOW to do this.

That's because you have different measures for each year instead of one budget measure. Your Design is incorrect. At least that is what I understand from your description. Year Budgets should be only distinguished by the period hierarchy, they should not be separate columns. So, what you should do is merge the year budget…

You could calculate separate measures like this: CASE WHEN "Project Dimension"."ProjectType" = 'Realty' THEN "Measures"."Value" Else 0 END. Per view exclude the measures you do not want to show.

I think R can be used to achieve this as well: http://www.oracle.com/technetwork/database/database-technologies/r/r-enterprise/ore-trng5-operatnlzgrscripts-1501640.pdf Haven't looked into it myself though

Agreed, the join on dates is not necessary here...Just make sure the new dimension key is used in the fact.

Sorry Christian, I Meant to reply to OP but messed up apparently. ;-)

You will have records like this: Dim_Department: id department_name division_id effective_start effective_end 23 Product Design 1 01/01/2017 31/03/2017 24 Product Design 2 01/04/2017 31/12/9999 fact_table department_id report_date quantity 23 30/03/2007 50 23 31/03/2007 100 24 01/04/2017 75 <--- New department allocation…

You can use Aggregation based on Dimensions: Aggregation Based on Dimensions - ClearPeaks Blog ClearPeaks Blog http://www.wegobeyond.co.uk/blog/entry/aggregation-based-on-dimensions-in-obiee.html

You need to design your DWH to keep track of dimension changes. Typically you would create a Slowly Changing Dimension type 2 for this. What are Slowly Changing Dimensions?

So, the result you are looking for would be something like this? Capacity | Enrollments | Available Class A 20 13 7 Class B 30 25 5 --------------------------------------- 50 38 12 I still think Thomas' solution should work and it is the best solution IMO. Alternatively, you could model this having a 'Capacity' Fact and an…

And you are going to leave it at that not knowing what problems it may (or may not) cause in the future? ....

Not exactly sure what you mean but if you generally want years to display as YY-YY then the best way to do this is to add a column containing this value to your time dimension.

You might want to have a look here: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi1221/cad/cad12c.html

No, It depends, It might in certain circumstances but it does not in many others. Also see Gianni's reply

No, I assume the original poster wants to refresh because the dashboard uses (near) real-time data. Otherwise I do not really see the point of an automatic refresh.

The tools you suggest would still not do a actual data refresh but just a page refresh (F5)