Modifying Existing Time Dimension

Hi All,
Presently I have a Time Dimension and a Fact table which has a FK to this Dimension. The Time Dim has a level upto hourly values.
Now it's in production and I need to change the Time Dim to take on minutes 'cause some reports need minutes.
1. So what is the best way to go about this?
2. Is it better just to add another extra field which has the required date, in the fact table?
3. How can the existing data be easily ported to the new Time Dim(if it has a minute-level)?
Thanks,
Justin.

I am wondering how you implemented the time dimension which only has a level up to hourly values. Do you mean the time dimension only has 24+1 = 25 rows? Usually the time dimension is separate from the date dimension and its lowest level values are minutes or seconds, depending on the business requirements. Therefore the time dimension should have 24X60 + 1 or 24X60X60 +1 rows.
The solution is depended on what you want.
My suggestion is as the follows:
1.     Create a new time dimension with the desired lowest level values (minutes or seconds).
2.     Create or modify the foreign key of the fact table to point the new created time dimension.
3.     Modify the ETL mappings.
4.     Option 1: If you want the new functionality available for the existing rows in the fact, you have to reload the fact no matter which approach you use.
Option 2: If you only want the new functionality available for the subsequent refresh load, you can modify the foreign-key values pointing to the old time dimension to the new time dimension, using the rule XX --> XX:00 or XX --> XX:00:00 (where XX is the hour number in the old dimension). In the subsequent refresh load, map the foreign-key values to the actual time.
Maybe other else can provide better solutions. IF so, please let me know.
Good luck!

Similar Messages

Modifying the time Dimension in OWB10G R2

Hello,
I've used the time-dimension wizard in OWB10G R2, but I am encountering some problems. Let me explain:
When you start with the wizard, it gives you the choice of a normal hierarchy based on year and/or quarter and/or month and/or day OR a week hierarchy, based on week and day. But I need a time dimension based on year, month, week and day. So I created a normal hierarchy time-dimension based on year, month and day and tried to alter it, by adding a week as an attribute (and level etc.).
So far no luck. I can't change the dimension, once it is created. Same for the other way around: create a weekbased hierarchy and ad month and year to it as attributes.
And now my question: Am I overlooking something? Or is it just a case of bad luck and do I have to build the time dimension myself by hand (not that much of a work, but still a pity of the wizard)? Or is there an other way around to fix this problem?
Regards,
Ingmar

Ingmar,
I just read your post and I am trying to accomplish the same thing with the time dimension - can you help me or direct me to another post that can?
After I create the time dimension with the wizard, I go back in via the Object Editor and I see the check box on the Levels tab and I have checked the Calendar_Week and all the attributes pop up, so far so good, then I navigate next to the Hieararchies tab and I don't see that the Level for Calendar_Week has been added?
How to I get a time dimension that has a single hierarchy that roles up as follows:
day ----> week ----> month -----> quarter ----->year
thx
monalisa

OWB 904 - problems creating time dimension

I'm using Oracle9iR2 DB and OWB 904. I have not much experience with OWB 904 yet and problems with creating the time dimension.
I tried to figure out the example which comes with OWB 904 and did everything as it is written in the readme.txt file:
1. loaded the time table functions owb_time_seq.sql and owb_time.sql in my runtime user schema
2. imported the owb_bp_time.mdl file into my design repository, which created the demo project 'OWB_BP'
The problems which I have with this demo are:
1.) I get warnings when I validate the mappings (TF_TIME_MAP):
VLD-1002: Mapping object T_TIME is not bound to a repository object.
VLD-1004: Column length of L_DAY_NAME is longer than the target column length.
VLD-1004: Column length of L_MONTH_NAME is longer than the target column length.
VLD-1004: Column length of L_QUARTER_NAME is longer than the target column length.
VLD-1004: Column length of L_YEAR_NAME is longer than the target column length.
VLD-3260: No Output Attribute name is specified. In this case, the attribute’s physical name will be used.
VLD-1123: Missing location information for Module WAREHOUSE.
VLD-1115: Commit frequency is defaulted to Bulk Size.
I know how to solve the errors VLD-1002, VLD-1004, VLD-1123 and VLD-1115 but I have no idea how I should solve VLD-3260 and VLD-1002, because reconcile outbound is not possible for the T_TIME dimension.
2.) When I try to import the table function
TIMEDATA (IN VARCHAR2, IN NUMBER) return TABLE
from the runtime user schema into my design repository I get the error message: Argument Data type is not supported.
3.) I cant deploy the mapping TF_TIME_MAP.
Is it possible to use the table function from the demo to create a time dimension and to import it into my own project? My aim is to create a bean compliant time dimension and I want to know what I have to bear in mind to accomplish that. The OWB904UsersGuide didn't give me enough information, therefore I'm asking if you can help me out.
Thanks in advance,
Dirk

Dirk,
The way you should approach the time dimension is following:
- Run the SQL scripts into your target schema (you already did).
- Import the MDL file (you already did).
- Copy and paste the times dimension into your own project to be able to use it.
- Copy and paste the mapping you want to use to your own project.
- If necessary, modify the times dimension according to your needs; change the mapping accordingly.
- Open the mapping, do a right mouse click on the time dimension and select 'Reconcile inbound'. Select matching strategy to match by bound name.
We do not currently support the table function as an object in the metadata repository. I.e. if it exists at runtime then you can call it (as the time dimension load mappings do).
With the objects in the target schema you should be able to deploy the mapping.
Thanks,
Mark.

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

Add Audit Columns to the Dimension and Fact tables (Created & modified date Time)

Hi All,
I am new to SSIS , I have to Add Audit Columns to the Dimension and Fact tables (Created & modified date Time) of the package.
Please let me know the best and easy way through which I can implement the same.
If possible suggest some real time example or link where I can find the same
Regards,
Vipin jha
Thankx & regards, Vipin jha MCP

You can simply use ALTER TABLE ADD.. syntax to add the columns if the tables already exist.
You can generate a single script for all tables using INFORMATION_SCHEMA.TABLES view
You can make then of NOT NULL type and set the default value to GETDATE()
In addition you can also have a Audit Trail trigger for UPDATE to make sure Modified date gets updated correctly on each update if not passed explicitly.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

How can I modify Time dimension to create a Top member above year members ?

Hi experts,
I would like to modify Time dimension to add a Top member above year members.
I already did a test:
I added a member in Time dimension which is the parent of all year members. I granted it these property values:
- ID = TOTAL
- EVDESCRIPTION = Total
- LEVEL = TOTAL
- HLEVEL = 1 (and I added 1 to all the other members)
- TIMEID = 10000001
All other properties were left blank for this member.
I processed the dimension. It went well. But when I tried an evdre in BPC excel it failed.
Any idea of something missing ?
I am working on SAP BPC MS 7 SP4
Thanks for your help
Ludovic

Hi Petar,
Thanks for your answer. No doubt that we could solve the issue using on of the way you suggested.
However, even though I had the evdre issue right after applying time dimension modifications, it occurs that the evdre issue was not due to time dimension modifications. I tested it better and I can tell that using "total" as a level works.
Best regards,
Ludovic

OLAP time dimension - how are the weeks allocated

Could someone please help me understand what logic Oracle uses when one makes use of Oracles OLAP time dimension based on weeks.
I am use Oracle OLAP 11.2
I have a Time dimension that has the following hierarchy:-
YEAR
QUARTER
MONTH
WEEK
For calculating the weeks ID I make use ISO week and year i.e. IYYYIW
For calculating the end date I use the following:- NEXT_DAY( l_date, 'MON' ) -1
i.e. the weeks end date is the Sunday.
According to me this is the required result.
Problem is that for some months there are 3 weeks allocated which makes no sense to me.
I cannot understand the logic used in allocating the weeks.
The following is an example:-
the following weeks were allocated to the month February
201306 (end date= 10-2-2013)
201307 (end date= 17-2-2013)
201308 (end date= 24-2-2013)
but the following week was allocated to January which makes no sence to me,
I would have expected it to be found in February
201305 (end date= 3-2-2013)
Week 201309 (end date= 3-3-2013) was allocated to March which according to me is correct..
Another example is week *201030 (end date= 1-8-2010)* that is allocated to July while I would have expected that it should be August.
I would have thought that it uses the end date that is placed in the mapping to determine the month to place it in.
Could some one please explain what the reason for this could be.

Oracle OLAP model/design (in this case, at least) cannot compensate to coverup existing flaws in the relational model/design.
I dont think this is a valid hierarchy even considering relational model/design.
Weeks do not fit in below Months (calendar months).
You can force fit them by making Weeks the source of truth and making all Months logical Months like "Business Month", "Business Quarter", "Business Year" etc. which will be composed of whole weeks but differ significantly from the calendar definition of Month, Quarter, Year etc.
You are better off modeling time as composed of two hierarchies:
H1: DAY -> MONTH -> QUARTER -> YEAR and
H2: DAY -> WEEK
Alternately if you dont want to introduce DAY level (lower granularity), you can split up the Time dimension into 2 different dimensions. And also modify your star schema to add an additional time dimension key to fact table - one key pointing to WEEK and another pointing to MONTH (independently).
TIME_MO: MONTH -> QUARTER -> YEAR
TIME_WK: WEEK
The fact data will need to be split up to correctly identify the coirrect MONTH-WEEK combination for the relational record.
E.g:
Fact table should have 2 dimension Fks for WK_KEY as well as MO_KEY so that a fact figure of 1000 evaluated over 7 days is split up into 300 from 29-31st of previous month and attached to MO_KEY of previous month and another record of 700 covering days from 1-4 and recorded/tied to same WK_KEY but next month (next month's MO_KEY).
HTH
Shankar

Getting error while deploying a cube with time dimension

Hi,
I created a time dimension using WB with Cal yr and day heirarchy. Designed a cube using both and tried to deploy it. I got the following error.
Appreciate your help..
Name
Type
Status
Log
TIME_CUB1
Cube
Success
VLD-0001: Validation completed successfully.
TIME_CUB1
Description : Runtime User : OWB_REP_OWNER Started : 2006-12-13 15:37:17.0
Name
Action
Status
Log
TIME_CUB1
Create
Error
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 394
ORA-06512: at line 5

Hi,
I'm having problems to deploy this cube (this was the origin of my problem), when I change it to "Deploy Data Object Only", It don't generate code and the cube is not created. This is what I get:
-- Product : Oracle Warehouse Builder
-- Generator Version : 11.1.0.6.0
-- Created Date : Wed May 12 08:41:59 CST 2010
-- Modified Date : Wed May 12 08:41:59 CST 2010
-- Created By : edennis
-- Modified By : edennis
-- Generated Object Type : TABLE
-- Generated Object Name : FACT_TMP_SALDOS
-- Comments :
-- Copyright © 2000, 2007, Oracle. All rights reserved.
WHENEVER SQLERROR EXIT FAILURE;
Ideas?
Thanks for your help!

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 Consistency Error in RSRV - Need Help

Hello,
I am having a problem when I run RSRV on our 0ECCS_C01 cube. We have extended the time characteristics to include posting period (0FISCPER3). The only problems RSRV finds is when 0FISCPER is period 0 and 0FISCPER3 is 0. For some reason, these are being flagged as inconsistent. I think this is causing negative performance on our queries because I feel partitioning may not be getting used from some research I've done due to this inconsistency.
Here are the errors I am getting from RSRV:
1. Record with the DIMID 410 contains non-fitting time characteristics
Message no. RSCV053
Diagnosis
The data record of the time dimension table with the described DIMID contains values for time characteristics that do not fit together.
2. This DIMID is used by 9860 records of the fact tables
3. No master data found for characteristic of test described subsequently
Message no. RSCV083
Diagnosis
No master record exists for a characteristic used in the time dimension. The characteristic is one of the characteristics described in the following message with one of the SIDs named there or it is the fiscal year variant that was derived from one of the characteristics.
4. Time characteristic 0FISCPER value 132000000 does not fit with time char 0FISCPER3 val 0
Message no. RSCV054
Diagnosis
The described values of the specified time characteristics do not fit together.
How exactly can I get these time characteristics to "fit" properly? Will it require a data reload?

hi,
did u get answer to ur problem.
thanks.
Raju

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

Updating master data for time dimensions from front end

Hi Experts,
I am sure this must be handled in a very straight forward way. Just want to know the best practice here. We are working on a copy of appset and want to completely revamp the time dimension papers as per client's fiscal year which is april to march every year.
When we have deleted all the existing memebers from the time dimension master data from BPC front end and replaced with new memebers, the task is getting completed successfully.
But when I check back in BI for the master data, it has not replaced all the existing members. How best to handle this?
The transaction data is deleted from all the application cubes. Are there any checks to be performed?
Thanks,
Santosh

Closing the thread as I could not replicate the problem. The problem is resolved.
Thanks,
Santosh

Performance Point Filter Scorecard by Time Dimension (without Time Intelligence)

Hello,
I use Performance Point 2010 and want to build a Performance Point Dashboard with Scorecard. My requirement is to provide a List of Years as a Filter for a Scorecard.
In the Scorecard I have a KPI which I want filter by Time Dimension. I can do this when I use "Time Intelligence" and "Time Intelligence Connection". But I want to use the "Member Selection Filter" to filter the Scorecard
KPIs by Years (Selected from a List).
I created a "Member Selection Filter" with certain Time Dimension and put Filter to a Dashboard. In my KPI Mapping Source I added a "new Dimension Filter" and choosed the same Time Dimension as
in the "Member Selection Filter".
When I try to connect the "Member Selection Filter" to my Scorecard, I can only choose the "Curent Date Time". As I know "Current Date Time" have to be used when Time Intelligence Filter is in use.
How I have to connect the Scorecard with the "Member Selection Filter"?
Thank you very much

Hi ShebUK,
I don't think we can achieve this requirement on the front end, but you can discuss this issue at the following forum:
http://social.technet.microsoft.com/Forums/en-US/home?category=performancepointserver
I'm not familiar with PerformancePoint Services and not sure that we can implement linked dimension to achieve this. A linked dimension is one that exists in one Analysis Services database, but reused in another Analysis Services database of the same version
and compatibility level. For more information, please see:
Define Linked Dimensions: http://msdn.microsoft.com/en-us/library/ms175648.aspx
Hope this helps.
Regards,
Elvis Long
TechNet Community Support

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

Duplicate time dimensions

Hello all
I think I have a simple requirement but I don't how it works :
I have some dimensions and a fact tables. In my fact table, I have 2 foreign key on my time dimension.
When I import my tables and check consistency, I have errors : "duplicate foreign key. Delete it" (don't remember full sentence)
That is the first point that I don't understand. Why can I not have more than 1 foreign key ?
The second point is how to do to have 2 time dimensions. In the BMM, I duplicate my time dimension. But which join do I choose ? I tested with foreign key and complex join (and 2 or 1 foreign keys in physical) and I always have the same (wrong) result.
So can anyone explain me how to configure both physical and BMM joins to use a dimension more than 1 time (without create a new physical dimension of course)
Thanks

Hi,
Create Alias tables (since they are playing different roles) for time dimension in the Physical layer and join that with your fact using physical joins.
After Importing to physical layer, if duplicate keys exists, delete the duplicate keys.
In this scenario two keys will be exist on the fact for the time dimension, delete those and create the joins between the aliases.
Thanks,
Vino

Modifying Existing Time Dimension

Similar Messages

Maybe you are looking for