"time" dimension modeling quandary

hello folks,
I am looking at a solution to build a model around a date & time dimension that would be scalable, for a tabular model, for a 24/7 business. From a scalability standpoint and number of records (in the hundreds of millions), splitting the date and
time into two distinct dimensions makes the only sense.
The only problem I have that I see, however, is answering questions around dynamic adhoc requests of timeframes, say 'Evenings 6pm-6am', 'Late Evenings 8pm-8am' (which is 8pm one day and the following day until 7:59am), 'Weekends 6pm-6am' (which
is Friday 6pm through Monday 6am), etc...
Is there a relatively robust & fast 'filtering' (within Excel) and/or DAX construct that is manageable, other than creating a compound Date/Time dimension which will create an unmanageably large dimension. (I am trying to bucketize the "time"
dimension in 15 min intervals -- but creating a compound date/time dimension will create an overall dimension that would potentially be 96 times larger than otherwise needed...not very optimal, IMO)
thx much for any thoughts & ideas,
Cos

Is there a relatively robust & fast 'filtering' (within Excel) and/or DAX construct that is manageable, other than creating a compound Date/Time dimension which will create an unmanageably large dimension?
Unfortunately, the answer to your question is probably not what you want to hear. The issue you have is strongly related to the implementation of multiple Time
Zones Chris Webb wrote on this topic nearly a decade ago and there really isn't any better way to achieve it. http://cwebbbi.wordpress.com/2005/11/01/handling-time-zones/
The problem is probably not much better handled in tabular. In one case that I had to address, I only needed to address two time zones. I handled it at the source by cross joining
to a DimTimeZone table and offsetting the Time and Date Keys in the fact based on the difference between the time zone and the UTC time. However, problem with that approach is that the number of relational rows loaded into the multidimensional model was doubled.
My approach would definitely not work with very large tables or the handling of many time zones.
Martin Mason Wordpress Blog

Similar Messages

ER Time Dimension

HI
i have a problem of creating a ER diagram for Time Dimension which consist of tables are DAY , WEEK , MONTH , QUARTER , YEAR and the relationship between those tables
can someone help i need a full solution with attributes for each table

Do you mean you need help designing the actual model or help putting the model in SDDM? (If you need an example Time Dimension model this is not the right forum. You can search online for examples as there are many published.)

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

Disaggregate Periodic Data to Weekly Data (Modeling Time Dimension)

Hi,
We are using BPC MS Version 7.0. Our users plan at period level and I need to disaggregate periodic data to weekly data by looking up weeks from Time Dimension.
Suppose if 2009.Jan has 4 weeks I need the following result
Periodic Data
2009.Jan Acct1 1000$
Weekly Data
2009.Jan Wk1 Acct1 250$
2009.Jan Wk2 Acct1 250$
2009.Jan Wk3 Acct1 250$
2009.Jan Wk4 Acct1 250$
Can we model Time Dimension with two hiearchies to achieves this?
Which is best way to dissaggrate? (Stored Proc or SSIS Pacakge or Script Logic) ?
Thanks
Raj

An easy way to achieve this feature is to have the time dimension be weekly and do the spread on the input schedules before sending.
There would be two EVDREs (one refresh only of monthly data and the other send only of weekly data). The data range of the monthly EVDRE would be input and where the user enters data. The data range of the weekly EVDRE would be formulas (pointing to the monthly data and doing the correct division based on number of weeks in a month). The user is inputting monthly data, but the schedule is sending the weekly values.
The allocation will work as well, but I would suggest to create a weekly input node under each month to capture the monthly value and then spread to the weekly members.
JAN
|---WK Input
|--- WK1
|--- WK2
|--- WK3
|--- WK4

Modelling Time Dimension with Fact Table containing Start Date and End Date

Hi Gurus,
I have a time dimension with Year till Date. I have a fact table which consists of Start Date, End Date, Person ID, Department ID.
How do i design Time dimension with fact table the below scenario
In the dashboard i have start Month and End month as prompts.
In the report i need to display Count(Person ID) > Start Date and < End Date along the trend.
For instance, i have selected Jan-2009 as start date and Apr-2009 as End Date, then i need to display Count(Person ID) of Jan-2009, Feb2009, Mar-2009 andApr-2009.
I Can not connect Time dimension with only Start Date or only with End Date to get the trend along the months.
Please advice on the issue which i am having.

Hi,
Thanks for the response, Infact i tried using Complex join in physical layer. I have considered Time table joined with Fact table, and used >= and took and alias of the Time table and joined fact table using <=. When coming to BMM, i am not knowing how do i design this as if i merge the both the time dimensiona and its alias into single table, values will not be correct and if i make them as seperate columns. i can not show the trend as both are different columns.
Can you please let know where i am going wrong.
Thanks

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

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

Creating Time Dimension

Hi
I have a fact table which has a time data stored in two columns, month_id,year_id.
My fact table looks like this
Sales,Month_ID,Year_ID
How can I model a level based dimension for time for this sort of table ?

You can map the time dimension to a view on top of your fact table as long as the fact is sufficiently dense in time (e.g. there are no missing months). The view would add end date and time span info as appropriate. Alternatively you can define a view that generates dates. The following thread shows the latter approach
populating a date dimension
You can adapt the view in it to derive time info from your fact if you like, but the standalone view is probably easier.

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?

10g - Most detailed table in the time dimension table source is not unique

hi, experts,
I cannot find any solution from google. please help
ERRORS:
BUSINESS MODEL ERP:
[38093] Most detailed table in the time dimension table source 'ERP_YEAR_MONTH' is not unique.

Hi Forreging,
the time key is incorrectly specified at the lowest level. In the 'ERP_YEAR_MONTH' table, have you correctly specified the primary key for the table?
For example, if the lowest level of granularity is MONTH, then the appropriate key is probably a combination of YEAR and MONTH (not simply MONTH).
Hope this helps,
Justin

Non-additive time dimension

Hi, I have an issue modelling the time dimension for one of our facts (employee counts). The problem is this - when a user says "I want to see the count of employees for a given time period" - what they mean is that they want to see the count of employees as of the last day in that time period. i.e. "June employee counts" means employee counts as of 6/30, "Year 2000" employee counts means as of 12/31/2000.
This is very similar to modelling a "ending balance" inventory type problem in OBIEE.
I've solved this (poorly) in OBIEE by changing the aggregation to use "LAST" for the time dimension and "count(distinct(emplid))" for everything else. This works....but....the performance is horrible. If I ask for employee counts for year 2000, it appears to bring down employee counts for all 365 days in the year, then sorting them by date, then throwing away all except the last date. In other words, it brings back 364 days worth of records and then throws them away. This makes the query perform absolutely terrible. A 2 or 3 second query ends up running for minutes.
Does anyone have a different way to solve this issue?
Thanks,
Scott

Hi Christian - agree completely, I just wish OBIEE were smart enough to do the "last" bit on the 2000 row time dimension instead of the mutli-million rows fact table...
I've thought about trying to materialize the measures, but I have a hidden "twist" on my data. In our fact table, I do NOT write a record for each day for each employee. Instead, I only write a record when something on the employee fact changes. So instead of having a hard "date" column, I instead have a "start date" and "end date", and then need to join to the reporting date dimension using a BETWEEN. I do this because most records stay unchanged for long periods of time, so instead of 365 records per employee per year, I average under 3 records per employee per year.
I may give the multiple fact LTS a try, but truthfully I'm a big believer in simplicity (mainly because I'm lazy....) so was trying to find something easier.
And honestly, I'd use a cube if I could, I'm a (very) old Express wiennie.
Thanks,
Scott

Time Dimension 2 PARENTH2 and PRIOR,NEXT

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

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

Valid time dimensions

Hi,
When reverse engineering an Oracle 12c database (using Data Modeler stand alone, 4.1 EA2 using a thin jdbc connection) on some tables valid time dimensions are detected in the database.
This suggests the existence of a period for clause on the table in the database. This is not present, however.
These valid time dimensions are reversed engineered to the model.
Where can these valid time dimensions (named, for example "SYS_STSSAKFUXTO4R$45K8IN#E2LV5") be found in the database ?
And why is it not possible to exclude the valid time dimensions in comparing the model with the database ?
Richard.

Hi,
Thnaks for sorting this out. Please note that this also causes a lot of differences being reported when synchronizing the model with the database (or vice versa).
I assume this behaviour will disappear once the bug is fixed and the "valid time constraints" have been erased form the model.
Is this correct ?
Richard.

"time" dimension modeling quandary

Similar Messages

Maybe you are looking for