Time Dimension and database 8.1.7.3

Hi,
I imported owb_bp project that is located in: <OWB install directory>\owb\misc\time directory into my OWB. Then i copied the standard time dimension and mapping from that project to my project. I changed the necesary things(removed day level, did reconcile inbound on a dimension in a mapping with "match by bound name" strategy) in the dimension and mapping and when i tried to deploy the mapping i got an error:
VLD-3268: A mapping can be deployed only if the database version is Oracle 9.2 or higher.
Is it true that you need Oracle 9.2 or higher for deploying this kind of time dimension. If that is so, how can i create a time dimension that is going to work with Oracle 8.1.7.3
Thx

Thanks for your answer Igor.
The problem is that we cant upgrade our database to 9.2, becouse our customers dont use it, so we are stuck with 8.1.7.3, which by the looks of things doesnt support a lot of things in OWB 9.04.
So I would really appreciate it if someone could give me some pointers as to how to generate data for time dimension, thats going to work on database 8.1.7.3.
Thanks you all for your time.

Similar Messages

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 and 1h periods

Hi All,
1. I'm new to OWB and I was wondering is there any chance to force default (made using wizard) time dimension to have 'smaller' level then one day (let's say 1h) ?
If not, have you tried to manually update the dimension & mapping ?
Or it is better to leave default dimension and start with my own time dim ?
2. What's the difference between dimension created as 'time' dimension and dimension with similar content but defined as typicall dim ? (any performance/analysis issues?)
Thanks in advance.
Cheers,
B

Hi Carsten,
Thanks for reply.
Carsten Herbe wrote:
Have you considered using a date dimension on day level and a second time dimesion containing only the hours 1-24?It seems to be a good idea. I'll try this.
Using the wizard does make live easier, but there is no performance advantage compared to a normal dimension. Great. Wizard's time dimension contains much more fields then I'd suspect thus I want to avoid situation when I make simple time dim at the begining and after some time I find out that there' s something important missing ;)
Thanks for help.
Cheers,
B.

Time dimension and chronological key

HI ALL
I WORK ON OBIEE 11G REPORTS
WHAT IS THE EXACT USE OF TIME CHECK BOX AND CHRONOLOGICAL KEY??
AND HOW CAN I USE IT
ANY HELP ??

Hi,
What is the chronological key use?
A. Typically time dimension differs from all other dimensions in one way and that is,
all other dimensions dont care about the order of the values in it.
e.g. in region_dim the values are north, south, west and east. Here nobody wants to see whether north comes first or south comes first. i.e. no order is required here.
in the case of time dimension there needs to be a particular order for all the values present in it.
e.g. 2010 is earliest and 2004 is older. Dec-10 is earliest and jan-10 is older. i.e. the values in the time dimensiion needs to follow a particular sorting order. So the chronological key is the key which tells the obiee that the data is incrementing based on the chronological column.
Here you may get another doubt. i.e. you are having columns like year, half_year, quarter, month, week and day. Here which one should become the chronolgocial key?
Analyse it yourself. If you kept year as chro key then obiee will be confused whether jan-10 is earliest or feb-10 is earliest. Because it knows only that 2010 is earliest and 2009 is older.
So always it should be the lowest level oif the dimension which needs to be the chronological key. In the abouve case it should be date.
You can select either date or date_id(this could be a sequence generator values).
2. what is the use time dimension?
A.If all you want is to achieve drills from Month, Quarter and Year then treat it as a normal dimension and create the levels. But if you want to do calculations like YTD, QTD and MTD then you need to create a time dimension.
http://oraclebizint.wordpress.com/2007/11/05/oracle-bi-ee-101332-understanding-todate-and-ago-achieving-ytd-qtd-and-mtd/
Refer the above link for time dimension.
Award points it is useful.
Thanks
satya
Edited by: Satya Ranki Reddy on May 2, 2012 12:29 AM

Difference between Time dimension and product(regular) dimenstion

Hi All,
I would like to know what is the difference between time dimenstiona and regular dimenstion. How can we differentiate and how Oracle bi server knows a dimension
as Time dimenstion.
Thanks,

Hi,
By using Logical Dimensional Structure and chronological keys it identify time or other types of dim.
Just double clik time dimension then you can find the
root type (Time, Ragged and skipped) and for the chronological keys > just double click logical level then select keys tab -- here u can find chronological keys
Thanks
Deva

Performance Point Filter Scorecard by Time Dimension (without Time Intelligence)

Hello,
I use Performance Point 2010 and want to build a Performance Point Dashboard with Scorecard. My requirement is to provide a List of Years as a Filter for a Scorecard.
In the Scorecard I have a KPI which I want filter by Time Dimension. I can do this when I use "Time Intelligence" and "Time Intelligence Connection". But I want to use the "Member Selection Filter" to filter the Scorecard
KPIs by Years (Selected from a List).
I created a "Member Selection Filter" with certain Time Dimension and put Filter to a Dashboard. In my KPI Mapping Source I added a "new Dimension Filter" and choosed the same Time Dimension as
in the "Member Selection Filter".
When I try to connect the "Member Selection Filter" to my Scorecard, I can only choose the "Curent Date Time". As I know "Current Date Time" have to be used when Time Intelligence Filter is in use.
How I have to connect the Scorecard with the "Member Selection Filter"?
Thank you very much

Hi ShebUK,
I don't think we can achieve this requirement on the front end, but you can discuss this issue at the following forum:
http://social.technet.microsoft.com/Forums/en-US/home?category=performancepointserver
I'm not familiar with PerformancePoint Services and not sure that we can implement linked dimension to achieve this. A linked dimension is one that exists in one Analysis Services database, but reused in another Analysis Services database of the same version
and compatibility level. For more information, please see:
Define Linked Dimensions: http://msdn.microsoft.com/en-us/library/ms175648.aspx
Hope this helps.
Regards,
Elvis Long
TechNet Community Support

Time Dimension

I have created a Time dimension using the Dimension Wizard with two hierarchies:
Year - Quarter - Month - Date
Year - Week - Date
We have a data warehouse with two fact tables, FactSite and FactWell.
Each table contains a different date field and we hope to use the Time dimension as a role playing dimension for each.
So we wish to filter FactSite and FactWell data by
Year - Quarter - Month - Week - Date using
the operational date fields.
My queries are. Must we now:
1 - Populate (using wizard) the Time dimension with a suitable date range? (i.e. the start date and expected end date of our data set).
Then during our ETL process, we do a lookup in the Time dimension and set the surrogate key in the corresponding fact table.
2 - Populate the Time dimension during the
ETL process from our OLTP data source?
3 - What is the best practice for this type of scenario?

Hi Darren,
According to your description, you need a time table to create your time dimension, now you want to know which is better, creating the time table in the project or creating the table in the OLTP data source during ETL process, right?
Microsoft SQL Server Analysis Services provide a convenient way to create time table, you can use the Dimension Wizard in SQL Server Data Tools (SSDT) to create a time dimension when no time table is available in the source database. As per my understanding,
it better to generate the time table in data source view using wizard. Please refer to the link below to see the details.
http://msdn.microsoft.com/en-us/library/ms174832.aspx
Then you can create a Date hierarchy Year - Quarter - Month - Week - Date using this time table.
http://msdn.microsoft.com/en-IN/library/hh231692.aspx
Regards,
Charlie Liao
TechNet Community Support

Fiscal Year Time Dimension - Month Time Span

I have a need to create a fiscal year time dimension and I created using Time Wizard in OWB. When I was developing BI Reports, I found some inconsistencies in Time dimension as it was showing figures in all the months of my first quarter of new financial year that Apr 2009 – Mar 2010. On close inspection of Time Dimension table I found that fiscal_month_time_span value varies from 35 to 28 to 29 for different months. i.e. it’s not matching with corresponding Calendar month. This means I am unable to plot data correctly using fiscal year dimension.
Maybe this is how it works in Oracle, but this does not solve my problem. Could anyone give me some solution for this ? My Fiscal year is from ‘1- Apr – 09’ to ’31-Mar-10’. In my reports I would like to see transactions for April month when I use month attribute of time dimension like it happens in Calendar time dimension.

May be someone from
Forum: Business Intelligence Suite Enterprise Edition can answer this .
Please post it there.

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

Modifying Existing Time Dimension

Hi All,
Presently I have a Time Dimension and a Fact table which has a FK to this Dimension. The Time Dim has a level upto hourly values.
Now it's in production and I need to change the Time Dim to take on minutes 'cause some reports need minutes.
1. So what is the best way to go about this?
2. Is it better just to add another extra field which has the required date, in the fact table?
3. How can the existing data be easily ported to the new Time Dim(if it has a minute-level)?
Thanks,
Justin.

I am wondering how you implemented the time dimension which only has a level up to hourly values. Do you mean the time dimension only has 24+1 = 25 rows? Usually the time dimension is separate from the date dimension and its lowest level values are minutes or seconds, depending on the business requirements. Therefore the time dimension should have 24X60 + 1 or 24X60X60 +1 rows.
The solution is depended on what you want.
My suggestion is as the follows:
1.     Create a new time dimension with the desired lowest level values (minutes or seconds).
2.     Create or modify the foreign key of the fact table to point the new created time dimension.
3.     Modify the ETL mappings.
4.     Option 1: If you want the new functionality available for the existing rows in the fact, you have to reload the fact no matter which approach you use.
Option 2: If you only want the new functionality available for the subsequent refresh load, you can modify the foreign-key values pointing to the old time dimension to the new time dimension, using the rule XX --> XX:00 or XX --> XX:00:00 (where XX is the hour number in the old dimension). In the subsequent refresh load, map the foreign-key values to the actual time.
Maybe other else can provide better solutions. IF so, please let me know.
Good luck!

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."

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_DSO_1 attribute in Time Dimension

Hi,
We are using Oracle Analytic Workspace Manager version 10.2.0.3.0A for creating a cube.
We have defined a dimension as "Time" dimension and have also specified the dimension type as "Time".
This dimension has the levels: Year, Quarter, Month, Week and Day. These levels are for the one and only hierarchy of the Time dimension.
The attributes of the dimension (applicable to all the levels) are: END_DATE, LONG_DESCRIPTION, SHORT_DESCRIPTION, and TIME_SPAN.
In this structure, we are having a strange observation : During the process of defining this TIME dimension, there were some problems with the machine (it got hanged) and so we had to exit (kill) the AWM and come in again. When we logged in to AWM again, we could see a new attribute called TIME_DSO_1 defined within the Time dimension by itself.
Can anyone let us know what is this attribute all about ? And can we go ahead and just delete this from our dimension structure without creating problems for ourselves?
Many thanks in advance for the kind inputs of the forum.
Regards,
Piyush

Hi,
I can't say that I really understand how your data shows up, but I do see an error in your hierarchy.
What you should do is split it up into two hierarchies.
Year-> Quarter-> Month-> Day
and
Year-> Week-> Day
And here is the reason:
A day can easily have a week as a parent and month. But week cannot. Since a month can end on any given day in a week, that means that a week can have two parents. If I take the next week as an example. Mon, tue, wed, thu and fri would belong to the august month, while the rest of the week would belong to september. But the entire week would still be week 35. And its the same issue with quarter. Months can be added into a quarter, but weeks can not.
Now, I'm not sure if this would solve all your problems, but there might be a few other things you might check out and thats what ID's you populate your member fields with.
say that you have used the month numbers (or at least the same id for every january and so on)to populate your months. If that is the case things will also behave extremely weird and slow. What you need to do is to create unique IDs for every month (and any other level) so that you are sure that january 2007 don't have any child records that really should belong to january 2006.
As a general rule, the member field needs to contain a completely unique value across on from all levels. The "generate surrogate key" functionality helps you a bit along the way as it adds the name of your level in front of the value that you load. If the values you load doesn't have unique values within the level it won't help you any.
Hope this can help you some more... ;)
regards Ragnar

OWB 904 - problems creating time dimension

I'm using Oracle9iR2 DB and OWB 904. I have not much experience with OWB 904 yet and problems with creating the time dimension.
I tried to figure out the example which comes with OWB 904 and did everything as it is written in the readme.txt file:
1. loaded the time table functions owb_time_seq.sql and owb_time.sql in my runtime user schema
2. imported the owb_bp_time.mdl file into my design repository, which created the demo project 'OWB_BP'
The problems which I have with this demo are:
1.) I get warnings when I validate the mappings (TF_TIME_MAP):
VLD-1002: Mapping object T_TIME is not bound to a repository object.
VLD-1004: Column length of L_DAY_NAME is longer than the target column length.
VLD-1004: Column length of L_MONTH_NAME is longer than the target column length.
VLD-1004: Column length of L_QUARTER_NAME is longer than the target column length.
VLD-1004: Column length of L_YEAR_NAME is longer than the target column length.
VLD-3260: No Output Attribute name is specified. In this case, the attribute’s physical name will be used.
VLD-1123: Missing location information for Module WAREHOUSE.
VLD-1115: Commit frequency is defaulted to Bulk Size.
I know how to solve the errors VLD-1002, VLD-1004, VLD-1123 and VLD-1115 but I have no idea how I should solve VLD-3260 and VLD-1002, because reconcile outbound is not possible for the T_TIME dimension.
2.) When I try to import the table function
TIMEDATA (IN VARCHAR2, IN NUMBER) return TABLE
from the runtime user schema into my design repository I get the error message: Argument Data type is not supported.
3.) I cant deploy the mapping TF_TIME_MAP.
Is it possible to use the table function from the demo to create a time dimension and to import it into my own project? My aim is to create a bean compliant time dimension and I want to know what I have to bear in mind to accomplish that. The OWB904UsersGuide didn't give me enough information, therefore I'm asking if you can help me out.
Thanks in advance,
Dirk

Dirk,
The way you should approach the time dimension is following:
- Run the SQL scripts into your target schema (you already did).
- Import the MDL file (you already did).
- Copy and paste the times dimension into your own project to be able to use it.
- Copy and paste the mapping you want to use to your own project.
- If necessary, modify the times dimension according to your needs; change the mapping accordingly.
- Open the mapping, do a right mouse click on the time dimension and select 'Reconcile inbound'. Select matching strategy to match by bound name.
We do not currently support the table function as an object in the metadata repository. I.e. if it exists at runtime then you can call it (as the time dimension load mappings do).
With the objects in the target schema you should be able to deploy the mapping.
Thanks,
Mark.

Non-additive time dimension

Hi, I have an issue modelling the time dimension for one of our facts (employee counts). The problem is this - when a user says "I want to see the count of employees for a given time period" - what they mean is that they want to see the count of employees as of the last day in that time period. i.e. "June employee counts" means employee counts as of 6/30, "Year 2000" employee counts means as of 12/31/2000.
This is very similar to modelling a "ending balance" inventory type problem in OBIEE.
I've solved this (poorly) in OBIEE by changing the aggregation to use "LAST" for the time dimension and "count(distinct(emplid))" for everything else. This works....but....the performance is horrible. If I ask for employee counts for year 2000, it appears to bring down employee counts for all 365 days in the year, then sorting them by date, then throwing away all except the last date. In other words, it brings back 364 days worth of records and then throws them away. This makes the query perform absolutely terrible. A 2 or 3 second query ends up running for minutes.
Does anyone have a different way to solve this issue?
Thanks,
Scott

Hi Christian - agree completely, I just wish OBIEE were smart enough to do the "last" bit on the 2000 row time dimension instead of the mutli-million rows fact table...
I've thought about trying to materialize the measures, but I have a hidden "twist" on my data. In our fact table, I do NOT write a record for each day for each employee. Instead, I only write a record when something on the employee fact changes. So instead of having a hard "date" column, I instead have a "start date" and "end date", and then need to join to the reporting date dimension using a BETWEEN. I do this because most records stay unchanged for long periods of time, so instead of 365 records per employee per year, I average under 3 records per employee per year.
I may give the multiple fact LTS a try, but truthfully I'm a big believer in simplicity (mainly because I'm lazy....) so was trying to find something easier.
And honestly, I'd use a cube if I could, I'm a (very) old Express wiennie.
Thanks,
Scott

Time Dimension and database 8.1.7.3

Similar Messages

Maybe you are looking for