Setup time dimension in some different fiscal calendars

I have the different fiscal calendars.
Then, I wanna compare the current month fiscal amount and the previous month fiscal amount with AGO function.
The calendars are like below.
Calendar A : fiscal month start April
Calendar B : fiscal month start January
In this case, how should I define the chronological key in the time dimension?
For example, I try the below setup in the calendar period hierarchy.
Year 2008
Half 1H 2H
Quarter 1Q 2Q 3Q 4Q
Month 1Q = {Apr-08 in CAL_A, May-08 in CAL_A, Jul-08 in CAL_A, Jan-08 in CAL_B, Feb-08 in CAL_B, Mar-08 in CAL_B}
and some.
In this examle, the number of MONTH level members are 24.
Then I make a column for sort.
The sort number is below.
For CAL_A
Month SortNo.
Apr-08 1
May-08 2
Jun-08 3
Jul-08 4
Aug-08 5
Sep-08 6
Oct-08 7
Nor-08 8
Dec-08 9
Jan-09 10
Feb-09 11
Mar-09 12
For CAL_B
Month SortNo.
Jan-09 13
Feb-09 14
Mar-09 15
Apr-08 16
May-08 17
Jun-08 18
Jul-08 19
Aug-08 20
Sep-08 21
Oct-08 22
Nor-08 23
Dec-08 24
In this case, if I try to get the previous month of Jan-09 in CAL_B with AGO function, the system get Mar-09 for CAL_A. Because the record of Mar-09 for CAL_A is 12 in SortNo. column.
As far as possible, I wanna use AGO function.
Does anyone have good ider for this problem?
Edited by: user3532462 on 2008/08/28 2:57

Hi,
I guess it's easier to setup two different time dimensions; one for calendar A and one for calendar B. Use aliases in the Physical Layer.
Good Luck,
Daan Bakboord

Similar Messages

  • 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

  • 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

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

  • PeriodsToDate and single Time dimension Attributes

    Hi folks,
    I just want to kindly confirm with you, if the PeriodsToDate function works only with user hierarchy?
    That is because I am building some YTD calculation and I have two user hierarchies in the Time dimension, let´s say Markenting Calendar and Fiscal Calendar, but also I have single attributes that do not belong to any of these hierarchies like RetailDay.
    Could I build a PeriodsToDate for these attributes?
    I think the answer is no, because if a year is not related through the user hierarchy, how could the siblings be found.
    Any comment will be appreciated.

    Hello,
    Basicly,PeriodsToDate function expects level expression for the first argument,i think it should be hierarcy level,since it should be hierarchy level,second argument should be hierarchy member as well,otherwise it throws an error.This is what i know.Hope
    this helps.
    Thanks,

  • 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

  • Multiple Fiscal Calendar in a single context

    Hi,
    I know that for each context we can only have one PAS database, as a result, only a single Fiscal Calendar definition for a each context.
    My question is: there is any way of creating a workaround for this? I need to have in a single context KPI's that use different fiscal calendar's
    Thanks in advance for the tips
    Regards
    Pedro

    Hi Bob,
    so, if I understand correctly there is only two options:
    1 - Have a single PAS database with a single fiscal calendar and use that in a single Context. The user's will have the option to then create specific reports for the metrics that should be displayed using a different Fiscal (using for that the different options in time that already exist in the reports component).
    2 - Create an individual PAS database for each Fiscal and have a different context for each of those databases.
    Is like this?
    If you think strategically, that shouldn't change the usefullness of Strategy Management, since the status of objectives and KPIs will still be driven off your current numbers, whatever the fiscal calendar.
    Yes, but for instance if we have KPI's that use Fiscal form Jan to Dec and other from Jul to Jun, when we select yearly data for 2009 for example, the information displayed for both is not the "same". For KPI1 is from Jul 2009 to Jun 2010 when it should be Jan 2009 to Dec 2009 (this for a database with Fiscal Calendar starting at "Jul"). Is not like this?
    PS: It's strange than no one have this problem in the past. Is not normal to have a customer that want to see in the same Scorecard/Context, KPI's that use different Fiscal calendar?
    Thanks in advance
    Pedro
    Edited by: Pedro S. Costa on Sep 23, 2009 5:11 PM

  • Multiple time dimension hierarchies ?

    Hi, is it possible to easily define multiple hierarchies in a time based dimension ?
    I know the time dimension wizard allows the definition of only 1 hierarchy but I need to have a time dimension that has both a calendar based and a fiscal calendar hierarchy.
    It is possible to modify the dimension definition after using the wizard but I don't think the original mapping automatically generated by the wizard is updated.
    Anyone done this ?
    Thanks
    Paul

    Hi,
    Did any of you manage to create the extra hierarchy in the time dimension?
    I also created the standard time dimension with only one fiscal hierarchy first, but later found the need to add another fiscal hierarchy that has month as the leaf level (does not include day level). However, when deploying, I get the message "ORA-00957: duplicate column name"...
    (Reason for defining other hierarchy without the day level is that it seems that when using auto-solve on a compressed cube, it tries to solve from all leaf levels upward, but one cube I have is loaded at the month level of the time dimension... day level is not applicable in this specific cube. Using the standard fiscal hierarchy in this case does not work on that cube.)
    Thanks,
    Ed
    PS Looking at the ddl script from the Job Details window, the duplicate columns are in the auto generated stage tables/views (for month and quarter level; not for year level(?)). How can we influence OWB to generate the correct things???
    Create table "OWB$STGTBL_D_DI_FISCAL__2B6926" (
    FISCAL_QUARTER_F_2B69262B6934 number,
    FISCAL_QUARTER_F_2B69262B6934 number);
    Create table "OWB$STGTBL_D_DI_FISCAL__2B6915" (
    FISCAL_MONTH_FI_2B69152B6926 number,
    FISCAL_MONTH_FI_2B69152B6926 number);
    Message was edited by:
    EdSp

  • Loading of time dimension

    Hi,
    I started thinking about what the best way to load the time dimension is. Until now I have loaded data for 10-15 years in advance into the dimension to be done with it. One down side to this is that when you create or view reports, you might see the year 2015 but for obvious reasons there won't be any data loaded for this year. Another thing I started thinking of the other day is how this may affect the performance and the loadtime of the cube.
    If all dimensions is set to not be sparse and you have loaded 10 years that's not yet in use, the size of the cube, from what I understand, will be unnecessarily large. This will probably also have an affect on the loadtime.
    If you set all the dimensions except for the time dimension as sparse, as AWM sets it as default, how will this affect the size of the cube?
    Anyone have any thoughts around this?
    Regards Ragnar

    Hi,
    I need to load time dimensions to have data till 2015. Moreover we have just regular time dimensions tables and no fiscal tables.
    We have updated the fiscal data file to include data till 2015 and update DAc parameter Analysis end date to 31/12/2015. Data is loaded in these tables till 2015 but the ETL is failing for analyze W_ETL_RUN_S task.(param-g table contans 256 rows inspite of just 1 record)
    I checked the OBI guide and found that parameters $$Start_date and $$End_Date needs to be set.
    I am not sure if Analysis end date in DAC-> ETL prefernces is same as $$End_Date . Also, I could not see any start date parameter. I have checked mapping parameter as well.
    It would be really great if you could tell the exact steps followed to extend the datawarehouse.

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

  • 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

  • SSRS Expression Current month in a Fiscal calendar dimension from a SSAS cube

    How to create an expression for a default SSRS parameter to a SSAS cube when using i Fiscal Year calendar - and where I want to show current Calendar month and year (for example February 2014) 
    This is an example of my Time dimension for February 2014:
    [Time].[FiscalYMD].[Fiscal_Year].&[2013].&[10]
    The fiscal calendar goes from May - May - which means that April 2014
    would look like this:
    [Time].[FiscalYMD].[Fiscal_Year].&[2013].&[12]
    and May 2014 would look like this:
    [Time].[FiscalYMD].[Fiscal_Year].&[2014].&[01]
    Please advise

    Hi HCMJ,
    To represent the fiscal calendar, you shift the current date by 4 months back. Then you can do:
    ="[Time].[FiscalYMD].[Fiscal_Year].&[" & Year( DateAdd( "m", -4, Today() ) ) & "].&[" & Month( DateAdd( "m", -4, Today() ) ) & "]"
    It just gets the year and month of '4 months ago'. I have not tested it, but I guess it should work.
    Regards
    Andrew Borg Cardona

  • Why are some of my calendar appointments synching, some synch multiple times and others not at all?

    why are some of my calendar appointments synching, some synch multiple times and others not at all?

    iTunes: May be unable to transfer videos to iPhone, iPad, or iPod - http://support.apple.com/kb/TS1497

  • 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

  • HT4576 What is the easiest way to enter a calendar event on an iPhone in a time zone which is different to one in which one is at present?

    What is the easiest way to enter a calendar event on an iPhone in a time zone which is different to one in which one is at present?  Can this synchronise with Outlook, which allows for time zones to be set manually for each event?
    This was easy on my old iPhone 4S, on which (exactly as in outlook) you manually defined a time zone for each event - but this function no longer seems to work on my new iPhone 5S.

    What is the easiest way to enter a calendar event on an iPhone in a time zone which is different to one in which one is at present?  Can this synchronise with Outlook, which allows for time zones to be set manually for each event?
    This was easy on my old iPhone 4S, on which (exactly as in outlook) you manually defined a time zone for each event - but this function no longer seems to work on my new iPhone 5S.

Maybe you are looking for