Hello Gaandni,
there are various ways, depending on what you need:
1. Do you need the day granularity? If not you can still provide the facts
every day, but include only month and above levels in the time dimension. So
you could compare directly with the goals.
2. You can build 2 hierarchies on the time dimension and use the month based
one for the goals and for comparing with the bookings.
3. You can build a booking cube on days and a goal cube on months and form a
virtual cube based on some other dimension, like accounts (you need at least
1 common dimension for doing this).
HTH
Helmut
"Gaandni" <gaandni2000 (AT) hotmail (DOT) com> schrieb im Newsbeitrag
news:uLOdnUgwkrayKGHdRVn-oA (AT) comcast (DOT) com...
Quote:
Hello
I would greatly appreciate pointers to reference material to help me
resolve the following problem :
1. We have a Time dimension with a granularity of Day, since our Bookings
data comes in at that granularity. Goaling (for our sales team) is done on
a monthly basis; granularity for this data along the Time dimension would
be Month. The reporting requirement is to display Plan vs. Bookings by
month, and facilitate drilling down to view each individual Booking.
How do I model the Time Dimension ? Do I need a separate Time dimension at
Month granularity for Goaling data ?
Thanks very much for your help. |