Setting up time dimension

Hi All,
My time dimension is set up based on the following table.
desc periods
Name Null Type
CALENDAR_DATE NOT NULL DATE
DAY_NAME CHAR(9)
MONTH_NAME CHAR(9)
DAY_NUM NUMBER(2)
WEEK_NUM NUMBER(2)
MONTH_NUM NUMBER(2)
QUARTER_NUM NUMBER(1)
YEAR_NUM NUMBER(4)
PREV_DAY_NUM NUMBER(2)
PREV_WEEK_NUM NUMBER(2)
PREV_MONTH_NUM NUMBER(2)
PREV_QUARTER_NUM NUMBER(1)
PREV_YEAR_NUM NUMBER(4)
I have noticed in may example reports people have their date in the following
MON-YYYY or YYYY-MON
June-2007 or 2007-06
How do I achieve this type of date formatting?
Do I create a new column on this table for each entry?

You can set any data format in Oracle Answers, by clicking the COLUMN PROPERTIES button in the Criteria tab.
A prompt box will be displayed. Then, you can select the DATA FORMAT tab, click the OVERRIDE DEFAULT DATA FORMAT check box and use the desired mask you need.
Hope this helps!
Best regards,
Marcos Spínola

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

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

Advice needed: join fact to time dimension with between clause

Hi All,
I've got 1 dimension and two fact tables. The 1 dimension could serve as a time dimension.(not specifically marked as this is a time dimension)
My Tables look like this (simplified)
Dim1:
date_pk (unique identifier)
date
month
year
fact1:
iid_date (foreign key to date_pk)
fact1_amount
Fact2:
begin_date
end_date
fact2_amount
In the physical layer i have a complex join between fact 1 and dim1 (date_pk = idd_date) and a complex join between fact2 and dim1 (dim1.date between fact2.begin_date and fact2.end_date and dim1.date <= CURRENT_DATE). In the business model i have complex joins between fact1 and dim1 and a complex join between fact2 and dim1 without further specification.
What I would like to achieve in Answers is that I select a Year and a Month from dim1 and add fact1_amount and fact2_amount to the same report and that the report shows both amounts. I would like some advice on how to set this up. Further more how to add a drill from year to month to date and what should I do when I'm willing to add more facts joined to the same Dim1
Any Advice is greatly appreciated
Gilles

Hello MMA1709,
You're right, this setup works!
But...
When you add an hierarchy and mark it as a time dimension it doesn't work anymore. It gives the following error in the consistency checker:
[38086] Physical table Dim1 in the time dimenison table source Dim1 is part of a complex join condition
And that means you cannot use any timebased calculations (AGO and TODATE). When I just create an hierarchy and do not mark it as a time dimension the hierarchy works well.
Any suggestions?

Slicer Time Dimension Issue with Cube Functions

Hi,
Hoping someone can help me figure out right approach here.
Summary:
Using Excel 2013 connected to a SSAS cube as data source, and cube functions with slicers to create a dashboard.
Have following time dimension slicers; Fiscal Year, Fiscal Quarter, Fiscal Month, Fiscal Week & Date, that are used to slice data based on user selection, along
with a sales measure.
Below is example of Slicer name and CubeMember function for each:
Slicer_Fiscal_Year:
=CUBEMEMBER("Cube","[Date].[Fiscal Year].&[2015]")
Slicer_Fiscal_Quarter:
=CUBEMEMBER("Cube","[Date].[Fiscal Quarter].[All]")
Slicer_Fiscal_Month:
=CUBEMEMBER("Cube","[Date].[Fiscal Month].&[201408]")
Slicer_Fiscal_Week:
=CUBEMEMBER("Cube","[Date].[Fiscal Week].&[201509]")
Slicer_Date:
=CUBEMEMBER("Cube","[Date].[Date].[All]")
Problem:
What I am trying to do is to build a table with cube functions that takes the lowest grain of the slicer time dimension selected, shows the current member, plus
the prior 7 so I can have an 8 period trending view table that I will build a chart from. In the above example that would mean that it would look at Slicer_Fiscal_Week since that is lowest grain that has an attribute other than All, and then show me the prior
7 periods. In this case 201509 means Week 9, so I would want to show in table Week 9 back to Week 2. But if Slicer_Fiscal_Week was set to All, along with Slicer_Date, then Fiscal Month would be lowest grain, so I would want to show Fiscal Months from August
(201408) back to January 2014. I know how to use CubeRankedMember to pull the value from what is selected in the slicer, the problem is figuring out how to pass the lowest grain time dimension so that I can use lag or some other MDX function to get the previous
periods.
Any help on this would be greatly appreciated.
<object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{28593A5C-70C0-4593-9764-80C76B51795C}"
/></object>

Hello,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Multiple Fiscal Calendars Displayed in Subject Area Time Dimension

Hi all,
Thanks for taking the time to review my post.
Environment
Oracle BI Applications 7.9.6 Financial Analytics
Oracle E-Business Suite 11.5.10
Query
The Time dimension on my Subject Areas (Financial Analytics) are showing more period data than I expected.
I have configured one Enterprise Calendar (WPG_Calendar) that I set in the DAC parameters - $$GBL_CALENDAR_ID (WPG_Calendar~Month) and $$GBL_DATASOURCE_NUM_ID (4). The warehouse Enterprise Calendar table W_ENT_PERIOD_D is populating with the periods as configured in EBS for that calendar(Jan-09, Feb-0, Mar-09, etc). I noticed that the Multiple Fiscal W_MCAL_PERIOD_D table is also been populated with the Enterprise Calendar data PLUS, the Seeded EBS calendar (JEBE_MONTH_VAT) and a generated Calendar that appears to be a 5-4-5-4 Calendar (Jan-01-09, Jan-02-09, Jan-03-09, etc). The trouble is these W_MCAL_PERIOD_D periods and dates are all coming through in my Time dimensions and make it confusing for the Answers Users when choosing a Time dimension.
Also, for columns W_CURRENT_MCAL_PERIOD_CODE, W_CURRENT_MCAL_QTR_CODE, W_CURRENT_MCAL_YEAR_CODE there are rows with Current, Previous and Next populated that span these different periods as you would expect, but I'm concerned these return multiple rows for Filters Current Fiscal Quater, Current Fiscal Year.
Funnily enough, W_CURRENT_MCAL_MONTH_CODE has nothing populated (NULLs for all rows).
Your comments are most welcome.
Kind Regards,
Gary.

The filtering of the calendar can be done directly on the logical layer.
for the logical dimension "Dim - Date Fiscal Calendar", Logical Table Source "Dim_W_MCAL_PERIOD_D_Fiscal_Period"
set the content as :
"Oracle Data Warehouse".Catalog.dbo.Dim_W_MCAL_PERIOD_D_Fiscal_Period.MCAL_CAL_WID = VALUEOF("MY_MCAL_WID")
and setup the repository variable MY_MCAL_WID to match with your calendar wid.
If your calendar depends on any context then you can use session variable instead of repository variable

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

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

Time Dimension - Additional Attributes..

Hi
We are building a Financial Services BI Applications. In one of my Cube, for Time Dimension, i need to add more attributes like
for Month Level i need the following
a) End Date of the Month
b) No of Days in the Month
at Quarter Level
a) End Date of the Quarter
b) No of Days at the Quarter
and likewise.
I can do this in AWs using attributes, however in essbase since i have to tag the TIME dimension as DENSE, it is not allowing me to create any attributes. Has somebody solved this problem in the past. Please help.
Thanks
bala

Any more recommendations please..
I cannot use UDAs as it expects that the consumer of the UDA knows the value set.
i.e. in Time Dimension assume the leaf is
200701 (UDA 31)
I would want something like this
if provided 200701 then the server should return 31 as the number of days.. However if i use UDA then i can only check (if @UDA(200701) = 31) then
here it assumes that i know the attribute value before hand which i would not know..
Please help as we are reaching a critical stage in our project
Thanks
bala

Disable grid spread on time dimension

Hello,
Is it possible to disable grid spreading on time dimension? I've tried to unflag "Enable Grid Spread" in form properties but nothing happens.
Input data in Quarters are spread on Months, and input data in Months is added on Quarters..
I'm using Hyperion Planning v11.1.2.1
This thing is driving me crazy.
thank you,
Daniele

Hi Daniele
Make sure the Time Balance property of your period members is not set to fill or flow.
Regards,
Robb Salzmann

Problem with time dimension aggregation

I have a time dimension with 2 columns:Year and week
I've created a hierarchy in it to drill down from the year to the week.
when I report the sales in week level I have the right values but when I report the sales value in year level I don't have the right aggregation.Even if the year Level is a grand Total in the hierarchy.
The problem is that for all the years I have the same value but when I add the week level to the report Then I have the right values.
What could be the problem

Hi,
1.Actually the drill down Route path is not properly generated with your given key columns in herarchies.
need to give correct key columns
like year(YYYY)-->Week(wee should be the unique column for each and evry year)
suppose:
2000-sunday
2001-sunday should be different
so mostly the problem at your week column make the unique yearweek column as the key identifier at that level
Every Week is unique cause the logical key is a combination of the year and the weeknumber
2.if not you need to set individual levels for measures in content tab...
you mean by the content tab the level tab when you doubleclick into the measure???
Thanks

Problem with Time Dimension generating

Hello, everybody.
I have a problem with Time Dimension generating with the help of the Standard Wizard.
1. I choose Dimensions -> New -> Using Time Wizard
2. Set Name as "Time"
3. On the next screen I choose ROLAP: Relational Storage
4. On the next screen set Start year: 2003, Number of years: 3
5. On the next screen choose all levels of the Normal Hierarchy
On the 6-th step Wizard complete 60% of job and hang up doing nothing (buttons "Cancel" and "Help" is active).
chapter "Create REL_TIME Dimension Using the TIME Dimension Wizard", step 1-6 of tutorial =(
http://www.oracle.com/technology/obe/11gr1_owb/owb11g_update_getting_started_intro/lesson3/less3_relational.htm
My system characteristics:
Builder client 11.1.0.7.0, warehouse at local computer.
can anybody give me any advice about this problem? =(
thanks in advance.

Had this issue been solved please?
I have just come across the exact same problem and this post is the only one i managed to find which describes exactly what is happening to me.
Thanks

How to build dynamic time series for the time dimension

I am planning to build dynamic time series using rule file instead of manually.Please let me know if there is any property need to assign to enable DTS property for TIME dimension.
Edited by: 844104 on Mar 14, 2011 3:37 AM

In the load rule in the dimension build settings you would need to go to the tab dimension definition, choose the time dimension and right click on it. Select Edit properties. If you have not done so, set the dimension to be the time dimension. Then go to the generations/levels tab and set the generation names you need. For example if you want YTD, you would set the generation name to Year, if you want QTD set it to Quarter. You would set the number to the generation number that coorisponds to the generation. The DBAG has the list of names for all of the DTS members.

Time dimension in French

Can anyone tell me how to obtain a french dimension from the dimension wizard. Using OWB 10.2.0.36, repository 10.2.0.4, oracle database 10.2 R2. Everything is set to ca_FR(canadian french), the gui for OWB is in french but when I create a time dimension the columns namaes are in english (that is not the problem since Ican change them) but the results are also in english, like the days and months names. If i do «select wb_day_name(sysdate) from dual;» in my target schema the result are in french though. What am I missing here, can anyone help.
Many thanks

Hi Oleg
Here they are
NAME TYPE VALUE
nls_calendar string
nls_comp string
nls_currency string
nls_date_format string
nls_date_language string
nls_dual_currency string
nls_iso_currency string
nls_language string FRENCH
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
NAME TYPE VALUE
nls_sort string
nls_territory string AMERICA
nls_time_format string
nls_timestamp_format string
nls_timestamp_tz_format string
nls_time_tz_format string
but I think I found why, need to set nls_date_language to french and it worked
Thanks a lot

Time Dimension displays End_Date instead of Long_Description in Analysis

I am importing an analytical workspace into a BI repository. At first I was doing it by exporting it from AWM (wherein it was built) with its Export to OBIEE plugin--doing this resulted in the Time dimension properly displaying its Long Description field in an analysis in BI.
Now I am trying to import it into BI following the instructions in the Oracle Business Intelligence 11g Developer's Guide (pg. 315 - pg.324). However, instead of displaying the Long Description field in an analysis, it displays the End Date field for all Time Levels. Is there something in the Admin Tool that sets what to display for a given Level?

Okay, I finally stumbled on the answer.
Under the Presentation Layer -> Time Dimension -> Time Hierarchy, I needed to double-click on every Level and go to the Display Columns tab and increment Long Description to the top in order for it to display the Long Description.

Setting up time dimension

Similar Messages

Maybe you are looking for