Checking Time Dimension

Hi experts!
I have a Time dimension with next members:
Year--> INT-----> Exemple: 2011
Quarter-> Char--> Exemple: Q1/11
Month-> Char --> Exemple: January
Day-> Char ------> Exemple: 1 January
Date-> Date ---> Exemple: 01/01/2011
When I try to get a report in answers I don't see all members. I have values in all members of year and only a few rows.
I add in answers all columns and a measure...
I add a picture: http://imageshack.us/photo/my-images/580/timeak.jpg/
Any help to see all rows with value??

http://imageshack.us/photo/my-images/862/acumq.jpg/
I have detected strange error doing a report.
My problem is about Cumulative Year value, if I have a report with Year, Month and Measure Cumulative Value I have good results...but If I add member of dimension DAY I have wrong values...
TIME DIMENSION has fourth herarchies: YEAR->Quarter->Month->Day
Cumulative Value is: TODATE(Measure Periodic, Year)
Any help?

Similar Messages

Sorting Time dimension in EVDRE

Hi all,
This is probably an easy question that for some reason I fail to answer.
I have an EVDRE with Time dimension in the columns.
I have defined my Time dimension as 2011.Jan, 2011.Feb, 2011.Mar etc.
One line below the key I have placed a description (in Hebrew) and I have indicated to hide the column keys.
During the expansion the dimension is not sorted properly. The order (by month number) is:
2011.Feb 2011.Jan 2011.Mar
2011.Apr 2011.Jun 2011.May
2011.Aug 2011.Jul 2011.Sep
2011.Dec 2011.Nov 2011.Oct
It seems that the system sorts it first by querter and then by alphabetic order.
Any ideas how can I control the sorting of columns in EVDRE?
I have also upgraded to 7.5 SP06. I last saved the template in SP05. When I open the template I can see that the dimension is sorted properly and then during the expansion it changes the sorting order. Did any one tackle this in SP06?
Thanks,
Avihay

Hi Avihay,
Actually the dimensions in reports or input schedules appear in the same order as you have maintained the hierarchy. But, yes, you can make some sort of arrangements using control panel memberset option. For eg. you can see parents after or parents before the base level members. There is no other option to change the order of members being displayed in IS or reports.
As far as your issue is concerned, even I was facing exactly the same problem. I checked time dimension membersheet and there found that 'TIMEID' property was not maintained properly. Therefore, would request you to cross-check the TIMEID property in membersheet and if it has been assgned correctly to each of the time dimension members. Goto to Maintain dimension members, change the sheet and reprocess the dimension.
I think this will resolve your issue.
Rgds,
Poonam

Time Dimension Consistency Check Failed

Dear all,
Got a issue..
A cube which is found to be active in RSA1, but when we do the consistency check for time dimension in the transaction RSRV, we get the following error.
Unknown, profound errors with instance creation in test "CL_RSRV_CHK_TIM_DIM"
Pl help to resolve this issue.
Thanks,
Ramya

Hi Ramya,
Welcome to SDN...!!
Check with the Correct Error option in RSRV after selecting testing ur cube.
Best Regards,
SG

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?

ERROR while loading time dimension table

i need to load time dimension from csv to oracle table, while loading i got the error.
my source data type is date and target is date.
ODI-1226: Step sample day fails after 1 attempt(s).
ODI-1240: Flow sample day fails while performing a Loading operation. This flow loads target table W_SAMPLE_DATE.
ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection Target_Oracle.
Caused By: java.sql.SQLException: ORA-30088: datetime/interval precision is out of range
while creating c$ table
create table WORKSCHEMA.C$_0W_SAMPLE_DATE
     C3_ROW_WID     NUMBER(10) NULL,
     C1_CALENDAR_DATE     TIMESTAMP() NULL,
     C2_DAY_DT     TIMESTAMP() NULL
)

check the source data and use the correct function eg TO_DATE(SRC.DATE, 'MM?DD/YYYY') use NVL if required.

Error while saving rpd (problen with time dimension)

Hi all.
I have business model that have no errors/warnings during "check consistency" procedure. But when I save rpd i get error:
-->The Physical table '***' which is part of a time dimension, is also used in the logical table 'XXX', which is not part of any time dimension.
Does someone know how to fix this?

go to time dimention -> right click -> check the box: time dimension

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

How to know on which time dimension level we are ?

Hello,
I would like to know is there a variable or a mean to know dynamically on which time dimension level we are in order to use that in a CASE WHEN clause ?
By using a sort of aggregation tables in which one of the column contains the name of the level, I could know on which level I am but I can't use that for drill down. What I mean :
Tab1 :
'Year' as typelevel, year
Tab2 :
'Month' as typelevel, year, month
In BMM, I have made one logical table with as Source tab1 and tab2 and as columns typelevel, year and month.
tab1 has in content column the year level
tab2 has in content column the month level.
So when in Answers I retrieve
typelevel, year
the result is : 'Year', 2008
and when I request : typelevel, year, month
the result is : 'Month', 2008, 1
But if I want to drill from year to month in order to have :
'Year', 2008
and then after drill
'Month', 2008, 1
it is impossible as a filter on typelevel='Year' is added on the month level, so it retrieves 0 columns.
If someone has an idea on how to do that it would be very great.
Thanks in advance for your help.

Hi Supriya,
OOTB I think you can use SharePoint designer, but I would suggest custom code to iterate to all pages, and get the lists that are associated with these pages.
http://stackoverflow.com/questions/633633/sharepoint-how-can-i-find-all-the-pages-that-host-a-particular-web-part
another one would be if those lists were never used and you can check for list with empty data.
I would use Get-SPLists to get all of the lists to check for zero items.
http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/15/use-windows-powershell-to-manage-lists-in-sharepoint-2010.aspx
http://sharepointrelated.com/2011/11/28/get-all-sharepoint-lists-by-using-powershell/
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you

Using time dimension in materialized view

Do anybody has an example of using Time dimension in MVIEW?. The time tablke has no relation with oder object (ex. i will join the time table with sales table, which has no relation with each other.
Thanks in advance
Mehdi

Hi
Check the foreign key on the fact table to see how it is related to the time dimension table.
Cheers
David

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

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

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

How to build 2 hierarchies in time dimension

Hi All
I want to know how to build 2 hierarchies in time dimension in SAPBPC 7.5 NW.
thanks

Hi nilanjan chatterjee
thanks for your feedback. please check my time dim below.
we got two financial years.
1. jan to dec ( thats my parenth1)
2. apr to mar ( thats my parenth2)
In usertime id i copied 2008 time ids for fy2009 jan sep and from oct to dec copied 2009 jan to mar time ids.
ID                         Desc            parenth1        parenth2                               Timeid         usertimeid
2009.Q1          2009.Q1          2009.TOTAL                                   20090001
2009.Q2          2009.Q2          2009.TOTAL                                   20090002
2009.Q3          2009.Q3          2009.TOTAL                                   20090003
2009.Q4          2009.Q4          2009.TOTAL                                   20090004
FY2009.Q1     FY2009.Q1                           FY2009.TOTAL                 20090001
FY2009.Q2     FY2009.Q2                            FY2009.TOTAL          20090002
FY2009.Q3     FY2009.Q3                          FY2009.TOTAL               20090003
FY2009.Q4     FY2009.Q4                           FY2009.TOTAL               20090004
2009.TOTAL     2009.TOTAL                                                      20090005
FY2009.TOTAL     FY2009.TOTAL                                        20090005
2009.JAN     2009.JAN     2009.Q1                                        20090100     20090100
2009.FEB     2009.FEB     2009.Q1                                        20090200     20090200
2009.MAR     2009.MAR     2009.Q1                                        20090300     20090300
2009.APR     2009.APR     2009.Q2                                        20090400     20090400
2009.MAY     2009.MAY     2009.Q2                                        20090500     20090500
2009.JUN     2009.JUN     2009.Q2                                        20090600     20090600
2009.JUL     2009.JUL     2009.Q3                                        20090700     20090700
2009.AUG     2009.AUG     2009.Q3                                        20090800     20090800
2009.SEP     2009.SEP     2009.Q3                                        20090900     20090900
2009.OCT     2009.OCT     2009.Q4                                        20091000     20091000
2009.NOV     2009.NOV     2009.Q4                                        20091100     20091100
2009.DEC     2009.DEC     2009.Q4                                        20091200     20091200
FY2009.JAN     FY2009.JAN                    FY2009.Q1                    20090100     20080400
FY2009.FEB     FY2009.FEB                    FY2009.Q1                    20090200     20080500
FY2009.MAR     FY2009.MAR                     FY2009.Q1                    20090300     20080600
FY2009.APR     FY2009.APR                     FY2009.Q2                    20090400     20080700
FY2009.MAY     FY2009.MAY                     FY2009.Q2                    20090500     20080800
FY2009.JUN     FY2009.JUN                      FY2009.Q2                    20090600     20080900
FY2009.JUL     FY2009.JUL                     FY2009.Q3                    20090700     20081000
FY2009.AUG     FY2009.AUG                     FY2009.Q3                    20090800     20081100
FY2009.SEP     FY2009.SEP                     FY2009.Q3                    20090900     20081200
FY2009.OCT     FY2009.OCT                      FY2009.Q4                    20091000     20090100
FY2009.NOV     FY2009.NOV                      FY2009.Q4                    20091100     20090200
FY2009.DEC     FY2009.DEC                        FY2009.Q4                    20091200     20090300
thanks

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

Time Dimension Type allows different values in attributes - Bug or Feature?

Not sure if this is a bug or a feature.
But if one has multiple hierarchies on a Time dimension. You have the ability to specify different values for member attributes in different hierarchies.
Example.
Hierarchy A has MIN_ID for it's Member and uses MIN_END_DATE for it's END_DATE
Hierarchy B has MIN_ID for it's Member and uses SESS_END_DATE for it's END_DATE
As per this post and David Greenfield's comment:
Dimension Sort issue when multiple mappings for different hierarchies
"Are you attempting to map the same attribute, SORT, to different columns in the two hierarchies? Put another way, do you expect the same member to have different values for the attribute in the two different hierarchies? If so, then this is a problem since a member must have the same value for the attribute regardless of the hierarchy."
Unlike a user dimension, a time dimension appears to allow this and it appears to work as intended. Is the behavior in this case intended to be different between a user and time dimension?

I think that this is not a bug. There is an incompatibility in design which prevents you from using the same attribute differently for both hierarchies.
NOTE: Unlike parent relationship which depends on <dimension, dimension hierarchy>, Dimension Attribute is dependent on <dimension> alone, not dependent on <dimension, dimension hierarchy> combination. Hence it can only take on 1 value for 1 dimension member.
I think that the time dimension only appears to allow this. The key thing to check is for Time Dimension members which are common to both the hierarchies. Only one of the mappings will take effect (usually the hierarchy which is loaded last will remain in the aw/usable for queries, reports.. it would have over-written the earlier attribute value loaded as per the earlier hierarchy load).
Visualize a dimension as a long list of members which are built up contiguously on a per hierarchy, per level process using the mapping information saved. Once a member is defined (created) via Hierarchy A, it wont be created once again while loading Hierarchy B but is instead updated or redefined based on Hierarchy B's mapping info.
Assuming the dimension load attempts to load Hierarchy A first and then Hierarchy B,
* Dimension load for Hierarchy A will define the various members using MIN_ID and set the END_DATE attribute to value=MIN_END_DATE
* Dimension load for Hierarchy B will re-define the various members using MIN_ID and re-set or over-write the END_DATE attribute to value=SESS_END_DATE
* In this case, it looks like all members are common for both hierarchies (as both members are mapped to same column MIN_ID) and you would end up with END_DATE=SESS_END_DATE.
Actually whether all members are common to both hierarchies or not depends on the quality of data in your snowflake/star table: if parent level for Hierarchy A as well as Hierarchy B is setup fine then the members will be same set (overlapping in whole). If some rows for MIN_ID have parent column for Hierarchy A setup correctly but parent column for Hierarchy B =null or invalid value then that member will exist in Hierarchy A alone and would contain END_DATE=MIN_END_DATE as the corresponding update along Hierarchy B would fail due to hierarchy data quality issues (join from current level to parent level).
As regards a solution to your problem, you should not use the same attribute "SORT" for dual purpose (both hierarchies). Instead define attributes SORT_A and SORT_B and make them enabled for Hierarchy A, Hierarchy B respectively and map/use them appropriately in your reports.
HTH
Shankar

Checking Time Dimension

Similar Messages

Maybe you are looking for