Hi,
I thought this might be useful for other PALO users too (espcecially for those who did not work with OLAP databases before).
Original thread:
http://www.jedox.com/community/palo-foru…p?threadid=1689
8<
..You also can build virtual cubes (they don't hold the data themselves and can e.g. have more or less dimensions than the original cube. Here is one example based on the Demo db (Sales Cube).
###just an exmpale###
Sales cube got the following dimensions:
1 Products (Desktop L, Desktop Pro,...)
2 Regions (Germany, France,...)
3 Months (Jan, Feb,...)
4 Years (2005, 2006,...)
5 Datatypes (Actual, Budget,...)
6 Measures (Units, Turnover,...)
Let's say you like to build a virtual cube with only Units.
Create a cube named "MyUnits" with the following dimensions:
1 Products
2 Regions
3 Months
4 Years
5 Datatypes
You see, there is one dimension less.
Now create the following rule for cube "MyUnits":
[] = PALO.DATA("Demo", "Sales", !'Products', !'Regions', !'Months', !'Years', !'Datatypes', "Units")
Use Paste View to check the values in your new cbues, which are only Units in this case.
You can also use
[] =N: PALO.DATA("Demo", "Sales", !'Products', !'Regions', !'Months', !'Years', !'Datatypes', "Units")
This will only retrieve the base elements and your new cube does the consolidation by itself.
Important: There are no physically values stored in your cube, they are fetched in real time from cube "Sales".
Check it out and have fun.
>8
Holger
