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.

Similar Messages

Setting date ranges when Time dimension includes Period instead of Month

I hope I am missing something simple here - we are on OBIEE 10g, and I have a Time dimension defined as follows:
Year > Quarter > Period > Week > Day
A "period" is not equivalent to a calendar month - a period can include either 4 or 5 weeks, and always starts on a Sunday. Fiscal years start on the first Sunday in July.
I need to create a graph that shows Total Sales for the previous 13 periods (not including the current period). This needs to be a rolling 13 periods based on the current period.
Since this is Period and not Month, I am unable to use the Month(CURRENT_DATE) functionality. Do I need to have repository variables defined for the current period? Is there another way to calculate what the current Period in my Time dimension is in a filter SQL?
So I want to do something like "Where period between [current_period - 14] and [current_period -1] as the filter for Period.
Thanks in advance for any assistance.
Rhonda

Sorry about that...
Periods are 1-12 (numeric).
Period 4 of FY 2012 for example has a begin date of 10/02/2011 and end date of 11/05/2011.
Right now we do not have unique combos created (like 4/2012, 5/2012, etc) so to get a unique value I have to specify both a year and period.
So on my dashboard today I will need to create a graph that covers FY2011 periods 6-12 and FY2012 periods 1-6 (translates to 12/5/2010 - 12/31/2011).
I haven't created repository variables before, but as the Period parameter will be used often I guess I will find out how.
Thanks in advance for the help.
Rhonda

OBI 10g merge 2 time dimensions on the same table/graph in analysis

Hi,
My problem is: I have 2 different analyses (working fine) (using OBI 10g), they both use a different time dimension:
time_dim_1 | fact1
time_dim_2 | fact2
I want to merge them to have something like the following:
time_dim | fact1 | fact2
What I managed to get so far is something like this:
time_dim1 | time_dim2 | fact1 | fact2 (with, if we suppose there are 12 rows in time_dim1 and time_dim2, 12*12 = 144 rows instead of just 12)
Here is some more explanations about how I set my repository:
My fact table "issues" is made of the following columns:
issue_id, issue_type, issue_create_date, issue_end_date
I also have a table "calendar" with year, quarter, month and full_gregorian_date.
In the physical layer I created 2 aliases for the "calendar" table to join with the fact table using "issue_create_date" and "issue_end_date".
In the business model I created the 2 related time dimensions.
Everything is working fine so far, I was able to get 2 different analyses :
- time dimension (joined with "issue_CREATE_date") | count of issues (with aggregation rule "count" on issue_id)
to see how many new issues are CREATED through time (are there more issues created or less)
- time dimension (joined with "issue_END_date") | count of issues (with aggregation rule "count" on issue_id)
to see how many new issues are ENDED through time (when are more issues ended)
What I want is a third analysis like this:
- time dimension | count of created issues | count for ended issues
Thanks for your help.
Florence

did you set the content level as well?

Date and Time dimensions

After reading the following article, I have decided to use SSAS dimension wizard for generating our Date dimension, which creates a DATETIME PK.
http://www.made2mentor.com/2011/05/date-vs-integer-datatypes-as-primary-key-for-date-dimensions/
I have also created a separate Time dimension as granularity of an hour is required.
The Time dimension is very simple and only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR).
DimTime(TimeKey, TimeInHours)
Our Fact table will now have a link to both the Date and Time dimension using the PK's.
Our analysis is required by hour, day, week, month and year.
My query is; Will this current structure cause any problems when creating MDX scripts to analyse our data (i.e. drilldown and rollup queries) Hour - Day - Week - Month - Year

Hi Darren,
According to your description, there a day and hour granularity in your fact table, so you want to a hierarchy like Hour - Day - Week - Month - Year, right?
In your scenario, you created a time table that only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR). We cannot create a Hour - Day - Week - Month - Year hierarchy without ant relationship between date table and time table. As per my understanding,
you need create a foreigner key in time table, and join those table in the data source view, then you can create such a hierarchy. Here are some links about create time dimension, please see:
http://www.ssas-info.com/analysis-services-articles/59-time-dimension/1224-date-and-time-dimensions-template
http://www.codeproject.com/Articles/25852/Creating-Time-Dimension-in-Microsoft-Analysis-Serv
Regards,
Charlie Liao
TechNet Community Support

Multiple Fiscal Calendars Displayed in Subject Area Time Dimension

Hi all,
Thanks for taking the time to review my post.
Environment
Oracle BI Applications 7.9.6 Financial Analytics
Oracle E-Business Suite 11.5.10
Query
The Time dimension on my Subject Areas (Financial Analytics) are showing more period data than I expected.
I have configured one Enterprise Calendar (WPG_Calendar) that I set in the DAC parameters - $$GBL_CALENDAR_ID (WPG_Calendar~Month) and $$GBL_DATASOURCE_NUM_ID (4). The warehouse Enterprise Calendar table W_ENT_PERIOD_D is populating with the periods as configured in EBS for that calendar(Jan-09, Feb-0, Mar-09, etc). I noticed that the Multiple Fiscal W_MCAL_PERIOD_D table is also been populated with the Enterprise Calendar data PLUS, the Seeded EBS calendar (JEBE_MONTH_VAT) and a generated Calendar that appears to be a 5-4-5-4 Calendar (Jan-01-09, Jan-02-09, Jan-03-09, etc). The trouble is these W_MCAL_PERIOD_D periods and dates are all coming through in my Time dimensions and make it confusing for the Answers Users when choosing a Time dimension.
Also, for columns W_CURRENT_MCAL_PERIOD_CODE, W_CURRENT_MCAL_QTR_CODE, W_CURRENT_MCAL_YEAR_CODE there are rows with Current, Previous and Next populated that span these different periods as you would expect, but I'm concerned these return multiple rows for Filters Current Fiscal Quater, Current Fiscal Year.
Funnily enough, W_CURRENT_MCAL_MONTH_CODE has nothing populated (NULLs for all rows).
Your comments are most welcome.
Kind Regards,
Gary.

The filtering of the calendar can be done directly on the logical layer.
for the logical dimension "Dim - Date Fiscal Calendar", Logical Table Source "Dim_W_MCAL_PERIOD_D_Fiscal_Period"
set the content as :
"Oracle Data Warehouse".Catalog.dbo.Dim_W_MCAL_PERIOD_D_Fiscal_Period.MCAL_CAL_WID = VALUEOF("MY_MCAL_WID")
and setup the repository variable MY_MCAL_WID to match with your calendar wid.
If your calendar depends on any context then you can use session variable instead of repository variable

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, 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

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

Non standard members of Time dimension

Colleagues,
I have created a Time Dimension which consists of 16 periods instead of normal 12 periods in a year.
When I attach YYYY.P13,YYYY.P14,YYYY.P15,YYYY.P16 to YYYY.TOTAL and send data for the respective periods, the input schedule saves successfully. However, on refreshing the schedule doesnt show any value ofr YYYY.P16 and YYYY.TOTAL figures doesnt seem to include the same. However, when I checked in BW; I did find values sent for YYYY.P16.
Regards,
Shrini

Hello Shrini,
Can you post a screenshot of what your time dimension looks like with these? (With all the properties if possible)
My guess is the properties may be incorrect or the hierarchy may be off a little bit.
It should be something like (using 2014 for example:
ID
BASE_PERIOD
LEVEL
PERIOD
YEAR
TIMEID
PARENTH1
2014.P01
001
MONTH
P01
2014
20140100
2014.TOTAL
2014.P02
002
MONTH
P02
2014
20140200
2014.TOTAL
2014.P03
003
MONTH
P03
2014
20140300
2014.TOTAL
2014.P04
004
MONTH
P04
2014
20140400
2014.TOTAL
2014.P05
005
MONTH
P05
2014
20140500
2014.TOTAL
2014.P06
006
MONTH
P06
2014
20140600
2014.TOTAL
2014.P07
007
MONTH
P07
2014
20140700
2014.TOTAL
2014.P08
008
MONTH
P08
2014
20140800
2014.TOTAL
2014.P09
009
MONTH
P09
2014
20140900
2014.TOTAL
2014.P10
010
MONTH
P10
2014
20141000
2014.TOTAL
2014.P11
011
MONTH
P11
2014
20141100
2014.TOTAL
2014.P12
012
MONTH
P12
2014
20141200
2014.TOTAL
2014.P13
013
MONTH
P13
2014
20141300
2014.TOTAL
2014.P14
014
MONTH
P14
2014
20141400
2014.TOTAL
2014.P15
015
MONTH
P15
2014
20141500
2014.TOTAL
2014.P16
016
MONTH
P16
2014
20141600
2014.TOTAL
2014.TOTAL
012
YEAR
TOTAL
2014
20140001
Check your Time dimension properties, if it isn't that, then I'm not sure. I'm guessing something is different for your Period 16 and your Total properties and that is why it's not displaying correctly on your report.
Thanks,
Alexander

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?

Time Dimension Roll-Up Not Working

Hi Gurus,
We are on BPC NW 7.0 SP04. We are experiencing a strange problem with Time dimension. Even after defining the hierarchy correctly, the values are not being rolled up the hierarchy. Our requirement is to capture data at quarter level and year level. So we have defined the time dimension in following manner:
ID                     EVDESCRIPTION   PARENTH1     LEVEL         YEAR   PERIOD STYLE   MONTHNUM    TYPE   TIMEID           HLEVEL
2007.TOTAL     2007 TOTAL                               YEAR             2007     TOTAL   T3                12                       ACT   20070005        1
2007             2007                   2007.TOTAL   QUARTER     2007     Q1        T2                13                       ACT                        2
2007.Q1             2007 Q1                   2007.TOTAL   QUARTER     2007     Q1        T1                  3                       ACT   20070001        2
2007.Q2             2007 Q2                   2007.TOTAL   QUARTER     2007     Q2        T1                  6                       ACT   20070002        2
2007.Q3             2007 Q3                   2007.TOTAL   QUARTER     2007     Q3        T1                  9                       ACT   20070003        2
2007.Q4             2007 Q4                   2007.TOTAL   QUARTER     2007     Q4        T1                12                       ACT   20070004        2
Here TYPE is a custom dimension property . As the members depict, 2007.TOTAL value should be calculated as the sum of 2007.Q1, 2007.Q2, 2007.Q3 and 2007.Q4 (Quarters and Years are mutually exclusive in our case). But when we maintain data for Q1,Q2,Q3 and Q4, the TOTAL value is displayed as the value of Q4, and not the sum of quarters. We have tried changing MEASURES from PERIODIC to QTD and YTD, with no effect. We thought that it could be a problem with BI, and so built a simple BeX Query on top of the BPC application cube. But in the BEX query, the time dimension is properly aggregated, nd values are displayed correctly. So apparently it is not a problem with BI. In that case, we are missing something in BPC itself. Can any of you identify what it could be? Awaiting answers and Thanking in Advance.
Sincere Regards,
Amitabha

Amitabha,
It's just a problem that a lot of people run into when they are getting used to BPC. Once you see it happen to 10 or 15 people, you can start to recognize it pretty quickly
There are not a lot of examples of this in the Netweaver documentation. I think there are more in the Microsoft docs. However, there is mention of it on this page in the Netweaver documentation: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/65/84d6596224477d80cc8a4392e4c114/frameset.htm]
Ethan

EXPAND INTERMEDIATE NODE OF TIME DIMENSION

Hello!
Can anybody help me? we created members for time dimension like this:
2010.TOTAL
___2010.JAN
______2010.JAN.Q1
______2010.JAN.Q2
If we try to expand, like a column, this dimension in a Report, adding the ID in the "MemberSet", it's only possible for the TOTAL and the Q1 or Q2. But It's not possible for de month directly. In that case we have an EVDRE error "invalid member in <memberset>"
Anybody know what can I do to expand the intermediate node of the tree?
Thank you very much!!
Elena

Hi Elena,
In one of the empty cells, type the below formula
=EVPRO($B$3,$B$23,"YEAR")&".JAN.F1,"&EVPRO($B$3,$B$23,"YEAR")&".JAN.F2,"&EVPRO($B$3,$B$23,"YEAR")&".FEB.F1,"&EVPRO($B$3,$B$23,"YEAR")&".FEB.F2,"&EVPRO($B$3,$B$23,"YEAR")&".MAR,"&EVPRO($B$3,$B$23,"YEAR")&".APR,"&EVPRO($B$3,$B$23,"YEAR")&".MAY,"&EVPRO($B$3,$B$23,"YEAR")&".JUN"
Where B3 is the cell with the application name
B23 is the cell with the time member
EVPRO($B$3,$B$23,"YEAR") is going to fetch the year from the member in the cell B23
Once you have entered the above formula in an empty cell, and if you have 2010.JAN in the cell B23, then your cell should display the value as
2010.JAN.F1,2010.JAN.F2,2010.FEB.F1,2010.FEB.F2,2010.MAR,2010.APR,2010.MAY,2010.JUN
In the memberset of the time dimension, refer to the cell in which you have entered the above formula.
Hope this helps.

How to build dynamic time series for the time dimension

I am planning to build dynamic time series using rule file instead of manually.Please let me know if there is any property need to assign to enable DTS property for TIME dimension.
Edited by: 844104 on Mar 14, 2011 3:37 AM

In the load rule in the dimension build settings you would need to go to the tab dimension definition, choose the time dimension and right click on it. Select Edit properties. If you have not done so, set the dimension to be the time dimension. Then go to the generations/levels tab and set the generation names you need. For example if you want YTD, you would set the generation name to Year, if you want QTD set it to Quarter. You would set the number to the generation number that coorisponds to the generation. The DBAG has the list of names for all of the DTS members.

Time dimension generated differently in 11gR2

Hi,
on generating a new default time dimension, I noticed some strange behaviour compared to the former release which seems to be incorrect.
1. No DIMENSION_KEY column as PK
2. the %_START_DATE columns are defined as business key instead of the %_NUMBER ord %_CODE columns
3. DAY_START_DATE is defined as PK column
I can modify this manually but what is the intention behind?
Is it meant that we should use a date column as FK reference in the cubes instead of the surrogate key.
Very odd !!
regards
Thomas

Hi,
thanks to Google I found Dave Allens excellent paper on [degenerate dimensions|http://blogs.oracle.com/warehousebuilder/2010/05/owb_11gr2_degenerate_dimensions.html].
Now it's a lot clearer to me.
Supposing you will read this, Dave, some more remarks:
1. The date column in the cube is a blessing not only with partitioning. Until now, I used to update the surrogate key of the time dimension to a number of format YYYYMMDD in order to ease my life.
2. But the time dimension table is still used not a mere stub as with DD?
3. I don't understand the context with SCD2. There, I need the DIMENSION_KEY.
4. I have the situation with a fact table containing one row per phone call. The unique phone call ID would be a candidate for a DD. But what would be the advantage to define the stub DD instead of just entering the string ?
Please give some more hints for a better understanding.
regards
Thomas

Time Dimension displays End_Date instead of Long_Description in Analysis

Similar Messages

Maybe you are looking for