Here's one approach in broad strokes:
1) build a cube based on hopeful sales fact table
2) combine the 2 cubes in a virtual cube
The virtual cube will have two measures, one from each cube. For most
planning apps I'm not partial to this design because it doesn't organically
adapt (sans schema change that is) if for instance you later need track
[optimistic hopeful sales] and [pessemistic hopeful sales] separately. This
is where a version dimension, commonly named Scenario, becomes useful.
tom @ the domain below
www.tomchester.net
"Michael Morse" <mike.morse (AT) micromo (DOT) com> wrote
Quote:
I have a cube that shows sales totals with the following
dims.
CustomerByRegion | DateTime | Engineer
how could I than tie in budgeted (hopeful) sales and
display this as a measure as well?
My (hopefulSales) table contains an ID back to the
DateTime table and an ID back to the Engineer table.
Any ideas? |