Dimension Time

Good morning,
I have the following problem:
I created a table TIME with fields day (ex: 1, 2, 3, ...), month (ex: January, ...) and year (ex: 2000, 2001, ...).
My table contains data such as:
2000 February 1
2000 February 2
2000 February 3
2000 February 4
2000 March 1
2000 March 2
2001 ....
Then I created a time dimension with the level day, month and year
I did the mapping
But when I try to watch my dimension I see something like this:
2000
January
9
10
11
12
1
2
10
11
I have several times the same day and I do not really understand why ... Normally I should have all the years, months and days as in my OLTP system, isn't it?
Like:
2000
February
1
2
3
4
Someone can help me?
My configuration:
Server: Oracle enterprise edition 11g
Client: AWM 11g
Thank you in advance,
David

The question is that when i do the reverse engineering of a planning application i cant see the dimension time such as version and scenario dimension and so i cant use the time dimension table target to load my dimension time .csv (for example the following structure: year, month grouped by quarters, and days grouped by weeks) into planning by the same procedure (by mapping source and target table) to load others sample dimensions (metadata) such as account, entity or another dimension that i have created after that i have created the application.
thanks
best regards

Similar Messages

Measures depending about dimension time

Hello!!
I have one problem about one report, depends of dimension time I can see one measure multiply with, one number depends if I choose Year,Month or Day.
I put a example:
I have a prompt in my dashboard, and I want that :
if user choose one specific year AND Month All choices and day All choices, my measure show me (measure*100)
if user choose one specific month AND day All choices, my measure show me (measure*50)
if user choose one specific day, my measure show me (measure)
I think that if in my prompt I create presentation variables (v_year, v_month and v_day) and in answers page edit my measure like this:
CASE WHEN @{v_month} = 'All choices' AND @{v_day} = 'All choices' THEN "- Actual"."Nº Cons"*100 ELSE CASE WHEN @{v_month} <> 'All choices' AND @{v_day} = 'All choices' THEN "- Actual"."Nº Cons"*50 ELSE CASE THEN @{v_day} <> 'All choices' THEN "- Actual"."Nº Cons"END
But I don't know how can I write "All choices". Can u correct my sentence or give another solution about this problem??
Thank you very much!!!

Hi,
You may use the bit_length(presentation_variable) function that returns zero when 'All Choices' o no choice is selected in the prompt. It returns a value greater than zero when a value is selected in the prompt.
Your case looks like the following:
CASE WHEN
*bit_length('@{v_year}') > 0 AND*
*bit_length('@{v_month}') = 0*
*AND bit_length('@{v_day}') = 0 THEN "- Actual"."Nº Cons"*100*
*WHEN bit_length('@{v_month}') > 0*
*AND bit_length('@{v_day}') = 0*
THEN "- Actual"."Nº Cons"50*
*WHEN bit_length('@{v_day}') > 0*
THEN "- Actual"."Nº Cons" END
Hope this help,
Monica

Obiee 11g problem with dimension time DATETIME

Hi experts!
I have a problem with a column of my time dimension. In my database I have a column called "DATE" and it has this format "01/12/2009 00:00:00" (property column is DATETIME) when I import this table in Oracle Administration I see the same format that my database but I want to see without any Hours,minutes...like this: "01/12/2009"
How can I fix this??
Thanks!!!

Hi alex,
check the column name your passing and then cast it....the error is not related to that i suppose as it is internal assertion.
chk this http://tipsonobiee.blogspot.com/2009/06/error-nqserror-46036-internal-assertion.html
UPDATED POST
You can alternatively use oracle trunc function in the physical layer to trunc the timestamp.
1) go to the table where the date column is coming in physical layer
2) go to the general properties and select SQL and write the SQL of all the columns needed from that table like
select x,y,z,trunc(date) from table_name.
3) this truncates the timestamp
UPDATED POST-2
By the way which database are you using,if its oracle trunc works out....other databases it wont work
select trunc(sysdate) from dual in your TOAD and check out.
hope helps you,
Cheers,
KK
Edited by: Kranthi.K on Jul 27, 2011 3:15 AM
Edited by: Kranthi.K on Jul 27, 2011 4:01 AM

Processing dimension Time Out Error

Hi All,
I face an issue while processing one dimension "CUSTOMERINP',it throws a run time error timed out.
But all other dimensions i'm able to process successfully,error occurs for ths specific dimension.
In BW, transaction ST22, the apab run time error is " BPC_ADMIN 300 C TIME_OUT.
Does anyone of you have any idea on this particular issue.
Thank you so much!
Regards,
Anila
Edited by: Anila Mohan on Jul 28, 2010 6:41 AM

I think,While redirecting to the processing page AM Retention is needed.
Although I am not very sure. Never used processing page.Please try this ...
OAProcessingPage page=...//page declaration
page.setRetainAMValue(true);

Dimension Time - Level property SEMESTER value?

Hello all,
I'm triying to organize a time dimension this way:
-YEAR
-SEMESTER
-QUARTER
-MONTH
I've an issue, and it's when I'm setting the LEVEL property to the corresponding semester in the hierarchy. If I set it to SEMESTER, the dimension won't process. What is the correct value for a semester? In the meantime I left the property set to QUARTER, is there any problem with this?
Thanks in advance!
Best regards

Hi Giovanni,
As you can see in the documentation here ([http://help.sap.com/saphelp_bpc75_nw/helpdata/en/4a/88580e1e01465f9ae876ffc46becd2/frameset.htm]), SEMESTER and HALFYEAR are not valid options for the LEVEL property in BPC NW. You could set these members as QUARTER and then set the actual quarters as MONTH and so on, but this will mess up your QTD and PERIODIC calculations, so it is not a good option.
I recommend that you maintain a PARENTH1 hierarchy on your time dimension that has conventional years, quarters, and months. Then maintain a secondary PARENTH2 hierarchy that contains only semesters/half-years (with the LEVEL set to YEAR or QUARTER) and months. In this way you can provide an aggregation on semester for your users.
If that is not what you are trying to accomplish, can you tell us a little bit more about what it is you want to do with these semesters?
Cheers,
Ethan

BPC Dimension TIME. How is TIMEID Format?

Hi All.
Anybody has a information about TIMEID format for WEEK and DAY?
For MONTH I used January 2010 --> 20100100
For YEAR and QUARTER         Total 2010      --> 10000001
                                                   Q1                 --> 10000002
                                                   Q2                 --> 10000003
But I'm not sure about WEEK and DAY.
The values of TIMEID is important? or is only necessary that this is unique.
Thanks
Marco

Some info provided in the following post :
Re: Time Dimension Master Data : Days

How do I include 'Time' in a time dimension?

I have a requirement where I need to classify the data in the warehouse based on date and time (example : between 10 am to 11 am, 3.00 pm to 6.00 pm like that).
The time dimension created by OWB contains only the date part and when I load the data I use the expression TO_NUMBER(TO_CHAR(input,'YYYYMMDD')) to populate the date.
But I would like to include the time also in the expression like 'YYYYMMDDHHMISS'. But unfortunately the OWB generated time dimension does not have data in this format.
How do I do that? Any pointers?
thanks in advance

You rather create 2 dimensions: Time and TimeOfDay. The first one will have all the date values with it characteristics. The second one will hold the all the possible HH24:MI:SS values with it's characteristics, for example which hour and which part of the day it is (Morning, Afternoon, Evening, Midnight or whether it's lunch time or not), depending on the requirements.
If you try to combine them both into 1 dimension you will get 86400 dimension records every day. Your dimension table will probably will become bigger than the fact tables.

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.

'Time' dimension hierarchy Required

Dear all,
We came across one requirement where 'Time' dimension having 365 days along with month, quarter, halfyear and yeartot as their ancestor.
"Time" Dimension hierarchy:
Time
- Yeartot
- Half year
- Quarters
- Months
- Days
Also we need alternate hierarchy in time dimension:
Time
- Yeartot
- Weeks
- Week1
- 1 Apr
- 2 Apr
- Week2
Weeks are Monday to sunday.
We are using 11.1.1.2 version.
Can anyone suggest me how to achieve this in Planning?
Thanks in Adv,
Bunny

I believe the limit for Planning's Period dimension is 400 members.
That's going to get you the first bit, but not the alternate hierarchy.
Does this alternate hierarchy have to be in Planning, or could it be in Essbase only?
This isn't exactly a recommended strategy, but I think you can still use the HSP_UDF UDA in Essbase to basically make your alternate hierarchy happen only in Essbase. It won't show up on forms, but will be available from a reporting tool.
I have not tried HSP_UDF (it was used all the time on pre System 9 (maybe Planning 4) Planning apps to get in member formulas) in 11, so it may be worth trying a small alternate hierarchy with that UDF and then forcing a refresh to see if it still sticks about.
Regards,
Cameron Lackpour

Populating the time dimension in ODI

I need to populate my time dimension in ODI> I read a solution in this forum suggesting to create a time table/view in the source schema, reverse it in ODI and then use it as source to populate the time dimension. Is there another way to do this? One way I thought of was to use the ORDERDATE field in my ORDER table (my source table in Oracle) and map it to my time dimension in SQL Server via an interface. But I also have DUEDATE, SHIPDATE and PAYDATE fields in my ORDERS table and this approach would mean that I have to map them through separate interfaces to the time dimension as well. I have created a procedure in the source schema(Oracle) and want to use it in ODI to populate the time dimension. But I amnt sure if that is possible in ODI. Could anyone help me with this please?
Regards,
Neel

Hi Neelab,
Sorry for my delay to reply you, I had no time the lasts days...
To get the four distinct key from your time dimension, just add four instance of dimension table at interface each one joined with one of the columns.
I believe that you load your time dimension from some other table than PRJ_TBL_TRANSACTION because you have the HolidayType column in your time dimension...
A view is one possible solution to load the time table but depends how the performance of the query is.
A way to do it at ODI is:
- Create 4 interfaces, one for each column, to load 1 singe table with 1 single date column, don't worry about duplicated value at this time, than you can just use the "IKM Control Append" that has more performance but check the "Distinct" box (flow tab) at each interface
- Create a last interface from this temp table as source, to the time dimension target table. Now you will use the "IKM Incremental Update" and do choose the "Update" option to "NO". Check the "Distinct" box.
As this table will have no more than 6.200 records from the last 20 years it will be a small table where you shouldn't have performance problems.
These are some of possible solutions but I would like to add other "way to think".
By the table that you show here you have a simple time table with no special feature, for that, let me suggest you other way.
- in the current way you will join but didn't get the record that "fail" from the join once they will be exclude if a date do not exist at time dimension
My suggestion:
- Load the dimension time table from your source table
- as PK in time dimension table, use the ''Julian Day"
- At ODI target fact table (datastore), create a 4 reference constraints (one by column) to the time dimension
- at interface do not use the dimension as source and transform the 4 date to Julian and let the 4 constraints take care if they exists or not at dimension table.
OR
- Look for the minimum "possible" date at your company
- populate your time dimension with every each day since then until a future date (Dec 31, for instance)
- create a process to populate the future date that will be execute in a interval that you decide (once a year, once a month, as you wish) dependent on how further the date is populated
- use the "Julian date" as PK
- At interface just transform any date to "Julian Date" it will be at dimension time once it is naturally unique
You could substitute the Julian date for "YYYYMMDD" that is a unique value too.
I presented you 2 way to consider be considered, each one could be used based on how important is for the business know if a date was loaded or not.
Someone can question that has the dates loaded from source against has all dates previous loaded could help to find errors from days that wasn’t loaded but it has a failure. As there are 4 dates source columns (and we are talking just about one source table until now) if a date loaded math a date when the load failure there is no value in use the time dimension date to analyze this possibility.
I defend the full time dimension load.
Make sense and/or help you??

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.

Time Dimension 2 PARENTH2 and PRIOR,NEXT

Hi all,
We have standart TIME hierarchy from AppShell (MONTH, QUARTER, YEAR). But in some cases users want insert data in detalization by week. We decide add additional ID's with detalizations to weeks and add they in second hierarchy. Everything is ok in system.
But than we try write scrip logic with PRIOR or NEXT which use data from previous year it doesn't work. But than we use PRIOR or NEXT with current year months everything ok.
Example of logic.
*XDIM_MEMBERSET TIME = PRIOR, %TIME_SET%, %YEAR%.DEC
*CALC_EACH_PERIOD
*WHEN P_ACCT
*IS A01
*REC(EXPRESSION=%VALUE% - GET(P_ACCT="A02",TIME=PRIOR), P_ACCT = A03)
*ENDWHEN
*ENDWHEN
Then we save data on January it doesn't work. BUt on December prev year A02 and January A01 we have data.
Maybe you have some advises according second TIME dimension hierarchy. I think problem on it.
Best regards,
iaroslav

Hi,
Here is fragment of debuglogic.
Start time --->7:29:17 PM - Date:9/28/2011 (build code:7.5.107)
User:T2RU\bpc.sysadmin
Appset:DEVTELE2
App:BUDGETS
Logic mode:0
Logic by:
Scope by:CATEGORY,INPUTCURRENCY,P_BF,P_BUDDIM,P_BUDDIM2,P_BUSTYPE,P_CC,P_CITY,P_DATASRC,P_PROJECT,TIME
Data File:
Debug File:D:\PC_MS\DATA\WebFolders\DEVTELE2\BUDGETS\PrivatePublications\bpc.sysadmin\TempFiles\DebugLogic.log
Logic File:
Selection:DIMENSION:CATEGORY|BU|DIMENSION:INPUTCURRENCY|RUR|DIMENSION:P_BF|IBF19|DIMENSION:P_BUDDIM|NO_BUDDIM|DIMENSION:P_BUDDIM2|NO_BUDDIM2|DIMENSION:P_BUSTYPE|NO_PRODUCT|DIMENSION:P_CC|3_KEM_FF_FA|DIMENSION:P_CITY|KEM|DIMENSION:P_DATASRC|CCDATA|DIMENSION:P_PROJECT|PR_PL|DIMENSION:TIME|2012.JAN|
Run mode:1
Query size:0
Delim:,
Query type:0
Simulation:0
Calc diff.:1
Formula script:
Max Members:
Test mode:0
Is Modelling:1
Query Type:0
Max members:
Region:
DIMENSION:CATEGORY
BU
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_ACCT
----- There a lot of accounts <All> accounts and I dont show it all
DIMENSION:P_BF
IBF19
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_CC
3_KEM_FF_FA
DIMENSION:P_CITY
KEM
DIMENSION:P_DATASRC
CCDATA
DIMENSION:P_PROJECT
PR_PL
DIMENSION:TIME
2012.JAN
DIMENSION:P_CC
3_KIR_FF_FA
DIMENSION:CATEGORY
BU
DIMENSION:P_DATASRC
CCDATA
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_BF
IBF19, IBF15
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:TIME
PRIOR, %YEAR%.JAN, %YEAR%.FEB, %YEAR%.MAR, %YEAR%.APR, %YEAR%.MAY, %YEAR%.JUN, %YEAR%.JUL, %YEAR%.AUG, %YEAR%.SEP, %YEAR%.OCT, %YEAR%.NOV, %YEAR%.DEC
DIMENSION:P_ACCT
<ALL>
Loading TIME.TIMEID
Time to load properties:0.0 sec.
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
into #tblTempLogic_266166
from tblFactBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFactWBBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
and SOURCE = 0
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFAC2BUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
select tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID,sum(SIGNEDDATA) as SIGNEDDATA
from #tblTempLogic_266166 as tmpTable
group by tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID
drop table #tblTempLogic_266166
I saw that TIMEID 10000425 is incorrect -its 2012.DEC.WEEK3 from second hierarchy
Thanks,
Bets regards
Iaroslav

Dynamic Time Dimension

Hi,
I've a problem during the set up of the Time Dimension of my Planning Application.
The structure of this dimension is the following:
Year
Months (grouped in 4 different quartes)
Days (grouped in different weeks per month).
My purpose is in having a dynamic dimension time which cross year dimension and update
days and weeks in relation to the year.
Can anyone help me?

It's been quite awhile since i personally created a planning app. but from what I remember, I believe there were essentially 3 options.
I believe there was a 52 week option, and a monthly app, and also a custom. (I dont remember there being a 'day' selection, someone please correct me if i am wrong).
Create an app with a custom # of periods, and enter 366 (includes leap years)
Your periods are going to be numbered P01-P365. So you will have to rename these.
Go ahead and then add the structure you want (in weeks, months and quarters), by adding members via planning web, You wont be able to move the level 0 members, so you have to create the upper level members and group them manually by specifying what time periods encompass each week/month/quarter.
Its a lot of manual work up front. I could be mistaken in the options which create days/weeks/months/quarters rollup, because its been awhile but even if that doesn;t exist just create a custom time dimension and put the structure around the level 0 members which it creates for you.
keep in mind that with a time dimension 366/367 members large, your block size is going to be massive, and will slow down performance.

OBIEE 11g Time Hierarchy with YTD function problem

Hi all,
Platform: OBIEE 11.1.1.5.0.
We have a Calendar dimension (*time dimension*), that includes the usual time hierarchy (Year > Semester > Quarter> Month > Day).
Creating a Pivot Table with a YTD measure, using also the Calendar Table hierarchy, everything works fine, and we can drill up & down always getting the right YTD values.
But, if we add to this analysis, a year and month prompts (filters), we only receive true YTD values, at the day and month levels of the hierarchy. Above this, values will sum up instead of getting the right YTD aggregated value.
YTD logical column definition = TODATE(Table A.Measure B , Hieararchy.Year)
Example of pivot values returned:
*2011*=1192812 (Sum of the 3 Semester not the YTD value)
Semester 1 = 377305 (Sum of the 4 Quarter not the YTD value)
Quarter 1= 107460 (Sum of the 3 months not the YTD value)
Jan = 18507 (YTD value)
Feb = 35223 (YTD value)
Mar = 53730 (YTD value)
Is there anything that we might be doing wrong?
Thanks in advance,
Ricardo

Ricardo,
You might be aggregatign values twice either at RPD level or at reprot level. Please check on that.

2 Variance Dimensions - Possible

Anyone know if there will ever be a (dynamic) 3 Pass calc mode?
I imagine I am not alone in having a situation where this would be incredibly useful - so it's possible there is some workaround for this...
Specifically I need to calculate variances in 2 dimensions (Time and Scenario), for a variety of 2 pass Dynamically calculated Accounts Rates without making the Time and Scenario dimensions dense (performance is terrible with a 1MB block).
I don't really see any other way to get around my problem because as long as Accounts are dense and dynamic 2 pass, they will calculate after my variance calculations execute. Only by making Time and Scenario Dense, with 2 pass calcs will the variances calculate after the rates.
Any Ideas?

Thanks for the tips.
I determined that a couple of 2 pass accounts which were necessary could be re-ordered to make them single pass, thus freeing up a pass, and allowing me to get around the problem.
However, you raise a good point about ASO, and I'm starting to take a look into it, because it seems pretty flexible. Only problem is the support of incremental data loads is a bit difficult in 7x

Dimension Time

Similar Messages

Maybe you are looking for