Essbase/OLAP Time Dimension in OBIEE

I am on OBIEE 11g release. After exported the below essbase time dimension with dynamic time series thru the Administration tool
Time
|_ Spring
|_ Q1
     |_Feb
          |_FebW1
     |_FebW1D1
          |_ .....
          |_FebW1D7
|_FebW2
     |_Mar
     |_...
     |_ Q2
     |_....
|_Fall
Of course OBIEE converted, OB converted the time into
Time
Year
Season
Quarter
Month
Week
Gen6
Drag the Time hierarchy from physical layer to Logical layer and to presentation layer.
However, when try to see the time hierarchy in Answer by drill down on the hierarchy from Year, it only shows spring but not fall, and drill from spring
I can only see Q1 etc .....
Is there a setup I need to done ?
Thanks

Answer not display hierarch when there is no data assoicated.

Similar Messages

Setting up a TIME dimension in OBIEE

Hi,
We have an Oracle OLAP Cube built using AWM v10.2.0.3A. We have also created a relational view for this cube (using the OLAP view generator) and are now using this view as a data source in OBIEE v.10.1.3.3.2.
As part of defining the Time dimension in the Business Model Layer of OBIEE repository, we have done all the relevant mappings to the TIME dimension as in the AWM Cube and have marked the dimension as type 'TIME'. Also, for the TIME logical table, we have defined each level (All Years, Year, Month, Quarter, and Day) to have its own chronological key with unique values at all levels. The primary key for our TIME table in the business layer is 'Day'. This level 'Day' is mapped to TIME_DAY_LVLDSC column of the relational view created over the AWM cube. The data type for this column is "VARCHAR". (We basically picked up all the 'Description' columns while creating the view over the cube!)
With this background of the TIME dimension structure, here is the problem scenario:
When we try to create a report with one AGO and one TODATE function defined over the "Day" level (both are defined as logical columns), then the report takes forever to run and never comes back with any data/error even for a handful of rows. We are seeking the forum's help on the following:
1. Is it necessary for the primary key 'Day' of the TIME logical table to be of type DATE? If yes, does this mean that we have to change the column data type in our cube (or select a 'date' type column to be a part of the view and then redo the mapping in the repository) or do we just make a change to the column data type in the physical layer of OBIEE repository?
2. Going by the description above, is there something missing (other than point 1. above) in the setup of the TIME dimension in OBIEE so as to make it usable for Time Series type of calculations/functions?
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Wildmight,
Thanks a lot for your kind inputs.
1. No, VARCHAR is fine. You should have also defined unique time keys in your time dimension (Quarter Year, Month Year) and check box 'time dimension' in the properties of your time dimension.
-->> The Time dimension that we have defined in the Business layer of the repository is mapped to the respective level columns in the AWM cube and has already got unique members at each level. We are using the "Description (LVLDSC)" columns for each level and have defined the "Description" column to have unique values at each level. A sample data set looks like :
Year:
2007
2008
Quarter:
QUARTER1 2007
QUARTER2 2007
QUARTER1 2008
QUARTER2 2008
Month:
JANUARY 2007
FEBRUARY 2007
JANUARY 2008
FEBRUARY 2008
Day:
Monday, January 1st 2007
Tuesday, January 2nd 2007
So in the above case, do we still need to define a unique key for each level like Quarter Year, Month Quarter, etc.? (Please note that the check box for 'TIME' dimension is checked !)
2. Is your AGO based on TODATE? or your TODATE based on AGO?
-->> I am not sure what this really means - however I can tell you that we have created two new logical columns (in the fact table in Business Layer) : one to show the measure as TODATE for Day level, and the other to show the measure as Day Ago.
So it means that we are trying to create two reports with three columns as below:
- Day Measure on Day Measure Todate (Day)
- Day Measure on Day Measure Day Ago (Day, 1)
I hope I have been able to clarify the problem scenario with this. Does this setup seem correct to you?
Many thanks for your help.
Best Regards,
Piyush

OLAP time dimension - how are the weeks allocated

Could someone please help me understand what logic Oracle uses when one makes use of Oracles OLAP time dimension based on weeks.
I am use Oracle OLAP 11.2
I have a Time dimension that has the following hierarchy:-
YEAR
QUARTER
MONTH
WEEK
For calculating the weeks ID I make use ISO week and year i.e. IYYYIW
For calculating the end date I use the following:- NEXT_DAY( l_date, 'MON' ) -1
i.e. the weeks end date is the Sunday.
According to me this is the required result.
Problem is that for some months there are 3 weeks allocated which makes no sense to me.
I cannot understand the logic used in allocating the weeks.
The following is an example:-
the following weeks were allocated to the month February
201306 (end date= 10-2-2013)
201307 (end date= 17-2-2013)
201308 (end date= 24-2-2013)
but the following week was allocated to January which makes no sence to me,
I would have expected it to be found in February
201305 (end date= 3-2-2013)
Week 201309 (end date= 3-3-2013) was allocated to March which according to me is correct..
Another example is week *201030 (end date= 1-8-2010)* that is allocated to July while I would have expected that it should be August.
I would have thought that it uses the end date that is placed in the mapping to determine the month to place it in.
Could some one please explain what the reason for this could be.

Oracle OLAP model/design (in this case, at least) cannot compensate to coverup existing flaws in the relational model/design.
I dont think this is a valid hierarchy even considering relational model/design.
Weeks do not fit in below Months (calendar months).
You can force fit them by making Weeks the source of truth and making all Months logical Months like "Business Month", "Business Quarter", "Business Year" etc. which will be composed of whole weeks but differ significantly from the calendar definition of Month, Quarter, Year etc.
You are better off modeling time as composed of two hierarchies:
H1: DAY -> MONTH -> QUARTER -> YEAR and
H2: DAY -> WEEK
Alternately if you dont want to introduce DAY level (lower granularity), you can split up the Time dimension into 2 different dimensions. And also modify your star schema to add an additional time dimension key to fact table - one key pointing to WEEK and another pointing to MONTH (independently).
TIME_MO: MONTH -> QUARTER -> YEAR
TIME_WK: WEEK
The fact data will need to be split up to correctly identify the coirrect MONTH-WEEK combination for the relational record.
E.g:
Fact table should have 2 dimension Fks for WK_KEY as well as MO_KEY so that a fact figure of 1000 evaluated over 7 days is split up into 300 from 29-31st of previous month and attached to MO_KEY of previous month and another record of 700 covering days from 1-4 and recorded/tied to same WK_KEY but next month (next month's MO_KEY).
HTH
Shankar

Time Dimension in OBIEE

Hi all,
I have an essbase cube with 2 dimensions related to time.
Year and Time (that contains Qtr, Months and days).
I'm working with OBIEE and would like to know if I can create 1 Time dimension that combines Year and Time so I can have:
2010
- QTR1
-- Jan
-- Feb
-- Mar
2011
- QTR1
-- Jan
-- Feb
-- Mar
I read the OBIEE tutorials but it doesn't show how to do this. May be is not possible?
Thanks

Hi
One cannot modify the cube dimensions from OBIEE. Also, even in OBIEE, you get the data for the intersection of at least one member from each dimension. Which looks like:
Year Time Time
2010 QTR1 Jan, Feb, Mar
2011 QTR1 Jan, Feb, Mar
But, you can use some options like 'hide column' etc in order not to show a particular dimension(s) in the report.
Regards
Vikas

Oracle 9i OLAP Time Dimension

I have got a problem with my cube in Oracle 9i R2 OLAP Services.
I would like to create time dimension with hour level. But, time type have
only day level.How I can create dimension with hour level ?
user cwm2 or OWB

Hi Jiaxu,
Are u a Chinese?
I find that you are learning OracleR2 OLAP.
I just take a project about OracleR2 OLAP.
Could we talk about the technology?
My mail is [email protected]
Best Regards
Chen Qizhuan

Time dimension - not ordered

Hello,
I'm new on OLAP Cubes,
I've made one that works well instead of the fact that my time dimension is not sorted : dates are not in order.
I've tried to sort dates before the cube, in the views. but even if when i see time attribute sorted in my view my cube time dimension stays unsorted.
I'm working with AWM 10g
please help !

You can always use the time_end_date attribute to sort the results of the query. When you say that the time dimension values are not sorted? what do you mean .... is the hierarchy correct ... all nn-JAN-yyyy records under JAN-YYYY or is it also mixed up due to the improper sorting? If the hierarchy is alright.. you may need to
Can you provide more details... perhaps all details relating to db view/table - structure (table/view, columns, datatype, size etc) and sample data (few rows) as well as how the data appears in the olap time dimension when viewed through AWM results. Whats loaded (all of the records but sorted improperly or if only some of them => what're the records which dont get loaded?)
Also noticed that you used the term olap cube time dimension.. the time dimension is not exactly an independent component of the cube, its used by the cube. Its defined in the AW and exists only as a dimension (independent of any/all cubes). The cube only references it.
Another reason for mismatch (not very likely though) could be that you have time end date data in your view as a varchar field instead of a date and is interpreted wrongly while its being loaded as a date datatype attribute by the AW dimension load program. Depending on your NLS settings (and thereby the default date format), the date string is interpreted as a inappropriate date. You usually encounter errors during such a load ... day #13 interpreted as month #13 (invalid) as a result of a mismatch of date format settings.
HTH

Month Sort Order Problem in Time Dimension(Essbase with Obiee)?

Hi All,
I am facing issue with month order in answers.
First I created BSO cube using Essbase Studio. When i exposed cube in answers, months were sorted in alphabetical order. So i used RANK function with evaluate to arrange month members in proper order. But if i use RANK function it pulls all missing records and it is effecting performance.
Then i created Time dimension(dimension loading) in essbase from FLAT file,initially it was coming in proper order. But after some time again it sorted in alphabetical order!!!
I have seen in internate few people saying they didn't face this problem. I
Please advice...
Essbase: 11.1.1.3
OBIEE: 10.1.3.4.1
RS

Hi user10300020,
That's a fairly common problem with months that happens regardless of database source.
In the logical layer of OBIEE you can specify the sort order on the month name column. Just double click on the month name column and look for the option to set sort order based on a different column. I typically sort the month name based on the month number.
Give that a shot and tell me if it works.
-Joe

How to build the time dimension in Essbase with Fiscal Year (July thru Jun)

Hi,
In a recent project i have a situation where i need the time dimension to have some thing like this Fiscal Year (July - June) using BSO need to achieve DTS (YTD and QTD) functionality also.
And also my reports should also be able to drill through and needs comparison years(Prev Year Vs Current Year), months(Prev Year Vs Current Year) and Qtrs(Prev Year Vs Current Year).
How can i achieve this using BSO?.

Hi there,
This forum is for Oracle OLAP. The Essbase forum can be found here:- Essbase
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

OBIEE Evaluate - "Essbase error : Repeated dimension in MDX query"

Hi,
I'm using OBIEE 11.1.1.6.2 BP1 on top of Essbase.
I have a project dimension in Essbase with three levels - Total Project -> Project Class -> Project. I have created a new logical column in OBIEE to query two levels from project dimension, using evaluate function as below:
Evaluate('%1.Members, %2.Members', "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen2,Project" , "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen4,Project" ).
The above column when used in analysis, works fine, returning "Total Project" and all the projects. It breaks however when any filter is applied on project dimension with the following error:
"[nQSError: 96002] Essbase Error: Repeated dimension [Project] in MDX query".
I donot have any MDX skills and would appreciate if anyone can explain this error and provide any workaround for this. Here's the MDX that fails:
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])
Many Thanks

This issue regarding BIEE
because MDX is wrong
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])

Problem with drill down in time dimension - OBIEE 11G

Hello There,
I have a problem with drill down in time dimension. The hierarchy for time dimension is " Fiscal Year---> Fiscal Quarter---> Month(Name)--->Date". When I select a Time dimension and click results its getting opened in a Pivot table view. The problem here is, when I click the "Total" its getting drilled down to Year ---> Quarter but when I click on "+ sign next to quarter" it should drill down to month for that particular quarter for that particular year but its drilling down to month for that particular quarter for all years.
Any suggestions are much appreciated.
Thanks,
Harry.

1.) Congrats for resurrecting a year-old thread.
2.) Your answer is here: "Check the level key of the quarter level...it should include both quarter and year columns. Since a specific quarter occurs every year, quarter column alone can't be used as the level key."

Time Dimension not loaded correctly when imported to 10.2.0.3 database

Dear All,
I created a Time dimension using the wizard that contian both Normal and Fiscal hierarchies on a repository created on 10.2.0.1 DBMS
I exported the poject in mdl and imported it in repository on 10.2.0.3 DBMS ... the Time dimension in the new poject wasn't loaded correctly
the Rows of the Day level contain information about the upper fiscal levels' columns while the columns of the normal hierarchy containd null
Can you help me to solve this problem ???? !!!!!...
Best of regards,
Shaimaa

Your quote comes from the OBIEE Plug-in user guide (http://www.oracle.com/technetwork/database/options/olap/awm-plugin-user-guide-for-obiee10g-303148.pdf)
So, yes, you can only use this if you are using database 11.1.0.7 or later and if you are creating an 11g style AW.
You can map 10g style AWs to OBIEE, but it is a manual and complex task. You would need to start by generating views using (for example) the OLAP View Generator (10.2.0.3) available on http://www.oracle.com/technetwork/database/options/olap/olap-downloads-098860.html . After this you would need to manually create the mapping metadata in OBIEE.

Creating Time Dimension from date columns in fact tables.

I remember watching a demo from a BI Tool a couple years ago, wich I swear was OBIEE, and the presentator stated it was possible to create a Time Dimension in the admin tool, based on a date column in other table.
Can you guys tell me if there's such functionality in OBIEE?
If so, how could I achieve that?!
Thanks in advance!
Marcos

hi,
You are trying to make Fact table as Dim table ???
Fact table has some dim columns??
We can do this by making a fact table as dim table ,create a dim hierarchy on that table
Year level :Extract(year from fact_date_column)
Month and year level:CAST (Extract(month from fact_date_column) As CHAR(5) ) || CAST (Extract(yearfrom fact_date_column) As CHAR(5) )
Like this
But,be careful while doing this make sure that all joins and content levels are good
As per my knowledge this is not a good way,Experts can add some words lets see!!!!!! :-)
thanks,
saichand.v

Time Dimensions and Logical dimension "..that not join to any fact source"

Hi Guys,
I get the following error on the ANSWERS front end:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: ToDate(SPECIFICG:[DAggr(RFACT.SPECIFIC [ ] by [ EFact.NO [ ] , Year.ID [ ] ] )], [Level Years]). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT EFact.NO saw_0, Fact.YTD_E saw_1, EFact.MTD_E saw_2 FROM "E#1" ORDER BY saw_0
The consistency manager shows no errors and the tables are physically joined up via foreign key i.e.
fact year monthday
data - date - date
year month
day
[see screen print|www.metallon.org/test/foreign.jpg]
I would be thankfull for any suggestions!

Hello wildmight.
I followed this tutorial:
http://www.rittmanmead.com/2007/04/30/obi-ee-time-dimensions-and-time-series-calculations/
Why should this layout not work?
Do you have a better idea?
When you say "it has to be one table" do you mean
that quartermonthday and year need to be ONE?
I just rememered that Oracle Hyperion Planning has to have
time and months seperated.
Hello mod100.
What do you mean hierachy over the time dimension?
Is it not obvious from the screen print that I have a hierachy
i.e. yeartotal - years and
quarters - months- days.
I read that by default the LEVELS are set to the lowerst. so thats fine. I set them by myself to the lowest as well but the ERROR is still the same.
no, I have not set the levels as in
http://obiee-tips.blogspot.com/2009/10/logical-levels.html

Setting date ranges when Time dimension includes Period instead of Month

I hope I am missing something simple here - we are on OBIEE 10g, and I have a Time dimension defined as follows:
Year > Quarter > Period > Week > Day
A "period" is not equivalent to a calendar month - a period can include either 4 or 5 weeks, and always starts on a Sunday. Fiscal years start on the first Sunday in July.
I need to create a graph that shows Total Sales for the previous 13 periods (not including the current period). This needs to be a rolling 13 periods based on the current period.
Since this is Period and not Month, I am unable to use the Month(CURRENT_DATE) functionality. Do I need to have repository variables defined for the current period? Is there another way to calculate what the current Period in my Time dimension is in a filter SQL?
So I want to do something like "Where period between [current_period - 14] and [current_period -1] as the filter for Period.
Thanks in advance for any assistance.
Rhonda

Sorry about that...
Periods are 1-12 (numeric).
Period 4 of FY 2012 for example has a begin date of 10/02/2011 and end date of 11/05/2011.
Right now we do not have unique combos created (like 4/2012, 5/2012, etc) so to get a unique value I have to specify both a year and period.
So on my dashboard today I will need to create a graph that covers FY2011 periods 6-12 and FY2012 periods 1-6 (translates to 12/5/2010 - 12/31/2011).
I haven't created repository variables before, but as the Period parameter will be used often I guess I will find out how.
Thanks in advance for the help.
Rhonda

TIME dimension processing fails saying "..attribute key cannot be found.." in EPM 10

After upgrading from version 7.5 to EPM 10, when we ran a ‘Full Process’ on the TIME dimension, it ran into an error saying “Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactCapEx', Column: 'TIMEID', Value: '20090013'. The attribute is 'Time_TIMEID'. (1/13/2015 2:41:02 PM)”.
Full error message is attached herewith – ‘Time Dimension Error.txt’
After researching, we did discover that MONTHNUM needed to be converted to BASE_PERIOD. Re-processed which produced the same error.
Prior to migration to version 7.5, we ran a full process on TIME dimension there. It completed successfully, confirming the issue is only with version 10.
Confirmed we could see the TIMEID value of 20090013 in the following places:
Time Dimension in the appropriate TIMEID attribute column.
Confirmed mbrTIME table had base member ID with TIMEID attribute filled out correctly.
Data in tblFactFINANCE could be pulled using that TIMEID
We truncated all the records in all the fact tables associated to this TIME dimension.
Eventually, when none of the tables had any records, the TIME dimension then processed successfully.
We this began to suspect the issue may not really be related to bad records.
We conducted one more test to confirm this.
Using an input form in EPM 10, we manually entered data in one of the models (at this point none of the fact tables have any records)
Ran Full Optimize on that model with Compress Database and Index Defragmentation checked – This step failed with the error attached in ‘MatrixRateFullOptimize.txt’
Ran Full process on Time Dimension – Failed indicating issue with TimeID 2012001 (that’s my manual entry). Attached error report ‘TimeDim Error MatrixRate.txt’
At this point, the table only contains the manually entered records (no suspected bad records)
We then suspected there could have been an issue with the upgrade process.
So we reprocessed all the dimension and optimized all the models in version 7.5, made a new backup and restored it to version 10.
The issue still persisted!
At this point, we have tried all the possibilities we could think of. Each time the fact table is populated with records, the TIME dimension process fails indicating ‘the attribute key’ cannot be found.
There is probably something in the OLAP partition that is not able to link the dimension attributes to the cubes.
Additional Information:
Please find attached the existing Time Dimension – TimeDimensionMembers.xlxs
Version of Excel used: Excel 2007, SP3 MSO (12.0.6683.5000)
System Specs: Please see screenshot below.

Thank you all for responding! This issue is resolved.
Here’s what the issue was:
The time structure is TOTAL >> Years >> Quarters >> Months (e.g. T.ALL >> 2012.TOTAL >> 2012.Q1 >> 2012.P01)
As shown in the screenshot below, the LEVEL for ‘T.ALL’ member was set to YEAR, which is incorrect (we can’t have Year rolling up to a Year)
We changed the LEVEL to ‘TOTAL’ and this fixed the issue!!
If only it gave a better error message than the “..attribute key not found” message

Essbase/OLAP Time Dimension in OBIEE

Similar Messages

Maybe you are looking for