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

Similar Messages

Time dimension with Hourly base time periods

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

How to create a working day/holiday attribute in Time Dimension with OWB ?

Hello everybody,
I am trying with no success to create a Time Dimension (with the wizard it would be easier...) with a working day or holiday attribute (0 or 1) to be able to calculate measures only on working time !!! I am totally sure it's possible, obviously, but I found nothing on forums... Could you help me ??
I use OWB 11g, I need all fiscal year/quarter/month/week and all calendar year/quarter/month/week attributes so without any wizard it would be quite impossible... thank you for your help !
NB: of course I know how to define if a day is a working one or not, but I currently can't add any columns in Time dim created with wizard...
Francois
Edited by: [email protected] on Jun 15, 2009 8:24 AM

Hi,
First of all, thanks everyone for your help.
I did several tests this morning.
First of all, i've tried with time_from = 000000 and time_to = 235959 (23:59:59 CET) and the activity has been created with Time From = 04:00:00 and Time To = 03:59:59
Strange no ??
I've also tried with 230000 for time from and time to but the activity has been created with Time From = 03:00:00 and Time to = 03:00:00
I cannot understand the logic behind....
Thanks,
Johnny Baillargeaux

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?

Handling Time Dimensions with Monthly and Weekly analysis

I'm charged to build a cube that can handle both monthly and weekly analysis. They want to be view projections on a weekly grain, but looking back at history they want to be able to tie back to the general ledger at a monthly level.
Is it overkill to load data down to the daily level in order to support multiple roll ups to the month and week? What is the best way to handle this kind of situation?

Having the data come as two different formats (one for months, one for weeks) versus having it come in daily buckets and constructing the months/weeks within Essbase is a call I wouldn't make without understanding the needs first.
Assuming there is no need for data at the daily level, I would weigh the selection based on performace. If the performance is not too outragious, taking the data in at a daily basis would make it easier to reconstruct later. If performance is an issue (or becomes an issue), I would still be tempted to load a daily cube at level 0, summarize the Months and Weeks, and then feed the main cube from there.
So many ways to do this... and for every way there is a reason you might want to try something else. I'd start with the easy approach, and only go "grand" if you have to (meaning: load it daily, summarize in Essbase, and revisit the detail/summary cube split idea if the performance tanks out).

Oracle 9i OLAP Time Dimension

I have got a problem with my cube in Oracle 9i R2 OLAP Services.
I would like to create time dimension with hour level. But, time type have
only day level.How I can create dimension with hour level ?
user cwm2 or OWB

Hi Jiaxu,
Are u a Chinese?
I find that you are learning OracleR2 OLAP.
I just take a project about OracleR2 OLAP.
Could we talk about the technology?
My mail is [email protected]
Best Regards
Chen Qizhuan

TIME Dimension - TIME_SPAN parameter value (constant or decrementing?)

Hi all
For the the 'TIME_SPAN' parameter value in dimension of type 'TIME', should the value be constant for all members in a particular level or should the value decrement over time as the period progresses.
For example, for a TIME dimension having levels DAY > MONTH should the values for TIME_SPAN be:
DAY, DAY_END_DATE, DAY_TIME_SPAN, MONTH, MONTH_END_DATE, MONTH_TIME_SPAN
D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 31
D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 31
and so on...
or like below:
D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 30
D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 29
and so on...
Any assistance will be appreciated.
Cheers.

Here's a script that might be helpful to you. It fills in aggregate values for date and times span when you have existing days with date data type. If you have time periods shorter than a day, you might check out this post.
http://oracleolap.blogspot.com/2010/05/time-dimensions-with-hourly-time.html
CREATE TABLE time_dim
DAY_KEY DATE,
DAY_TIME_SPAN NUMBER,
MONTH_ID VARCHAR2(30),
MONTH_END_DATE DATE,
MONTH_TIME_SPAN NUMBER,
QUARTER_ID VARCHAR2(30),
QUARTER_END_DATE DATE,
QUARTER_TIME_SPAN NUMBER,
CALENDAR_YEAR_ID VARCHAR2(30),
YEAR_END_DATE DATE,
YEAR_TIME_SPAN NUMBER
-- Add rows for days. E.g.,
-- insert into time_dim (select distinct day_key from fact_view);
--UPDATE time_dim
--SET hour_time_span = round(1/24,5);
-- Add month members.
UPDATE time_dim SET month_id = TO_CHAR(day_key 'MON-YYYY');
UPDATE time_dim a
SET month_time_span =
(SELECT ts
FROM
(SELECT DISTINCT month_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY month_id
) b
WHERE a.month_id = b.month_id
UPDATE time_dim a
SET month_end_date =
(SELECT ed
FROM
(SELECT DISTINCT month_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY month_id
) b
WHERE a.month_id = b.month_id
-- Add Quarter members.
UPDATE time_dim SET quarter_id = TO_CHAR(day_key 'Q-YYYY');
UPDATE time_dim a
SET quarter_time_span =
(SELECT ts
FROM
(SELECT DISTINCT quarter_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY quarter_id
) b
WHERE a.quarter_id = b.quarter_id
UPDATE time_dim a
SET quarter_end_date =
(SELECT ed
FROM
(SELECT DISTINCT quarter_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY quarter_id
) b
WHERE a.quarter_id = b.quarter_id
-- Add Year members.
UPDATE time_dim SET month_id = TO_CHAR(day_key 'YYYY');
UPDATE time_dim a
SET year_time_span =
(SELECT ts
FROM
(SELECT DISTINCT year_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY year_id
) b
WHERE a.year_id = b.year_id
UPDATE time_dim a
SET year_end_date =
(SELECT ed
FROM
(SELECT DISTINCT year_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY year_id
) b
WHERE a.year_id = b.year_id
;

Optimizing order by query with multiple time dimensions

Hello all,
I have two time dimensions, one a standard date dimension (Year,Qtr, Month, Week, Day) the other a user defined Time dimension (All, Hour, Minute, Second).
I am joining my cube with my time dimension using only the 'All' level, so that I can get a single record for the Day level in my Date dimension. Under these circumanstances there aren't many records in my sample data. Less than 100 dates, although at the lowest level(seconds) there are approx 2 million records.
In order to get my results back in order I am ordering by the date dimension day_end_date. The query is taking longer than I would expect given that there aren't many records at the Day Level. How can I ensure that my query is ordering based only on the values in the current day_level and not all day_end_dates values in the underlying cube.

Changed order, speed improved significantly.

Problem with time dimension aggregation

I have a time dimension with 2 columns:Year and week
I've created a hierarchy in it to drill down from the year to the week.
when I report the sales in week level I have the right values but when I report the sales value in year level I don't have the right aggregation.Even if the year Level is a grand Total in the hierarchy.
The problem is that for all the years I have the same value but when I add the week level to the report Then I have the right values.
What could be the problem

Hi,
1.Actually the drill down Route path is not properly generated with your given key columns in herarchies.
need to give correct key columns
like year(YYYY)-->Week(wee should be the unique column for each and evry year)
suppose:
2000-sunday
2001-sunday should be different
so mostly the problem at your week column make the unique yearweek column as the key identifier at that level
Every Week is unique cause the logical key is a combination of the year and the weeknumber
2.if not you need to set individual levels for measures in content tab...
you mean by the content tab the level tab when you doubleclick into the measure???
Thanks

Time Dimension Population with ODI 11.1.1.5

Hi All,
I am planning to build a time/Date dimension to use with the HR Fact tables (sourced from Oracle HRMS).
Customer would like to supply start and end dates (01-JAN-05 TO 31-DEC-11) and i should be able to generate and load the time data between these dates.
Down the line, if the customer to append the Time Dimension for future data, he should be able to specify the new start and end dates (01-JAN-12 To 31-DEC-15), i should be able to incrementally load the new time data, instead of truncating and regenerating all the time data.
Any ideas on implementing this requirements using ‘Oracle Data Integrator 11.1.1.5’?
Thanks in advance
Regards,
Venkat

This is what I did recently,
Download the 'SQL_as_source' knowledge module from the Oracle ODI Blog here : http://blogs.oracle.com/warehousebuilder/entry/odi_11g_simple_flexible_powerful
Used a temporary interface with the following simple query :
with row_generator as (
SELECT to_date('01011980','ddmmyyyy') + LEVEL - 1 DT
FROM sys.dual
CONNECT BY LEVEL <=
/* End Date in here -> */ to_number(to_date('31122030','ddmmyyyy') -
/* Start Date in here -> */ to_date('01011980','ddmmyyyy')) +1 )
SELECT DISTINCT
'YEAR' as TIME_LEVEL,
NULL as YEAR_MONTH,
NULL as YEAR_QTR,
to_char(DT,'YYYY') as YEAR
from row_generator
UNION
SELECT DISTINCT
'QUARTER',
NULL,
to_char(DT,'YYYY')||' / '||to_char(DT,'Q'),
to_char(DT,'YYYY') from row_generator
UNION
SELECT DISTINCT
'MONTH',
to_char(DT,'YYYY')||' / '||to_char(DT,'MM'),
to_char(DT,'YYYY')||' / '||to_char(DT,'Q'),
to_char(DT,'YYYY')from row_generator
order by 1,2,3,4
As you can see in the above code, it would be possible to pass in ODI variables as the start and end dates , you could either allow the user to type these in at run time or read them from a control table.
Use the temporary interface as the source data for your Time dimension interface (you might want to add more Time Attributes - Mine was very simple) , then use an IKM Incremental update approach (Im using IKM Oracle Incremental update (Merge)).
Hope this helps
Rgrds
Alastair
p.s - my time dimension is loading multiple levels (Years, Quarters, Months) into the same table - the SQL contains a row for each day though so easily adapted to report days.
Edited by: PeakIndicators_Alastair on Jan 24, 2012 12:05 PM

Additional custom level on Time dimension ?

Hi,
I´m very new to OWB, so I don't know if what I want to do is even possible at all.
I created a time dimension using the "Time Dimension Wizard", selecting all possible levels (year, quarter, month, day), but I also need to have one extra level: semester. You see, we need that level for our reports.
I tried to open the mappings that were generated automatically but Oh, boy! does that look complicated!!! Some operators call time functions but when looking them up, they're in packages that come wrapped, so basically I have no clue as to how the data is being generated by Oracle.
Do you know of any way to accomplish this? Basically have a time dimension with the levels:
Year -> Semester -> Quarter -> Month -> Day
Any help would be very much appreciated.
Rgds,
--Oswaldo Santos
[osantos]

Hi JP,
Thanks for the tip.
I created a new "time" dimension manually. I basically made a copy of the attributes and levels of a normal time dimension, plus the new fields for "semester". I also defined the corresponding fields for "END DATE" and "TIME SPAN".
Now, I can populate this dimension, based on a script that someone else posted in this forum. I'm not sure, though, that Oracle OLAP will recognize this as a "time" dimension, will it? I mean, OWB adds some extra fields for a time dimension created with the wizard (like "level type"). Will this affect the performance or behavior of my cubes? Or, can I say that this is as real a time dimension as one created with the wizard in OWB?
Again, thanks a lot for your support.
Regards,
--osvaldo santos.
[osantos]

DIMENSION WITH ONE LEVEL

When I create a dimension with just one level when I refresh I have this error:
SQL> EXECUTE DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E');
BEGIN DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E'); END;
ERROR en línea 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 1143
ORA-06512: at line 1
can anyone help me?

Hi!thank you for all. I dont know if I understand correctly what you said but
this is the xml template that generates de awm creating a dimension with one level. Can you do something?
<?xml version = '1.0' encoding = 'UTF-8' ?>

<AWXML version = '1.0' timestamp = 'Mon Feb 11 13:29:11 2002' >
<AWXML.content>
<Create Id="Action6">
<ActiveObject >
<AW Name="M62.M62_EN_AW" LongName="M62.M62_EN_AW" ShortName="M62.M62_EN_AW" PluralName="M62.M62_EN_AW" Id="M62.M62_EN_AW.AW" Schema="M62">
<Dimension Name="ENTID" LongName="ENTID" ShortName="ENTID" PluralName="ENTID" Id="ENTID.DIMENSION" Schema="M62" isTime="false" isMeasure="false" UseNativeKey="false">
<Attribute Name="LONG_DESCRIPTION" LongName="DescripciÃ³n Larga" ShortName="DescripciÃ³n Larga" PluralName="Descripciones Largas" Id="ENTID.LONG_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_LONG_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
<Attribute Name="SHORT_DESCRIPTION" LongName="DescripciÃ³n Breve" ShortName="DescripciÃ³n Breve" PluralName="Descripciones Breves" Id="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_SHORT_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
<Hierarchy Name="J_ENT" LongName="J_ENT" ShortName="J_ENT" PluralName="J_ENT" Id="ENTID.J_ENT.HIERARCHY" isDefault="true" Type="LEVEL">
<AttributeProjection Name="OBJ1780952198" LongName="" ShortName="OBJ1780952198" PluralName="OBJ1780952198" Id="ENTID.J_ENT.OBJ1780952198.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952199" LongName="" ShortName="OBJ1780952199" PluralName="OBJ1780952199" Id="ENTID.J_ENT.OBJ1780952199.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<HierarchyLevelAssociation Name="NIV1" LongName="HLA1" ShortName="HLA1" PluralName="HLA1" Id="ENTID.J_ENT.NIV1.HIERARCHYLEVELASSOCIATION">
<AttributeProjection Name="OBJ1780952201" LongName="" ShortName="OBJ1780952201" PluralName="OBJ1780952201" Id="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952202" LongName="" ShortName="OBJ1780952202" PluralName="OBJ1780952202" Id="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<SourceMappingGroup >
<DimensionMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.DIMENSIONMAPGROUP" Type="HIERARCHYLEVEL">
<DimensionKeySourceExpression Name="KeyMap" LongName="KeyMap" ShortName="KeyMap" PluralName="KeyMap" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.DIMENSIONKEYSOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952205" LongName="" ShortName="OBJ1780952205" PluralName="OBJ1780952205" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.OBJ1780952205.SOURCECOLUMN" Column="M62.ENTIDADES.ID_ENTIDAD"/>
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</DimensionKeySourceExpression>
<AttributeSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.ATTRIBUTESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952207" LongName="" ShortName="OBJ1780952207" PluralName="OBJ1780952207" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.OBJ1780952207.SOURCECOLUMN" Column="M62.ENTIDADES.DES_ENTIDAD_CAS"/>
<TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<BaseAttribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
</AttributeSourceExpression>
<AttributeSourceExpression Name="AttrMap2" LongName="AttrMap2" ShortName="AttrMap2" PluralName="AttrMap2" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.ATTRIBUTESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952209" LongName="" ShortName="OBJ1780952209" PluralName="OBJ1780952209" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.OBJ1780952209.SOURCECOLUMN" Column="M62.ENTIDADES.DEC_ENTIDAD_CAS"/>
<TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<BaseAttribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
</AttributeSourceExpression>
</DimensionMapGroup>
</SourceMappingGroup>
<level XMLIDref="ENTID.NIV1.LEVEL" />
</HierarchyLevelAssociation>
</Hierarchy>
<MemberSelection >
<Level Name="NIV1" LongName="NIV1" ShortName="NIV1" PluralName="NIV1" Id="ENTID.NIV1.LEVEL" isDimensioned="false">
<AttributeProjection Name="OBJ1780952195" LongName="" ShortName="OBJ1780952195" PluralName="OBJ1780952195" Id="ENTID.NIV1.OBJ1780952195.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952196" LongName="" ShortName="OBJ1780952196" PluralName="OBJ1780952196" Id="ENTID.NIV1.OBJ1780952196.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</AttributeProjection>
</Level>
</MemberSelection>
</Dimension>
<Cube Name="CUBO_ENT" LongName="CUBO_ENT" ShortName="CUBO_ENT" PluralName="CUBO_ENT" Id="CUBO_ENT.CUBE" Schema="M62" UseGlobalIndex="false" SparseType="STANDARD" DefaultDataType="DECIMAL" AutoSolve="YES">
<SourceMappingGroup >
<CubeMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="CUBO_ENT.MAPGROUP1.CUBEMAPGROUP">
<CubeDimensionSourceExpression Name="KeyMap1" LongName="KeyMap1" ShortName="KeyMap1" PluralName="KeyMap1" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.CUBEDIMENSIONSOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952236" LongName="" ShortName="OBJ1780952236" PluralName="OBJ1780952236" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.OBJ1780952236.SOURCECOLUMN" Column="M62.EMAITZA_E.ID_ENTIDAD"/>
<TargetObject XMLIDref="ENTID.DIMENSION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</CubeDimensionSourceExpression>
<MeasureSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.MEASURESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952238" LongName="" ShortName="OBJ1780952238" PluralName="OBJ1780952238" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.OBJ1780952238.SOURCECOLUMN" Column="M62.EMAITZA_E.CANTIDAD"/>
<TargetObject XMLIDref="CUBO_ENT.MED1.MEASURE" />
</MeasureSourceExpression>
</CubeMapGroup>
</SourceMappingGroup>
<SolveDefinition >
<AggregationDefinition Name="OBJ1780952211" LongName="" ShortName="OBJ1780952211" PluralName="OBJ1780952211" Id="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" Schema="AW$DEFAULT" AggIndex="NA" CacheStore="SESSION" CacheNa="NA">
<CalculationSpecification >
<AggregationHierarchySpecification Name="Relation1" LongName="Relation1" ShortName="Relation1" PluralName="Relation1" Id="CUBO_ENT.OBJ1780952211.RELATION1.AGGREGATIONHIERARCHYSPECIFICATION" CalculationOrder="1">
<AggregationOperator >
<BaseOperator Name="Base Operator" LongName="Base Operator" ShortName="Base Operator" PluralName="Base Operator" Id="CUBO_ENT.OBJ1780952211.RELATION1.BASE OPERATOR.BASEOPERATOR" opcode="SUM"/>
</AggregationOperator>
<Dimension XMLIDref="ENTID.DIMENSION" />
<PreComputeClause Name="OBJ1780952231" LongName="" ShortName="OBJ1780952231" PluralName="OBJ1780952231" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.PRECOMPUTECLAUSE">
<DimensionMemberExpression Name="OBJ1780952232" LongName="" ShortName="OBJ1780952232" PluralName="OBJ1780952232" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.OBJ1780952232.DIMENSIONMEMBEREXPRESSION" ExpressionType="EXCLUDE" Expression="ALL"/>
</PreComputeClause>
</AggregationHierarchySpecification>
</CalculationSpecification>
<SolveDefDimRef Name="OBJ1780952226" LongName="" ShortName="OBJ1780952226" PluralName="OBJ1780952226" Id="CUBO_ENT.OBJ1780952211.OBJ1780952226.SOLVEDEFDIMREF" CalcMemberSolveOrder="0">
<Dimension XMLIDref="ENTID.DIMENSION" />
<SolveDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
</SolveDefDimRef>
</AggregationDefinition>
</SolveDefinition>
<DefaultAggregationDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
<CubeDimRef Name="OBJ1780952225" LongName="" ShortName="OBJ1780952225" PluralName="OBJ1780952225" Id="CUBO_ENT.OBJ1780952225.CUBEDIMREF" Sparse="true">
<Dimension XMLIDref="ENTID.DIMENSION" />
</CubeDimRef>
<Measure Name="MED1" LongName="MED1" ShortName="MED1" PluralName="MED1" Id="CUBO_ENT.MED1.MEASURE" DataType="DECIMAL" isInternal="false" UseGlobalIndex="false" ForceCalc="false" ForceOrder="false" SparseType="STANDARD" AutoSolve="AUTO_SOLVE"/>
<PartitionHierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<PartitionLevel XMLIDref="ENTID.NIV1.LEVEL" />
</Cube>
<ExtendedProperty Name="OBJ1780952192" LongName="" ShortName="OBJ1780952192" PluralName="OBJ1780952192" Id="OBJ1780952192.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.LONG_DESCRIPTION.ATTRIBUTE"/>
<ExtendedProperty Name="OBJ1780952193" LongName="" ShortName="OBJ1780952193" PluralName="OBJ1780952193" Id="OBJ1780952193.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.SHORT_DESCRIPTION.ATTRIBUTE"/>
</AW>
</ActiveObject>
</Create>
</AWXML.content>
</AWXML>

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!

[38073] dimension has multiple leaf levels which are not identical

Hi,
I am trying to implement a time dimension with 2 source tables.
The time dimension is from minute to year where logical table includes 2 source tables :
Source table#1 : Year,month,week,day
Source table#2: hour,minute (minute is a leaf level and chronological key)
When i try to check-in i got the following error: [38073] dimension has multiple leaf levels with are not identical.
Thank you.
Michael

Hi RM
i am able to create multiple hirerachy in time dimension and assigned time_id as chronological key which is at the dimension detail level and acting as shared child level for both of them......
I have created AGO function for calendar year as
AGO(Test."Fact".amount_sold, Test."Time Dim"."Calendar Year", 1)
but when i have used AGO column in answers i am getting below mentioned error:-
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22046] To use AGO function, the query level ('Calendar Year, Fiscal Year') must be a static level. (HY000)
any suggestion would be appreciated to solve this.
thanks & regards

Time Dimension with Hourly base level

Similar Messages

Maybe you are looking for