Time dimension population

Hi
I am taking "clndr" as source and populate time dimension table.Time dimension table ( granularity is an hourly basis) will be populated with date with 24 intervals and based on the cln_dt whether it falls in weekened or holiday ,If falls in weekened or holiday , populate 'Y' Else 'N' .Please see the below example
clndr(source table)
cln_dt cldr_day busday cldr_yr
1/05/2006 monday y 2005
2/5/2006 Tuesday y 2005
Expected data
==========
Time_dim(Target table)
Time_dt interval holidy ind
1/05/2006 0 N
1/05/2006 1 N
1/05/2006 2 N
1/05/2006 3 N
1/05/2006 23 N
2/5/2006 0 N
2/5/2006 1 N
2/5/2006 23 N
Thanksinadvance
MR

Try this, Modified Dnikiforov's solution:
SQL> ed
Wrote file afiedt.buf
1 select date#, hour, decode(busday,'Fri','Y','Sat','Y','Sun','Y','N') flag
2 from ( select to_date('06-MAY-06') date#, to_char(to_date(
3 '06-MAY-06'),'Dy') busday from dual
4 union all
5 select to_date('07-MAY-06') date#, to_char(to_date(
6 '07-MAY-06'),'Dy') from dual
7 union all
8 select to_date('08-MAY-06') date#, to_char(to_date(
9 '08-MAY-06'),'Dy') from dual ) calendar,
10 (select rownum-1 hour from dict where rownum <=24) hours
11* order by 1,2
SQL> /
DATE#        HOUR F
06-MAY-06       0 Y
06-MAY-06       1 Y
06-MAY-06       2 Y
06-MAY-06       3 Y
06-MAY-06       4 Y
06-MAY-06       5 Y
06-MAY-06       6 Y
06-MAY-06       7 Y
06-MAY-06       8 Y
06-MAY-06       9 Y
06-MAY-06      10 Y
06-MAY-06      11 Y
06-MAY-06      12 Y
06-MAY-06      13 Y
06-MAY-06      14 Y
06-MAY-06      15 Y
06-MAY-06      16 Y
06-MAY-06      17 Y
06-MAY-06      18 Y
06-MAY-06      19 Y
06-MAY-06      20 Y
06-MAY-06      21 Y
06-MAY-06      22 Y
06-MAY-06      23 Y
07-MAY-06       0 Y
07-MAY-06       1 Y
07-MAY-06       2 Y
07-MAY-06       3 Y
07-MAY-06       4 Y
07-MAY-06       5 Y
07-MAY-06       6 Y
07-MAY-06       7 Y
07-MAY-06       8 Y
07-MAY-06       9 Y
07-MAY-06      10 Y
07-MAY-06      11 Y
07-MAY-06      12 Y
07-MAY-06      13 Y
07-MAY-06      14 Y
07-MAY-06      15 Y
07-MAY-06      16 Y
07-MAY-06      17 Y
07-MAY-06      18 Y
07-MAY-06      19 Y
07-MAY-06      20 Y
07-MAY-06      21 Y
07-MAY-06      22 Y
07-MAY-06      23 Y
08-MAY-06       0 N
08-MAY-06       1 N
08-MAY-06       2 N
08-MAY-06       3 N
08-MAY-06       4 N
08-MAY-06       5 N
08-MAY-06       6 N
08-MAY-06       7 N
08-MAY-06       8 N
08-MAY-06       9 N
08-MAY-06      10 N
08-MAY-06      11 N
08-MAY-06      12 N
08-MAY-06      13 N
08-MAY-06      14 N
08-MAY-06      15 N
08-MAY-06      16 N
08-MAY-06      17 N
08-MAY-06      18 N
08-MAY-06      19 N
08-MAY-06      20 N
08-MAY-06      21 N
08-MAY-06      22 N
08-MAY-06      23 N
72 rows selected.

Similar Messages

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

Populating the time dimension in ODI

I need to populate my time dimension in ODI> I read a solution in this forum suggesting to create a time table/view in the source schema, reverse it in ODI and then use it as source to populate the time dimension. Is there another way to do this? One way I thought of was to use the ORDERDATE field in my ORDER table (my source table in Oracle) and map it to my time dimension in SQL Server via an interface. But I also have DUEDATE, SHIPDATE and PAYDATE fields in my ORDERS table and this approach would mean that I have to map them through separate interfaces to the time dimension as well. I have created a procedure in the source schema(Oracle) and want to use it in ODI to populate the time dimension. But I amnt sure if that is possible in ODI. Could anyone help me with this please?
Regards,
Neel

Hi Neelab,
Sorry for my delay to reply you, I had no time the lasts days...
To get the four distinct key from your time dimension, just add four instance of dimension table at interface each one joined with one of the columns.
I believe that you load your time dimension from some other table than PRJ_TBL_TRANSACTION because you have the HolidayType column in your time dimension...
A view is one possible solution to load the time table but depends how the performance of the query is.
A way to do it at ODI is:
- Create 4 interfaces, one for each column, to load 1 singe table with 1 single date column, don't worry about duplicated value at this time, than you can just use the "IKM Control Append" that has more performance but check the "Distinct" box (flow tab) at each interface
- Create a last interface from this temp table as source, to the time dimension target table. Now you will use the "IKM Incremental Update" and do choose the "Update" option to "NO". Check the "Distinct" box.
As this table will have no more than 6.200 records from the last 20 years it will be a small table where you shouldn't have performance problems.
These are some of possible solutions but I would like to add other "way to think".
By the table that you show here you have a simple time table with no special feature, for that, let me suggest you other way.
- in the current way you will join but didn't get the record that "fail" from the join once they will be exclude if a date do not exist at time dimension
My suggestion:
- Load the dimension time table from your source table
- as PK in time dimension table, use the ''Julian Day"
- At ODI target fact table (datastore), create a 4 reference constraints (one by column) to the time dimension
- at interface do not use the dimension as source and transform the 4 date to Julian and let the 4 constraints take care if they exists or not at dimension table.
OR
- Look for the minimum "possible" date at your company
- populate your time dimension with every each day since then until a future date (Dec 31, for instance)
- create a process to populate the future date that will be execute in a interval that you decide (once a year, once a month, as you wish) dependent on how further the date is populated
- use the "Julian date" as PK
- At interface just transform any date to "Julian Date" it will be at dimension time once it is naturally unique
You could substitute the Julian date for "YYYYMMDD" that is a unique value too.
I presented you 2 way to consider be considered, each one could be used based on how important is for the business know if a date was loaded or not.
Someone can question that has the dates loaded from source against has all dates previous loaded could help to find errors from days that wasn’t loaded but it has a failure. As there are 4 dates source columns (and we are talking just about one source table until now) if a date loaded math a date when the load failure there is no value in use the time dimension date to analyze this possibility.
I defend the full time dimension load.
Make sense and/or help you??

Populating the Time Dimension

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

Reposted.

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

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

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.

Composite key in Time dimension

Hi All,
I would like to know Time dimension with Composite key. I have a requirement where I want to store 2 Calendars in Time dimension table. for e.g :
for one calendar Weekstarts from SUN-SAT and for another it is from MON-TUE
DateKey Type WeekStart WeekEnd
20140101 1 Sun Sat
20140101 2 Mon Tue
..................etc
I have a measure group which is related to Time dimension (DateKey and Type used a Composite key). This implementation has no issues for additive measures but there are few issues with semi-additive measures (last non-empty,...).
Will composite Key have any effect on semi-additive measures ?
what if i use surrogate key instead of composite key.
Please suggest if the approach has any issue with Time intelligence. Advise if there is any better approach for the same.
Ram MSBI Developer

Hey.. Thanks!
I am clear about the concept about defining annotation based composite key. Also, I read in the documentation that I'll be needing to define as direct, aggregate or one-to-one. But, I am not able to define and run the same in the project mapping xml of toplink.
It would be great if you can share some sample code for defining the same. For e.g. in my mentioned example, there is TestEntity POJO having 'id' as the attribute which gets populated with the testEntityCode of the TestEntityKey POJO. Please suggest the same for the same:
<opm:primary-key>
<opm:attribute-name>id</opm:attribute-name>
<opm:field table="TEST_ENTITY_B" name="TEST_ENT_CODE" xsi:type="opm:column"/>
</opm:primary-key>
Thanks!

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

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

Time dimension question

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

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

How to build the time dimension in Essbase with Fiscal Year (July thru Jun)

Hi,
In a recent project i have a situation where i need the time dimension to have some thing like this Fiscal Year (July - June) using BSO need to achieve DTS (YTD and QTD) functionality also.
And also my reports should also be able to drill through and needs comparison years(Prev Year Vs Current Year), months(Prev Year Vs Current Year) and Qtrs(Prev Year Vs Current Year).
How can i achieve this using BSO?.

Hi there,
This forum is for Oracle OLAP. The Essbase forum can be found here:- Essbase
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

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?

Slicer Time Dimension Issue with Cube Functions

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

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

Fiscal Year Time Dimension - Month Time Span

I have a need to create a fiscal year time dimension and I created using Time Wizard in OWB. When I was developing BI Reports, I found some inconsistencies in Time dimension as it was showing figures in all the months of my first quarter of new financial year that Apr 2009 – Mar 2010. On close inspection of Time Dimension table I found that fiscal_month_time_span value varies from 35 to 28 to 29 for different months. i.e. it’s not matching with corresponding Calendar month. This means I am unable to plot data correctly using fiscal year dimension.
Maybe this is how it works in Oracle, but this does not solve my problem. Could anyone give me some solution for this ? My Fiscal year is from ‘1- Apr – 09’ to ’31-Mar-10’. In my reports I would like to see transactions for April month when I use month attribute of time dimension like it happens in Calendar time dimension.

May be someone from
Forum: Business Intelligence Suite Enterprise Edition can answer this .
Please post it there.

Time dimension population

Similar Messages

Maybe you are looking for