'Time' dimension hierarchy Required

Dear all,
We came across one requirement where 'Time' dimension having 365 days along with month, quarter, halfyear and yeartot as their ancestor.
"Time" Dimension hierarchy:
Time
- Yeartot
- Half year
- Quarters
- Months
- Days
Also we need alternate hierarchy in time dimension:
Time
- Yeartot
- Weeks
- Week1
- 1 Apr
- 2 Apr
- Week2
Weeks are Monday to sunday.
We are using 11.1.1.2 version.
Can anyone suggest me how to achieve this in Planning?
Thanks in Adv,
Bunny

I believe the limit for Planning's Period dimension is 400 members.
That's going to get you the first bit, but not the alternate hierarchy.
Does this alternate hierarchy have to be in Planning, or could it be in Essbase only?
This isn't exactly a recommended strategy, but I think you can still use the HSP_UDF UDA in Essbase to basically make your alternate hierarchy happen only in Essbase. It won't show up on forms, but will be available from a reporting tool.
I have not tried HSP_UDF (it was used all the time on pre System 9 (maybe Planning 4) Planning apps to get in member formulas) in 11, so it may be worth trying a small alternate hierarchy with that UDF and then forcing a refresh to see if it still sticks about.
Regards,
Cameron Lackpour

Similar Messages

Time Dimension: Naming requirement?

I am trying to create a YTD calculation in a cube using BI beans/Jdeveloper. This used to work fine in a previous version of the cube. In the new cube, the 'next' button remains grayed out if I select the 'YTD calculation (or any other time related calculation)
One of the changes between the cubes seems to be that we renamed the time dimension to t_time_month. I am wondering if BI beans has a requirement that the time dimension ends in 'Time', similar to the requirement that the dimension name needs to end with 'Name'. I can't find a way to tell BI beans which is the time dimension, so maybe the name is the only way it could know?
Is there a document that describes this type of requirements for BI Beans?
Thank you in advance for your help.
Cor Wooning

Hi,
There are certain requirements for a dimension to be of type time. Each level in the dimension must have two attributes: End Date and Timespan.
If your DW environment is purely relational you can use OEM to check the status of your time dimension. There is a radio button to indicate if the dimension is of type time. You can try setting this, when you apply the change OEM will validate the dimension to see if it complies with the requirements for a time dimension.
If you are using Oracle Warehouse Builder to construct your DW environment, it provides a default mapping and dimension within a best practice MDL file. (it is located in the OWB_HOME/owb/misc/time directory).
There should me information in the OLAP Developer and user manuals relating Analytic Workspace dimensions
Hope this helps,

Time dimension hierarchy

Hi,
Im creating time dimensional hirearchy in BMM Layer in 10g and getting the below error
[nQSError:15001]Could not load navigation space for subject area Test.
[nQSError:15019]Table period is functionally dependent upon level Month,but a more detailes child level has associated columns from that same table or a more detailed table.
plz anyone help me
Thanks
Edited by: Business Intelligence Foundation on May 24, 2012 2:16 AM

Hi,
This message occurs when either a key is defined under the Total level or when the first child level below the Total level contains two keys.
Right-click on the Total level and select Properties.
The Keys tab should be grayed out.
If it is selectable, check to see what is there and delete it.
Go to the next level down, right-click, select the Keys tab.
Only one Key should appear.
Delete the key that does not belong.
Thanks,
Balaa...

A Question Related to Dimension Hierarchy

Hi All,
While going through some hierarchies, i found that some columns were associated with the levels in hierarchy but these columns were not part of level keys.
I want to know that what is difference between the result when columns that are not level keys are associated with a logical level and when such columns are not associated with a logical level ?
Does such columns affect the result when selected in BI Answer?
For exp -
Suppose i have below time dimension hierarchy -
Time
->Grand Total Level 0
---> Year Level1
Year (Level Key)
Year Start Date
Year End Date
---> QuarterLevel2
Quarter(Level Key)
Quarter Start Date
Quarter End Date
---> MonthLevel3
Month(Level Key)
Month Start Date
Month End Date
---> Day Level4
Day (Level Key)
Day Start Date
Day End Date
These start date/end date columns are not part of level keys.
The same thing i have observed in other hierarchies too.
I want to know that what would happen, if these columns are not present at these levels?
So When should we associate columns those are not part of level key to levels and when we should not associate ?
Thanks,
Ashish

Hi ,
The non key columns used in each of the levels help in faster retireval for that aggregate level .
If you look closely at these columns you will find these to be unique ,now having said that another point is that these levels are also used for aggreagation
as we all know.
For ex at the month level the key identifies all the unique moths but if data has to be shown for one particualr month then with the start momth date and end month date the retrieval would be still better :)

Oracle Business Intelligence Dimension hierarchy question

Hi,
I am prasanna.I have a problem while display the data from dimension hierarchy.I have created a time dimension hierarchy.I can drill down upto week number but i m unable to display the time_id(this is the last level of the hierarchy).When i check the properties of the time_id,the HIDE check is checked.Even if i uncheck the checkbox also i m unable to display that column.How to change properties of the column manually.I can find the column at the criteria but not at results tab.How can i display the column.
Thanks ,
prasanna

HI Prasanna,
what is the least granularity for your time dimension? is at week level or day level. verify the dim hier configuration in rpd. if you define time_id as level key you dont get that column in answers results while drilldown. you may create another logical column and drag it to week level as an attribute then you will get it. and why do you need time id in answers. generally we dont use id's for reporting.
try again after above configuration and you will be all set.
Thanks
Jay.

BPC Time Dimension - 13 periods NOT Calendar

My client reports 13 periods in a year (4 weekly).
Quarter two contains 4 periods (periods 4, 5, 6, 7).
I was reading a post about how to set this up properly using the UserTimeId property. They had a situation where they needed to put their 13th period in Qtr 4, and they discussed using this property, but the answer didn't go into exactly what settings to put in the UserTimeid property.
Could someone explain how to set this up in BPC so that it calculates properly - my system is a YearToDate system (not periodic),
regards
scott Farrington

Hi Scott,
Have you tried just putting these 4 periods in Quarter 2 on your time dimension hierarchy? I believe the hierarchy (not the properties) is what drives QTD reporting, so theoretically that should work. I have not tried your specific scenario however as it is a fairly uncommon setup.
If that doesn't work and you can explain exactly what kind of issues you are seeing, then it might be easier for others to come up with helpful solutions.
Thanks,
Ethan

Time Dimension 2 PARENTH2 and PRIOR,NEXT

Hi all,
We have standart TIME hierarchy from AppShell (MONTH, QUARTER, YEAR). But in some cases users want insert data in detalization by week. We decide add additional ID's with detalizations to weeks and add they in second hierarchy. Everything is ok in system.
But than we try write scrip logic with PRIOR or NEXT which use data from previous year it doesn't work. But than we use PRIOR or NEXT with current year months everything ok.
Example of logic.
*XDIM_MEMBERSET TIME = PRIOR, %TIME_SET%, %YEAR%.DEC
*CALC_EACH_PERIOD
*WHEN P_ACCT
*IS A01
*REC(EXPRESSION=%VALUE% - GET(P_ACCT="A02",TIME=PRIOR), P_ACCT = A03)
*ENDWHEN
*ENDWHEN
Then we save data on January it doesn't work. BUt on December prev year A02 and January A01 we have data.
Maybe you have some advises according second TIME dimension hierarchy. I think problem on it.
Best regards,
iaroslav

Hi,
Here is fragment of debuglogic.
Start time --->7:29:17 PM - Date:9/28/2011 (build code:7.5.107)
User:T2RU\bpc.sysadmin
Appset:DEVTELE2
App:BUDGETS
Logic mode:0
Logic by:
Scope by:CATEGORY,INPUTCURRENCY,P_BF,P_BUDDIM,P_BUDDIM2,P_BUSTYPE,P_CC,P_CITY,P_DATASRC,P_PROJECT,TIME
Data File:
Debug File:D:\PC_MS\DATA\WebFolders\DEVTELE2\BUDGETS\PrivatePublications\bpc.sysadmin\TempFiles\DebugLogic.log
Logic File:
Selection:DIMENSION:CATEGORY|BU|DIMENSION:INPUTCURRENCY|RUR|DIMENSION:P_BF|IBF19|DIMENSION:P_BUDDIM|NO_BUDDIM|DIMENSION:P_BUDDIM2|NO_BUDDIM2|DIMENSION:P_BUSTYPE|NO_PRODUCT|DIMENSION:P_CC|3_KEM_FF_FA|DIMENSION:P_CITY|KEM|DIMENSION:P_DATASRC|CCDATA|DIMENSION:P_PROJECT|PR_PL|DIMENSION:TIME|2012.JAN|
Run mode:1
Query size:0
Delim:,
Query type:0
Simulation:0
Calc diff.:1
Formula script:
Max Members:
Test mode:0
Is Modelling:1
Query Type:0
Max members:
Region:
DIMENSION:CATEGORY
BU
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_ACCT
----- There a lot of accounts <All> accounts and I dont show it all
DIMENSION:P_BF
IBF19
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_CC
3_KEM_FF_FA
DIMENSION:P_CITY
KEM
DIMENSION:P_DATASRC
CCDATA
DIMENSION:P_PROJECT
PR_PL
DIMENSION:TIME
2012.JAN
DIMENSION:P_CC
3_KIR_FF_FA
DIMENSION:CATEGORY
BU
DIMENSION:P_DATASRC
CCDATA
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_BF
IBF19, IBF15
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:TIME
PRIOR, %YEAR%.JAN, %YEAR%.FEB, %YEAR%.MAR, %YEAR%.APR, %YEAR%.MAY, %YEAR%.JUN, %YEAR%.JUL, %YEAR%.AUG, %YEAR%.SEP, %YEAR%.OCT, %YEAR%.NOV, %YEAR%.DEC
DIMENSION:P_ACCT
<ALL>
Loading TIME.TIMEID
Time to load properties:0.0 sec.
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
into #tblTempLogic_266166
from tblFactBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFactWBBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
and SOURCE = 0
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFAC2BUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
select tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID,sum(SIGNEDDATA) as SIGNEDDATA
from #tblTempLogic_266166 as tmpTable
group by tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID
drop table #tblTempLogic_266166
I saw that TIMEID 10000425 is incorrect -its 2012.DEC.WEEK3 from second hierarchy
Thanks,
Bets regards
Iaroslav

Time Dimension Working Days

Hi i have a calendar table
Has Year , Month, Week, Date and a flag for a working day or not..
Is there anyway i can use this working day flag in my Time Dimension Hierarchy so that under Date i can have another drill Working Days ...
(Non working day is where flag = 'Y')
Year - Month - Week - Day - Working Day
or Even
Year - Month - Week - Working Day
Cheers
Bibi

Year - Month - Week - Working Day
You could acheive this by putting a filter on your logical table source to exclude non-working days. Or maybe just remove the non working days from the source table
The trouble with trying to put an extra level in beneath Day is that your primary key, I.e. your lowest level for the date dimension in this case is Day. Working Days won't roll up into Days as they are at the same level.

Having issues when creating alternate hierarchy in time dimension

Hi Everyone
I used How to guide of MS version 7.5 to build 2 hierarchies in time dimension.
It worked in MS version.7.5
But when i copied the same dimension members to NW version the alternate hierarchy (parenth2) doesn't work.
I mentioned all the required properties for both roll ups (like parenth2,timeid,usertimeid,ISBEGINNING).
Any idea?
thanks
reddy

"This sounds confusing to me as to how a stored hierarchy can contain a shared member from a dynamic hierarchy"
You just need to understand how things are stored in ASO for this to make sense.
A level 0 member with no formula, even though it is in a dynamic hierarchy is still a stored member.
-- All level 0 members that do not have formulas are stored in ASO.
Upper level members are all "dynamically calculated".
-- Upper level members of dynamic hierarchies are pure dynamic.
-- Upper level members of stored hierarchies are candidates to have their values pre-aggregated and stored in a view.

Star Schema Dimension Hierarchy Changes Over Time

Say you have a dimension hierarchy with the level Department that has a child level Division. The Sales Division belonged to the Financials Department up until July 9th, 2011, after which it was moved to the Marketing Department. How can you make it so that both Sales Divisions are interpreted as the same Division, rather than two different Divisions as BI Answers does by default?

I don't think SCD1 would work as BI Answers essentially splits things via both keys and description fields, resulting in odd behavior such as this:
Time
Division
# Employees
All Time
Sales
16
22
Regarding SCD2:
So is there something I need to do on the repository so that BI Answers knows to switch between the two versions of the same Division at that particular time, such that I can make an Analysis such as this:
Month
Division
# Employees
% Change
May
Sales
15
-6%
June
Sales
15
0%
July
Sales
14
-7%
August
Sales
22
+57%
Instead of this:
Month
Division
# Employees
% Change
May
Sales
15
-10%
June
Sales
15
0%
July
Sales
2
14
-87%
0%
August
Sales
22
+57%

Locking Periods using the Second Hierarchy in the Time Dimension

Hi,
They are not usiing work status for this...
I am at a client, and they used the second hierarchy in the time dimension to lock periods. If they left the second hierarchy blank, no data can be written to it. To open the open the period, they code the Second Heirarchy with CONS_OPEN. Just wondering if anyone has information on this?
It was working fine, then we needed to run a transport to move BPC to a new machine, and it stopped working. Not sure if anyone has done it this way before?
Thanks,
Chandra

Dear Kacper,
the way I understood, there are two separate questions in this post, namely:
I'm using a shared resource in multiple actors, and the code accessing the resource can take quite some time to execute. How can can I ensure this does not mess up the timing of one or all accessors?
I'm using a shared resource in multiple actors, and the code accessing the resource can generate errors if I try to access it from multiple places. How can I ensure synchronization between all accessors?
As for the first question, the optimal solution to separate the resource prone to timing issues in a different thread/actor. Put anything that is not strictly timed (file access, network comunication) in a separate loop. For each actor, you will get queue references to communicate with, so instead of logging the measurements in the actors where they are made, just queue them up for a different loop to process.
For the second part, the same logic still applies. Ideally, every singular resource should be handled by its own thread and nowhere else, so if anything else needs data from/to said resource, it can send a request to the dedicated thread or actor.
If, for some reason, this is not sufficient, you have to handle synchronization in some other way. There are a lot of techniques here, for example:
Create a named semaphore or lock as a part of the class. Have class functions use the semaphore before accessing the resource.
Use actor messages. Have a "resource in use" or "resource released" messages sent to all users whenever obtaining or releasing said resource.
Have a separate actor handle all resources, awarding them to threads needing them. This method also allows setting priorities between requests.
These are just a few examples, there are many other options.
Please let me know if this was helpful.
Kind regards:
Andrew Valko
National Instruments Hungary

Date and Time dimensions

After reading the following article, I have decided to use SSAS dimension wizard for generating our Date dimension, which creates a DATETIME PK.
http://www.made2mentor.com/2011/05/date-vs-integer-datatypes-as-primary-key-for-date-dimensions/
I have also created a separate Time dimension as granularity of an hour is required.
The Time dimension is very simple and only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR).
DimTime(TimeKey, TimeInHours)
Our Fact table will now have a link to both the Date and Time dimension using the PK's.
Our analysis is required by hour, day, week, month and year.
My query is; Will this current structure cause any problems when creating MDX scripts to analyse our data (i.e. drilldown and rollup queries) Hour - Day - Week - Month - Year

Hi Darren,
According to your description, there a day and hour granularity in your fact table, so you want to a hierarchy like Hour - Day - Week - Month - Year, right?
In your scenario, you created a time table that only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR). We cannot create a Hour - Day - Week - Month - Year hierarchy without ant relationship between date table and time table. As per my understanding,
you need create a foreigner key in time table, and join those table in the data source view, then you can create such a hierarchy. Here are some links about create time dimension, please see:
http://www.ssas-info.com/analysis-services-articles/59-time-dimension/1224-date-and-time-dimensions-template
http://www.codeproject.com/Articles/25852/Creating-Time-Dimension-in-Microsoft-Analysis-Serv
Regards,
Charlie Liao
TechNet Community Support

Time Dimension Roll-Up Not Working

Hi Gurus,
We are on BPC NW 7.0 SP04. We are experiencing a strange problem with Time dimension. Even after defining the hierarchy correctly, the values are not being rolled up the hierarchy. Our requirement is to capture data at quarter level and year level. So we have defined the time dimension in following manner:
ID                     EVDESCRIPTION   PARENTH1     LEVEL         YEAR   PERIOD STYLE   MONTHNUM    TYPE   TIMEID           HLEVEL
2007.TOTAL     2007 TOTAL                               YEAR             2007     TOTAL   T3                12                       ACT   20070005        1
2007             2007                   2007.TOTAL   QUARTER     2007     Q1        T2                13                       ACT                        2
2007.Q1             2007 Q1                   2007.TOTAL   QUARTER     2007     Q1        T1                  3                       ACT   20070001        2
2007.Q2             2007 Q2                   2007.TOTAL   QUARTER     2007     Q2        T1                  6                       ACT   20070002        2
2007.Q3             2007 Q3                   2007.TOTAL   QUARTER     2007     Q3        T1                  9                       ACT   20070003        2
2007.Q4             2007 Q4                   2007.TOTAL   QUARTER     2007     Q4        T1                12                       ACT   20070004        2
Here TYPE is a custom dimension property . As the members depict, 2007.TOTAL value should be calculated as the sum of 2007.Q1, 2007.Q2, 2007.Q3 and 2007.Q4 (Quarters and Years are mutually exclusive in our case). But when we maintain data for Q1,Q2,Q3 and Q4, the TOTAL value is displayed as the value of Q4, and not the sum of quarters. We have tried changing MEASURES from PERIODIC to QTD and YTD, with no effect. We thought that it could be a problem with BI, and so built a simple BeX Query on top of the BPC application cube. But in the BEX query, the time dimension is properly aggregated, nd values are displayed correctly. So apparently it is not a problem with BI. In that case, we are missing something in BPC itself. Can any of you identify what it could be? Awaiting answers and Thanking in Advance.
Sincere Regards,
Amitabha

Amitabha,
It's just a problem that a lot of people run into when they are getting used to BPC. Once you see it happen to 10 or 15 people, you can start to recognize it pretty quickly
There are not a lot of examples of this in the Netweaver documentation. I think there are more in the Microsoft docs. However, there is mention of it on this page in the Netweaver documentation: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/65/84d6596224477d80cc8a4392e4c114/frameset.htm]
Ethan

Time Dimension- Wk and Month

Hi,Our user would like to see sales performance by time which rolls up to different hierarchy paths, with measures which use dynamic time series, such as MTD, YTD.TIME1) Year --> Qtr --> Month2) Year --> Week of yearMy question is since I have two different hierachy paths, should I put these time dimensions in one cube. Thus, the cube would contains the following dimensions:TIMEinMonth, TIMEinWeek, Measures, Prod, Geogaphy Or should I build two cubes: one has time dimension as in months, and another has time dimension as in week.It looks like the first alternative has lower space requirements overall, but I can't tag both TIMEinMonth and TIMEinWeek as "Time" dimension in OLAP outline. Can I still have YTD for both time dimensions?What should be the best design?Thanks.Sam

Why don't you try with the two different time hierachies under the same dimension?TIME Dimension: Time --> Year_Month --> Qtr --> Month | --> Year_Week --> Week of year Do not aggregate the Year_Week to the Year_Month and you will have the Year_Month data at Time level! In this way your cube would contains only the following dimensions: TIME, Measures, Prod, Geogaphy.I have used this solution several times, but sincerely I haven't tested too much the Dynamic time series functions with this architecture.

Intra Day Time Dimension

Hi has anyone had any success implementing a Time Dimension which goes down to HOURS granularity?
So I want Year-Month-Day-Hour.
The only way I think I can achieve this is by creating two physical tables, one containing the DATES (DD-MON-YYYY) and the other containing the TIMES (ie. 24 records 1 for each hour).
I can't find a suitable method for getting them into a single OBIEE hierarchy as my requirement also has to OUTER JOIN so that when there is no FACT DETAIL record I still get the Dates/Times displayed.
If I create two seperate Business Model Dimension Tables (and Dimensions) and have a preferred drill path I am able to see the Outer Join Dates, but as soon as I drill into the detail (Hour) I only see a single Hour record (not 24).
Thanks in advance.

Ok cardinal rule broken, replying to my own thread.
I do have a way of doing this, however I haven't volume tested it!
1) Create 2 Phyiscal Tables DATES and TIMES.
2) Create a View on Top called DATE_TIMES_VW which SELECTS date_col, time_col FROM DATES,TIMES and creates a Cartesian Product.
3) Create Physical Model and joins from DATE_TIMES_VW to FACT
4) Create Business Model and complex join (left outer) from Dimension Tab to Fact Tab.
5) Create Dimension from for full hierarchy.
Step 2) is effectively the same as creating one big Timestamp table on the fly, without having to store a large volume of data.
I'm hoping there is a better OBIEE tool method for achieving the same, which would be more scaleable than this one.
Anybody got any suggestions?

'Time' dimension hierarchy Required

Similar Messages

Maybe you are looking for