cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Splitting Time Dimension

Former Member
0 Likes
254

Hi all

We are currently in the initial stages of a BPC implementation (I believe it is v10.1).

At present we use Oracle Hyperion Planning as our budgeting tool, where time is split between two dimensions (Year and Period) as default.

As I understand it, default behaviour for time in BPC is to combine year and period as one dimension. Is this correct?


We currently have weeks as our base member; I would assume that the time dimension would get a little large if week members were repeated for each year in the same dimension (52 base members for every year). If in the future we decide to budget at a more granular level and add days as our base member then suddenly there are 365 base members for every year (plus the roll ups to 52 weeks then 12 periods).

Does any of this really matter? Is this approach commonly used across any implementations you have worked on? Is it possible to split the time dim into two and if so does it bring any benefits / drawbacks?

Thanks for your time

JB

Accepted Solutions (1)

Accepted Solutions (1)

Shrikant_Jadhav
Active Contributor
0 Likes

Hi John,


As I understand it, default behaviour for time in BPC is to combine year and period as one dimension. Is this correct?

Correct !

Having day as lowest level in time dimension is what we did and it's working. I thing it's approach commonly used approach.

The only thing you need to take care is that maintain all property correctly specially  TIMEID to member.

One time efforts are more but it works as expected.

Having two separate dimension may be cause performance, data roll up and don't have more idea.

Shrikant

Answers (1)

Answers (1)

former_member5472
Active Contributor
0 Likes

Hi,

There is no restriction in terms of Time Dimension going down to DAY level.Week level implementations are common and i have been involved in many of them.

Splitting Time dimension may not be a good idea. BPC will not allow you to have two dimension of Type T in same Model.

We have taken a different approach where  we propose  Time to be at Week/Month level and in case user wants to see more detail, they can use "Drill Through" functionality which will take them to detail BW cube.

I hope this gives you an idea about how to design your Model.

Prat

Former Member
0 Likes

Thanks to both of you for your insights.

Will take these thoughts on board for our design.

If anybody else wishes to give their opinion then feel free

JB