Time dimension question

Hi,
I just created a time dimension from a table that contains all the info I need, Once processed, I went to the browser to finalise the viewing, I have a time period from 2009 to 2025 and once I expand the levels, I see a level unknown right under the
year 2025, the table I use for this dim is not missing any rows at all, all the columns I need are properly populated, no missing info at all.
What can cause that and how to suppress this unknown level
Thanks

Hi a,
Analysis Services has a built in member for each dimension called “Unknown.” This is to simplify the process of dealing with facts that have the property of Unknown for a particular dimension. If a dimension member comes to the
fact table after failing a lookup in the SSIS package and contains a null for the surrogate key, Analysis Services assigns it to this special Unknown Member and moves forward.
The dimension has a property called UnknownMember that describes the usage of this unknown member. It can be set to Visible, Hidden, or None. Next, the dimension member set with the usage of Key has a property called NullProcessing
that is set to UnknownMember. You can supress the visibilty of Unknown member in this way..Hope this helps
Regards
Venkata Koppula

Similar Messages

Universe Design Question - Time dimension

Hi,
Please help me with universe design question here.
I have to make line graph
Y- axis time dimension hh24:mi:ss
y - axis Date dimension YYYYMM
The data is like this
progname end_date
abcd 2011/01/23 13:01:20
abcd 2011/01/24 13:30:20
abcd 2011/01/25 13:34:20
abcd 2011/01/23 13:34:20
abcd 2011/01/25 13:45:20
abcd 2011/01/2614:34:20
I need to take time portion of each month and take average of it and that is printed on graph.
I just wonder how I get average of time. The tool seems like can not get average of time as this is not a number.
Then I converted time portion into seconds and did the average but my requirement is to show time on line graph not in seconds.
Please give some idea.
Thanks.

Hi Afzal,
I know how to segregate the date part and the time part. I just wonder how I get average of time. The tool seems like can not get average of time as this is not a number.
Then I converted time portion into seconds and did the average but my requirement is to show time on line graph not in seconds.
Please give some idea.
Thanks.

Populating the Time Dimension

Ok, the Oracle Enterprise Manager was kind enough to automatically create the often used Time dimension for me. It even created the associated look up table for me.
Question:
Is there a facility/function/feature that populates the weeks - month - year levels in this new lookup table or do I have to do it "by hand"?
Thanks for your time.
GGA

Reposted.

Slicer Time Dimension Issue with Cube Functions

Hi,
Hoping someone can help me figure out right approach here.
Summary:
Using Excel 2013 connected to a SSAS cube as data source, and cube functions with slicers to create a dashboard.
Have following time dimension slicers; Fiscal Year, Fiscal Quarter, Fiscal Month, Fiscal Week & Date, that are used to slice data based on user selection, along
with a sales measure.
Below is example of Slicer name and CubeMember function for each:
Slicer_Fiscal_Year:
=CUBEMEMBER("Cube","[Date].[Fiscal Year].&[2015]")
Slicer_Fiscal_Quarter:
=CUBEMEMBER("Cube","[Date].[Fiscal Quarter].[All]")
Slicer_Fiscal_Month:
=CUBEMEMBER("Cube","[Date].[Fiscal Month].&[201408]")
Slicer_Fiscal_Week:
=CUBEMEMBER("Cube","[Date].[Fiscal Week].&[201509]")
Slicer_Date:
=CUBEMEMBER("Cube","[Date].[Date].[All]")
Problem:
What I am trying to do is to build a table with cube functions that takes the lowest grain of the slicer time dimension selected, shows the current member, plus
the prior 7 so I can have an 8 period trending view table that I will build a chart from. In the above example that would mean that it would look at Slicer_Fiscal_Week since that is lowest grain that has an attribute other than All, and then show me the prior
7 periods. In this case 201509 means Week 9, so I would want to show in table Week 9 back to Week 2. But if Slicer_Fiscal_Week was set to All, along with Slicer_Date, then Fiscal Month would be lowest grain, so I would want to show Fiscal Months from August
(201408) back to January 2014. I know how to use CubeRankedMember to pull the value from what is selected in the slicer, the problem is figuring out how to pass the lowest grain time dimension so that I can use lag or some other MDX function to get the previous
periods.
Any help on this would be greatly appreciated.
<object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{28593A5C-70C0-4593-9764-80C76B51795C}"
/></object>

Hello,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

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

A few simple (?) dimension questions...

Hi, I have a few really simple dimension questions that I just can't figure out in OWB (which I'm just now starting to play with):
1) I'm trying to create a dimension that has no levels or any hierarchy. In the BI tool, I just want this dimension to act as a "pick list" for one of 8 values (DW data snapshot dates for the last 8 weeks...) Users won't summarize by this dimension, or ever have more than 1 week selected at a time. How can I set this type of dimension up?
2) Somewhat related to #1 - just to get something working, I set up a "time in weeks" dimension not as a time dimension, just as a normal user dimension. I then added a single "weeks" level with a surrogate key (using "key" instead of "id"), short desc (as the business key), and long description. Set up a mapping from my source table, everything worked fine. The strange thing I've notcied is that the relational table produced has both a "week_key" column and a "dimension_key" column. How can I get rid of the "dimension_key" column - its just an exact duplicate of the lowest level key column? Note - we will have a dimension table with over 1.3 BILLION rows in our warehouse - so duplicating this column does add a significant amount of overhead - this isn't just an academic problem.
3) related to building this "test" dimension - my source table has 8 records in it. Whenever I run the ETL to populate the dimension table, the surrogate keys end up being key values 9 - 16 instead of 1 - 8. Note this is even if I reset the sequence number to 1 before I start, etc. My understanding is that Oracle uses a variable width number field when storing data - so having this dimension with values 1-8 instead of 9-16 saves approx a byte for every fact table record (which we're predicting will be in the range of 20 - 50 BILLION rows). How can I force the dimension to start numbering at 1?
Thanks in advance,
Scott

Hi
Reg #2, I do not think we can get rid of the "dimension key". It looks like OWB is creating this column as a default Primary Key and hence is not possible to remove this. May be if we build the base Table for dimension as a normal relational table, which will allow us to define our own keys, and then build the "Dimension" using AWM on this relation table may resolve the issue of having duplicate primary keys. Its only a thougt, have not tested though.
rgds
Mahesh

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

Time series questions - how to do AGO function for prior year end

Question on how to perform the following calculation in OBIEE:
I need to create a time series calculation that will calculate a metric as of Dec prior year. For example, my users will select Mar 2010. I want to show the amount for Mar 10 as well as the amount for Dec 09. If the select Jun 10, I will show them the amount for that month as well as Dec 09.
Is there a way to do an AGO function that will give me this value? I can't use a filter calculation on my column because filter on the period will exclude these records

Thanks John. Your suggestions seems promising but I'm having issues when I tried it out. I am receiving the following error message:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22046] To use AGO function, the query level ('Fiscal Period, Prior Fiscal Year End Date') must be a static level. (HY000)
What I did was create a new level off my Fiscal Time dimension which is a child of Total. I tried creating my AGO calculation using this level but received that error message in Asnwers. Any ideas on what I may be doing wrong?

Time Dimension, i don´t bind the fact dimension and the time dimension

Well i don´t know why my fact table don´t bind with the time dimension, i create a time table in the data base and change the key to int32 for example year(date)*10000+month(date)*100+day(date), and create to similar in the fact table, and
this attributes binding, when i process the dimension all result without problems, after i process the cube and all result without problems, but when i try to deployment the browser, the measures in all years are equals, please help me

Hi franciscofelipe,
According to your description, you find the measures shows all same value for all years of time dimension. Right?
In this scenario, since your change the key of your time table into an integer, when pulling this dimension out in Browser, the measure will only regards those members as numeric value instead of date so that is will show an aggregate value. Even
all the members are displayed properly in your dimension. So please change the attribute type into appropriate date type.
If you have any question, please feel free to ask.
Regards,
Simon Hou
TechNet Community Support

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.

Data warehouse, time dimension

Dear folks,
My boss asked me an interesting question, but I couldn't answer, because I'm not an Oracle expert, I'd rather describe myself as Cognos developoer.
We have a ROLAP data warehouse, and there is a time dimension table, the primary key column has type number. He asked me, why is it worth having a number primary key, and not having the date itself as primary key, because Oracle converts dates to numbers too... So what do you think, what's the difference, wich is the better option?
Thanks you in advance, and sorry for my bad English.

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.

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

Display all dates between date range (Time Dimension left outer join Fact)

All,
I have done some searching around this issue but within all the posts regarding date variables, date prompts and date filtering I haven't seen one exactly answering my issue (maybe they are and I just dont have my head around it correctly yet).
My report requirement is to allow a user to select a start day and an end day. The report should show all activity between those two days - AND display 0/null on days where there is no activity. That second part is where I am getting hung up.
The tables in question are:
TimeDim
EventFact
CustomerDim
My BMM is setup as follows:
TimeDim left outer join EventFact
CustomerDim inner join EventFact
If I run a report selecting DAY from TimeDim and a measure1 from EventFact with day range 1/1/2010 - 12/31/2010 .. I get a record for every day and it looks perfect because of the left outer join between TimeDim and CustomerDim.
But .. if I add in a field from CustomerDim, select TimeDim.DAY, CustomerDim.CUSTNAME, EventFact.MEASURE1, OBIEE only returns records for the days that have EventFact records.
This is due to the fact that the TimeDim is still outer joined into EventFact but adding in CustomerDim makes OBIEE setup an inner join between those tables which then causes only data to be returned where EventFact data exists.
There is a way around this in this simple case and that is to define the relationship between CustomerDim and EventFact as an outer join as well. This will give the desired effect (but an outer join between these two tables is not the true relationship) and as I add additional dimensions and add additional logical sources to a single dimension in the BMM it gets complicated and messy.
Ive also messed with setting the driving table in the relationship, etc.. but it has not given the desired effect.
Has anyone ever encountered the need to force display all dates within a specfied range with a fact table that may not have an entry for every date?
Thanks in advance.
K
Edited by: user_K on Apr 27, 2010 11:32 AM

It worked!!!* Even my time drill downs and date based filtering still work!
That is awesome. Never would have thought of that intuitively.
Now, just need a little help understanding how it works. When I run my report and check the logs I can see that two queries are issued:
Query 1: Joins the fact table to all the associated dimensions. I even changed all the relationships to inner joins (which is what they truly are). And calculates the original measure. If I copy and paste this query into sql developer it runs fine but only returns those rows that joined to the time dimension - which is what was happening before. It is correct but I wanted a record for every time dimension record.
Query 2: Looks like the following:
select sum(0)
from timedim
where date between <dateprompt1> and <dateprompt2>
group by month *<--* this is the time dimension level specified in Query 1, so it knows to aggregate to the month level as was done in query 1
Final Question: So what is OBIEE doing ultimately, does it issue these two requests and then perform a full outer join or something to bring them together? I couldn't see anywhere in the log a complete query that I could just run to see a similar result that I was getting in Answers.
Thanks for all the help .. Id give more points if I could.
K

Time Dimension with Hourly base level

Hi all
I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
02-SEP-10 10:00:00 AM
02-SEP-10 11:00:00 AM
To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table. My questions are:
1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
Cheers.

Thank you Szilard and Adnan for the very prompt and informative responses.
I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
FYI, I have not created any indexes on any of the attributes.
My platform is:
11.1.0.7.0 DB
11.1.0.7.0B Client

Where can I get the TIME dimension example files?

Where can I get / download the following files for creating this time dimension?
They are only in OWB R1.
[OWB Home]\owb\misc\time\readme.txt
[OWB Home]\owb\misc\time\owb_bp_time.mdl
and
[OWB Home]\owb\misc\time\owb_time_seq.sql
[OWB Home]\owb\misc\time\owb_time.sql
Thanks for help.

Hi,
Not sure if this answers the question, but in 10.2 you don't need these files any longer. Simply create the time dimension and it will load data for you (it acts as a data generator).
JP

Time dimension question

Similar Messages

Maybe you are looking for