Time dimension wizard and leap year error?

I've created a time dimension (rolap) using the wizard. I started with 2006 for 6 years. I used a fiscal calendar, 445, fiscal year start = jan 1, and month start = monday.
The first 2 months of 2008 are ok. However, OWB ends the third month on March 31, 2008 and it should be March 30, 2008. It starts the next month on April 1, 2008 which is a Tuesday.
I've tested with 10.2 and 11.1.
Anybody seen this or have a solution?
Garrett

Garrett
The start day that you specified as being Monday is in fact the week start day and not the month start day. In most cases these will both always land on the day of week you specify, but there are exceptions.
The Fiscal year is split into Quarters and the start of each Quarter is based on the date of the start of the year, so if you started the year at Jan 6th, then the 2nd quarter will start on April 6th, and the third on July 6th and so on.
In your case, an extra day is inserted in the 5th week of the first quarter so that the quarter can start at the correct date

Similar Messages

Time Dimension Wizard Hangs Creating Map

I'm running OWB 11.1.0.7 and trying to create a time dimension using the time dimension wizard and when I get to the progress screen it just hangs when it gets to 60% progress and the message window says it's creating the map.
There is no indication of any kind of error that might say why it's hanging, or any indication other than "creating map" that says what it's trying to do at the time. Is there anyway to dig under the covers anywhere to see what the wizard is trying to do that is causing it to hang?
Another question is how I can create the same kind of dimension manually that the wizard would have created? It appears to be creating a special kind of dimension, specifically for time but I can't see anyway to create it manually if the wizard doesn't work. I found another message that mentioned a time dimension template that the wizard uses but that post was about how to use OMBPlus to remove the time template type so it could be edited manually, not how to create one using it.
So, anyone have any suggestions for how I can track this problem down and/or create that time dimension manually? Thanks.
Regards, Bob

Are you using OWB 11.1.0.7 or greater?
We encountered the same problem from that version on. try to use an older version (11.1.0.6 client definitely works).
We will put this into metalink as it is definitely a bug.
Cheers,
Knut

Oracle 11gR2 use the time dimension wizard---the cube didn't show any information!

I created a Time Dimension with the Time dimension wizard , a category dimension, and a rel_expense cube in OWB 。what I do is following the oracle 11g r1's turtoial
The rel_expense cube has two forigen keys, one is refrence the category dimension's dimension_key(primary key in the category dimension), and the other one refrence the time dimension's start_day_date(bussniess key in the time dimension).
The result I get is the rel_expense_tab had datas, but the rel_expense cube had nothing.
.I delete the category dimension , it is the same result(cube rel_expense had nothing).
But if I only delete the time dimension, it is ok(both of them had datas)!!!
So I think is the time dimension's problem ,because the 11g r2's time dimension wizard didnt' generate the dimension_key for time. Is the forigen key(time dimension) i refrenced in the cube is error,so if it is, what should I do?
SEEK FOR YOU HELP!!!!!
ps:my mother language isn't English ,so it has many erros in the passage

can anybody help me? the measures in my cube were round to integer, i doubt it came from time dimension. did anyone encounts such a senario

Oracle Warehouse Builder 11GR2 -no time dimension wizard?

Hi,
I am running OWB 11GR2 on top of a 11GR2 database (OEL 5.4 64 bit).
I don't have a time dimension wizard, just a normal wizard. What I do is right-click, new dimension....but no time wizard. How can I activate it?
I have installed everything several times, but no luck...
Can anyone help, please?

Hi
Right Johnny. This happened when we moved to the new UI, all objects can be created using the New 'gallery' style approach, not exactly intuitive for how you remember time dimensions being created but it's still all there.
Cheers
David

Seeking advice regarding Time Dimension - Correction and Customization

Dear all:
Situation
1. We have a measure called HTD, Half Year to Date, which aggregates 6 months worth of data. However, I just realized that the previous consultants set HTD at LEVEL = "Week". It works fine but I feel that this naming convention is confusing, and would like to rename HTD's LEVEL.
2. We have 4 more additional periods after period 12 for adjustment purpose. What is the good practice to have a year with 16 periods?
Data
Current LEVEL for Half Year to Date is named "Week". I would like to rename this to something like "HalfYr"
200x.01 - 12 are regular periods
200x.13 - 16 are additional periods
Question
1. If I go to SQL's back end and rename my LEVEL, and then update my Time dimension, is this going to pose a problem to my historical data?
2. I would like to include additional 4 more periods to sync with BW, but at the same time not confuse my BPC users in running reports at month of December. In other words, how do I integrate the 16 period time dimension design into the concept of "1 yr = 12 months (periods)"?

Tim:
Sorry for the late reply.
We are running BPC 5.1 SP3 and SQL 2003
Yes, MONTH, QUARTER, YEAR are used for LEVEL property, and the only irrelevance is HALF YEAR which has WEEK in LEVEL property.
I think perhaps a separate data source makes sense... Have you handled any case like this before and how did you manage the "additional" periods?
Thank you! Have a great day!
Sincerely,
Brian

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.

How to use the Time Variants PYTD and Prior Year Annual?

Hi,
We have a time dimension which has the generic columns i.e Month, Year.
We need to calculate the Time variants for the Facts Say Sales. I was able to calculate the Prior Month, Current YTD
I have some doubts regarding the other variants:
1. Prior Year : Does this include the Prior Year Annual?
2. Prior YTD: How to calculate it?
Somehow I am getting the same results for PYTD and Prior Year.
The formula used are :
Prior Year:
AGO(Sales, Year, 1)
PYTD:
AGO(Sales CYTD, Year, 1)
Has anybody encountered similar issue?

I assume the Sales measure is a monthly measure. The Prior year calculation as I described will give you the sales for the same month in the previous year when selecting month in your report. When selecting year it will add up all months of the prior year until now and you will indeed see the Prior year YTD.
If you want to see the total sales for the previous year you have to use the same calculation as 'Prior year' and map it to the year level of your time dimension. This will work as a 'partition by year'.

Function CALCULATE_DATE and leap year

Hi,
I need to substract some months from a date. I tried to use the standard function CALCULATE_DATE but it has a proble with leap years. If I execute it with the following parameters:
CALL FUNCTION 'CALCULATE_DATE'
     EXPORTING
          days        = '0'
          months      = '-24'
          start_date = '20080229'
     IMPORTING
          result_date = X.
The value that I get in X is '00000000' because 2006 isn't a leap year. The problem is that the function doesn't know how to deal with this. The solution is very easy, buy if it's possible I would like to use a standard function.
Do you know if there are any standard function that has no problems with leap years?
Thanks and kind regards,
Marcela.

Hi Marcela,
Welcome to SDN.
You can try this FM <b>RP_CALC_DATE_IN_INTERVAL</b>.
data: wa_date like sy-datum.
call function 'RP_CALC_DATE_IN_INTERVAL'
         exporting
              date      = '20080229'
              days      = 0
              months    = 24
              signum    = '-'
              years     = 0
         importing
              calc_date = wa_date.
Hope this will help.
Regards,
Ferry Lianto

ICal and Leap Year

I had set up a yearly recurring event for a birthday notification for Feb 29 (Leap Year) with a Alarm notification 6 days in advance of the day so I could be sure to send out a card in time, etc. etc. However, because there is no Feb 29 in calendar year 2010 it appears that the Alarm notification isn't working. Is this a bug or did I possibly do something wrong?

Yes, I noticed this the other day but didn't make a connection with the US holidays. Odd quirk.

Bug with interval and leap years

select to_date('2012-feb-29','yyyy-mon-dd') + interval '1' year as dt from dual;
ORA-01839: date not valid for month specified
01839. 00000 - "date not valid for month specified"
*Cause:
*Action:
select to_date('2012-feb-29','yyyy-mon-dd') + interval '2' year as dt from dual;
ORA-01839: date not valid for month specified
01839. 00000 - "date not valid for month specified"
*Cause:
*Action:
select to_date('2012-feb-29','yyyy-mon-dd') + interval '3' year as dt from dual;
ORA-01839: date not valid for month specified
01839. 00000 - "date not valid for month specified"
*Cause:
*Action:
select to_date('2012-feb-29','yyyy-mon-dd') + interval '4' year as dt from dual;
29-FEB-16 00:00:00
select to_date('2012-feb-29','yyyy-mon-dd') + interval '1' day as dt from dual;
01-MAR-12 00:00:00
select to_date('2012-feb-29','yyyy-mon-dd') + interval '1' month as dt from dual;
29-MAR-12 00:00:00The problem exists in 10.2.0.4 and 11.2.0.3
Edited by: Sanjeev Chauhan on Feb 29, 2012 9:20 AM

>
considering this answered is simply sweeping an issue under the rug.
>
No - the question was answered. Did you read the reference that Paul cited? That is an ISO document and defines the standard.
The section he referred to is General Rules 3b and states:
>
b) Arithmetic is performed so as to maintain the integrity of the datetime data type that
is the result of the <datetime value expression>. This may involve carry from or to the
immediately next more significant <datetime field>. If the data type of the <datetime value
expression> is TIME, then arithmetic on the HOUR <datetime field> is undertaken modulo
24. If the <interval value expression> or <interval term> is a year-month interval, then the
DAY field of the result is the same as the DAY field of the <datetime term> or <datetime
value expression>.
c) If, after the preceding step, any <datetime field> of the result is outside the permissible
range of values for the field or the result is invalid based on the natural rules for dates and
times, then an exception condition is raised: data exception—datetime field overflow.
Note: For the permissible range of values for <datetime field>s, see Table 11, "Valid values for fields
in datetime items".
>
The relevant part of the above for year-month is
>
then the
DAY field of the result is the same as the DAY field of the <datetime term> or <datetime
value expression>.
>
DAY FIELD OF THE RESULT IS THE SAME AS THE DAY FIELD OF THE <DATETIME TERM>.
That is, for 'year-month' the day cannot change and, per section c, if it does an exception is raised.
That is how Oracle implements it. If the other databases implement it incorrectly then they have the problem not Oracle. The question was regarding Oracle's implementation so the question for Oracle is answered.
That document was printed in 1994 but the current document, ISO-8601 2004, does not alter it at all.
http://dotat.at/tmp/ISO_8601-2004_E.pdf

Cannot recreate mapping to populate MOLAP time dimension

I am using OWB10gR2 to create a time dimension having MOLAP as storage type and two hierarchies (year and week).
I used the wizard to create a time dimension having the standard year hierarchy. The wizard does not allow to generate the time dimension with both hierarchies (why?). That's why I had to manually add the week hierarchy with the object editor in a second step. The next step would be to recreate the mapping to populate the time dimension, but I got the following error message:
"There is no sequence attached to the dimension. Please add a sequence in the attribute tab."
I tried the same thing with ROLAP as storage types: for ROLAP I can recreate the mapping.
Does anybody have a solution for that problem?
Many thanks in advance!!

I further explored the Time dimension wizard and for standard if i select year,month and day .... the autogenerated mapping generates a validation error... Anyways i am using oracle11gr2 any ideas why this is happening ??

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

Time dimension (Using Wizard)

Hi
i want to create Time dimension using simple wizard(not through time wizard)
i have following attributes in it
Year( year ID,year Discription)
Quarter(Quarter ID,Quarter Discription)
Month ( Month ID,Month Discription)
Week ( week ID,week Discription)
DAY ( Day ID,Day Discription)
Hours ( hours ID,hours Discription)
i complete time dimension with simple wizard but it create sequence and table
so what is mapping for it kindly give me guide in detail
thnx in advance

Hi,
you may create your custom time dimension using the simple wizard.
To fill it with values, create another time dimension with the time dimension wizard. Fill it using the generated mapping.
Then write your own mapping to fill your time dimensions with the values from the generated one.
This way is easier than to write some custom logic to fill your custom time dimension.
Regards,
Carsten.

Weeks and Months roll-up in Time dimension

We need to change our Time dimension roll-up ('Total Year' 'Quarter' 'Month') as some users want to see the week level as well. What is the best way to do that? I still want to use the DTS and both need to be Time dimension. Thanks for your reply.

Assuming you have data down to the daily level, another option would be to create an alternate hierarchy in your time dimension. You would use your level zero members (individual days) that are currently rolling up into months and share them. Your Time dimension you would then have two children; "By Months" and "By Weeks".Under months you would have Jan, Feb, Mar, etc. Under Weeks you would have Week 1, Week 2, ... Week 52. The level zero members are the same for both. What I like about this method is it does not add any overhead since you are using shared members, and you don't run into a situation where your total "by months" varies from your total "by weeks". Since your base level data is the same you can have confidence that your data will tie out. Of course the end user needs to decide when they run their report wether they want to run by months or by weeks. My users were more than happy to do this when I explained there was no practical way to have months and weeks in the same hierarchy since weeks will overlap months. I have an outline set this way and I am using DTS effectively. If you want, send me an email and I will send you an OTL file with the Time dimension as I explained.Best Regards;

Help with Time Dimensions

Hi,
I am trying to create a Time Dimension using the Wizard, but I want to add certain fields to the dimension like Month Ago, Week Ago, Quarter Ago, etc. What are the steps to do this?
Also, is it possible to combine Fiscal and Calendar year into the same dimension?
Thanks

Gurus, anybody anything on this one??
I haave done a small adjustment in the dimension order by which I have eliminated the following error:
Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
Record #40 - No time dimension defined
But, I have the following new error/warning (cube build successfull in this case) when I made this adjustment:
Record #427 - Error adding Attribute to member PATB4_ADJ-PDA (3320)
The adjustment I made is... I moved TIME dimension up and ACCOUNT dimension below that...so the order I have now is TIME,ACCOUNT,SCENATRIO,XXX,XXXX instead of ACCOUNT,TIME,SCENARIO,XXX,XXXXX ..*would this create any performance issues?*

Time dimension wizard and leap year error?

Similar Messages

Maybe you are looking for