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.

Similar Messages

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

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

Create time dimension table in repository without data warehouse

Hi,
I want to implement only BI repository solution in my customer (not datawarehousing). Is it possible to transform the data by repository tools, so that the times columns in fact tables are categorized by the "time dimension" table?
To be more explanatory:
The "Sales" table has the "time of sale" column. It contains the timestamp when the sale was performed. I have imported this table in "physical layer" of the repository. Now I want to create a new "time dimension" table, something like:
CREATE TABLE dimension_time (
Day_Key INT NOT NULL PRIMARY KEY,
Day_Timestamp DATETIME NOT NULL,
Day_Name NVARCHAR(32) NOT NULL,
Day_Text NVARCHAR(32) NOT NULL,
INSERT INTO dimension_time VALUES (20110101, {d '2011-01-01'}, '1/1', 'January 1', 'Saturday', 0, 6, 1, 1, 185, 1, 201052, 'W52', 'Week 52', 52, 201101, '01', 'January', 1, 7, 1004, 'Winter', 'Winter', 20111, 'Q1', '1st Quarter', 1, 20103, 'Q3', '3rd Quarter', 3, 20111, 'S1', '1st Semester', 1, 20102, 'S2', '2nd Semester', 2, 2011, '2011', '2011', 2010, '10/11', '2010/2011', 0);
INSERT INTO dimension_time VALUES (20110102, {d '2011-01-02'}, '2/1', 'January 2', 'Sunday', 0, 7, 2, 2, 186, 2, 201052, 'W52', 'Week 52', 52, 201101, '01', 'January', 1, 7, 1004, 'Winter', 'Winter', 20111, 'Q1', '1st Quarter', 1, 20103, 'Q3', '3rd Quarter', 3, 20111, 'S1', '1st Semester', 1, 20102, 'S2', '2nd Semester', 2, 2011, '2011', '2011', 2010, '10/11', '2010/2011', 0);
and after to add a new column in "sales" fact table for "time dimension ID" and through the repository populate this column based on the "time of sale" column and the corresponding "time dimension ID".
I know that the ETL process might perform it, but I do not want to go for Data Warehousing (it is not real - time, needs more resources, etc).
Is it possible to perform such action only on repository?
Thank you.

Hi,
I can do it, but this would be usefull only to create "time dimension" table. But also the "sales" fact table needs to be altered (thus, the "time" column will not contain the value of the time, but the ID of the corresponding time in the "time dimension" table).
I know that on DW this procedure is done automatically by the ETL process.
My question is that does the repository has any tools similar to this?
Thank you.

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

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

Creating Time dimension in BW data model. - like seen in logical data model

Hello all,
I have been struggling with this thing and I am looking for some help from anyone on this forum.
We are trying to create a logical data model of our bw system. We are going live next month with Student module for universities. We have multiple Infocubes and DSO and since there is so much crossing over in between them most of the reporting is done on infosets.
One of the thing we were thinking; is it possible to create something like a common time dimension table for every infoprovider. Basically when we are providing the reports to the end user can we give them a drop down menu which gives a time frame for reporting rather than selecting.
Example: Like can we create something which looks in the drop down like current month data, last months data, three months ago, four months ago, five months ago, one year ago, two years ago. Can we make like these data slices in our cube and deliver it to the end user?
We have in our cube a few date infoobjects, like receipt date, decision date, cancellation date and like wise.
Please let me know if any one has done any similar thing, it will be very helpful.
Thank you so much in advance.

if you add your common time dimension to your data model, first identify for each infoprovider the time against which 'current month' and other frames should be applied and map them to your dimension.
just a question... are you not using time dimension in cubes ? ideally this should be your time dimension llinking all.
when you use time dimension which uses 'current month' , 'current year' , you will have to address their historisation as well. (because current month now will not be so current after 2 months).
so in data load procedure every day these values need to change (meaning drop and reload).
and routines to populate these values based on reporting date.
Edited by: hemant vyas on May 6, 2009 1:56 PM

Error in creating time dimension

Hi,
I created a simple time dimension with two levels: year and month, and each level has one element that serves as chronological key. This is the error I got when checking global consistency:
"The physical table 'my time table' , which is part of a time dimension table, is also used in the logical table 'my time table', which is not part of any dimension".
What does it exactly mean?
Thanks for any assistance.

Hi ,
Please provide details about how you are bringing in the table into presentation layer , its seems like the table is taken as a fact table by the tool , its very important how you are defining the relationship in the logical diagram.Some times its easier to bring a dummy table along in the physical layer and make a sensible logical diagram, since you are trying to create a time dimension you want it to have drillability , so you have to create a hierarchy on the same table.The key here is to make sure the tool understands what you really want ,sometimes you have to work around since the logical diagram is the only way the tool makes sense of the tables brought in.
Thank you,
Mohammad Farhan Alam

Odi-Creating time Dimension

hi,
i want to create a time dimension using odi.
How do i create the below table.
CREATE TABLE Dim_Time(
Timekey INT IDENTITY(1,1),
Day CHAR(2),
Month VARCHAR(9),
Quarter CHAR(1),
Year CHAR(4),
Week CHAR(2),
FullDate DATETIME,
Thank You.

You can use an Excel file as a source that contains 1 columns with 1 date by row
then you map the other columns thanks to date function in ODI

Creating Time Dimension

Hi
I have a fact table which has a time data stored in two columns, month_id,year_id.
My fact table looks like this
Sales,Month_ID,Year_ID
How can I model a level based dimension for time for this sort of table ?

You can map the time dimension to a view on top of your fact table as long as the fact is sufficiently dense in time (e.g. there are no missing months). The view would add end date and time span info as appropriate. Alternatively you can define a view that generates dates. The following thread shows the latter approach
populating a date dimension
You can adapt the view in it to derive time info from your fact if you like, but the standalone view is probably easier.

SPRUNCALCACCOUNT to copy PL results to BS problem with time dimension

Hi there,
I'm trying to copy PL result to BS account using account transformation with a simple configuration without informing source period. I'm running the datapackage informing the time dimension. it works fine for 2008.JAN but if we try with 2008.FEB we get same result. We have tried with several time periods allways getting 2008.JAN results copied to BS destination account.
Any ideas on what we're doing wrong.
Thanks in advance,
Regards, Carlos

Sorry guys, It's working fine.....it was my fault, we have a SP for carry-forward that has a little bug.

Ora-00942 when creating time dimension

hi All,
I am new to data warehouse, i have created a date dimension " date_dim " in a target location, it has created a corresponding mapping "date_dim_map" in mappings section.
But when i try to deploy the dimension i get error ora-00942 table or view does not exist.
I get the same error when i try to deploy the corresponding map created by this dimension.
any ideas what the problem could be.
regards

oops got it had to deploy the corresponding table first.\

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

Unable to create time series ago function

Hello guys
I am running into a problem about time series function, ago function
I have a simple schema, fact <---->Time dimension
I have created time dimension hierarchy where month is the lowest level, I have also made it "time dimension" and month is the "chronogical key"..
When applying ago function, I am putting my measure from the fact table, level as "month" from time dimension table, and 1 meaning 1 month ago, when I complile it, I get the following error:
[nQSError: 27009] Unresolved identifier: "FTTNBILLSUM"."FTTNOBIEEBILLTIME"."Month".
Could anybody help me out as what the system doesn't like about this column?
Thanks

Thanks Maden
I did the correction and now it's giving a different error: [nQSError: 22038] Function AGO requires at least one measure attribute in its first argument.
My code is:
Ago("FTTNBILLSUM"."F_Bill_Sum"."ATM_UNITS_Sum" , "FTTNBILLSUM"."D_Time"."Month" , 1)
I have time hierarchy that names: D_Time with Month at the lowest level with Chrono keys, there is no level above it except grand total level, so only 2 level hierachy
I have a fact table that is F_Bill_Sum, which is join to D_Time... I made the D_time both the name of table and hierarchy
Please let me know what this error is coming from
Thanks

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

OWB 904 - problems creating time dimension

Similar Messages

Maybe you are looking for