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

Similar Messages

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

  • Time utility shell dimension across multiple date dimensions

    Hello,
    I have built a time utility shell dimension based on a solution from Tomislav Piasevoli (book: MDX with SSAS 2012 cookbook) however I have modified it slightly
    In his example he uses two hierarchies from the same dimension. However I have modified it to use two different date dimensions, 1 hierarchy from each of the dimensions. The hierarchies must be able to be filtered by one another or combined
    in the same query. The problem I’m having is my solution does not work for
    distinct count measures. It works for every other type of measure…sum, count of rows etc etc. The filtering works perfectly when one hierarchy is filtered by the other, it’s just the distinct count that won’t show the parallel period.
    I have created the shell dimension the typical way. Creating a named query like below. Creating the dimension with the default value etc etc
    SELECT       
    0 AS ID, 'As is' AS Name
    UNION ALL
    SELECT       
    1 AS ID, 'Year ago' AS Name
    Below is the original MDX and my modified MDX. If anyone can help that would be great!
    --original mdx for one date dimensions.. the below works perfectly for all measures including distinct counts
    SCOPE( [Time Calcs].[Calc].[Year ago]);
    SCOPE([Date].[Date].MEMBERS,
    [Date].[Calendar Year].[Calendar Year].MEMBERS
    This = (ParallelPeriod([Date].[Calendar].[Calendar Year],1,[Date].[Calendar].CurrentMember),
    ParallelPeriod([Date].[Calendar Weeks].[Calendar Year],1,[Date].[Calendar Weeks].CurrentMember),
    [Time Calcs].[Calc].&[0]
    End
    Scope;
    End
    Scope;
    --my modifed mdx for multiple date dimensions.. the below works perfectly for all measures
    except distinct counts
    SCOPE( [Time Calcs].[Calc].[Year ago]);
    SCOPE([Date].[Date].MEMBERS,
    [Date].[Calendar Year].[Calendar Year].MEMBERS
    [Delivery Date].[Date].MEMBERS,
    [Delivery Date].[Calendar Year].[Calendar Year].MEMBERS
    This = (ParallelPeriod([Date].[Calendar].[Calendar Year],1,[Date].[Calendar].CurrentMember),
    ParallelPeriod([Delivery Date].[Calendar Weeks].[Calendar Year],1,[Delivery Date].[Calendar Weeks].CurrentMember),
    [Time Calcs].[Calc].&[0]
    End
    Scope;
    End
    Scope;

    Hi Toro07,
    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Multiple time hierarchies in OWB

    Hello,
    Have anyone tried creating multiple time hierarchies in the same MOLAP time dimension in OWB?
    I tried creating calendar hierarchy first by the time wizard and fiscal hierarchy later by the editor in the same dimension. Deployment was OK and calendar hierarchy worked fine but fiscal hierarchy only showed all the days in the dimension, without indicating any other levels (fiscal week, month, year).
    After close inspection i found out that OWB only creates either DAY_OF_CAL_YEAR or DAY_OF_FIS_YEAR (of course, DAY_OF_CAL_MONTH or DAY_OF_FIS_MONTH as well) according to whichever hierarchy was created initially by the wizard. People have suggested using the create map button in the levels tab but the program has instead asked me for sequences. What sequence should I enter? Was the method flawed? or There are other ways to work around this problem?
    Personally I don't really think having two separate dimensions is a good idea since by joining these two dimensions to the same measure, what happens if I drill down fiscal dimension but leave calendar dimension in the year level, would it mean that I am going to fiscal quarter by calendar year? doesn't really make sense.
    As always, I'm wide open to any suggestion/criticism to the problem/approach i have right now.
    Thank you!

    Hi Ram,
    I don't think you need to have 2 seperate hierarchies for that. Once you build the data model based on 'Day' bucket, you can agreegate the data to see/use it at any time level. The available time levels for a data model built on 'Day' time bucket are,
    - Day
    - Week
    - Month
    - 4-4-5
    - Quarter
    - Half Year
    - Year
    Only you need to configure your worksheets and interfaces choosing one of these time level based on the purpose i.e. DM or SOP.
    Hope this solves your issue.
    Regards,
    Milind..
    Edited by: Milind_K on Jun 11, 2010 3:55 PM

  • 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

  • Unable to filter the data for multiple time selections by dimensions

    Hi to all,
    I am new in MDX, i have a problem with my MDX query.
    Calculated Member Logic:
    SUM((OPENINGPERIOD([Date].[YQMD].[Year],[Date].[YQMD].[Month].&[2010-12-01T00:00:00]):[Date].[YQMD].Currentmember),[Measures].[Paid Amt])
    Mdx Logic EX:
    With Member [MEASURES].[Received_Amount]
    AS
    SUM((OPENINGPERIOD([Date].[YQMD].[Year],[Date].[YQMD].[Month].&[2010-12-01T00:00:00]):[Date].[YQMD].Currentmember)
    ,[Measures].[Paid Amt])
    SELECT {[MEASURES].[Received_Amount]} On Columns
    ,[Date].[YQMD].[Year].members On Rows
    From [Financial]
    If i select multiple time periods in Rows, the query working fine.
    but if select multiple periods in where clause it is not responding.
    With Member [MEASURES].[Received_Amount]
    AS
    SUM((OPENINGPERIOD([Date].[YQMD].[Year],[Date].[YQMD].[Month].&[2010-12-01T00:00:00]):[Date].[YQMD].Currentmember)
    ,[Measures].[Paid Amt])
    SELECT {[MEASURES].[Received_Amount]} On Columns
    ,[Speciality].[Specialty Name].[Specialty Name].members On Rows
    From [Financial]
    Where {[Date].[YQMD].[Year].&[2012-01-01T00:00:00],[Date].[YQMD].[Year].&[2013-01-01T00:00:00]}
    Note:
    Each of them is considered from the minimum date in the database to the selected time.
    And also the data has to be filtered with respect to each drill down dimension.
    If select multiple time periods the same formula has to be applied with respect to the dimensions.
    Kindly help me to get out of this problem
    Best Regards,
    Nagendra

    Hi David,
    Thanks for your response.
    I have a measure, i have to get received_amount in the database from the database starting period to my selection period. Later i have to check by dimensions using same measure. if i select any one period by dimension it's coming, but if i select multiple
    periods in filter level by dimensions it's showing no records.
    For Ex: 
    I have four years data in my database (2010-2013).
    In 2010
    Bill_Amt
    Bill_Date  
    Specialty received_amount
    1000
    10/01/2010 4
    600
    2000
    04/08/2010 2
    1000
    In 2013
    Bill_Amt
    Bill_Date Specialty
    received_amount
    1500
    22/02/2013 2
    1200
    2000
    14/03/2013 1
    800
    In the above scenario,
    By Period:
    if i go by period i should get,  
    Jan'13  ---> 1600
    Feb'13  ---> 2800
    Mar'13  ---> 3600
    Specialty By Single Period:
    If i select Jan'13 by specialty
    Specialty
     received_amount
    2 1000
    4 600
    If i select Feb'13 by specialty
    Specialty
     received_amount
    2 2200
    4 600
    If i select Mar'13 by specialty
    Specialty
     received_amount
    1 800
    2 2200
    4 600
    Specialty By Multiple selection Periods:
    The result should be sum of the individual selection periods by specialty as follows,
    If i select Jan'13 & Feb'13 by specialty
    Specialty
     received_amount
    2 3200
    4 1200
    If i select Jan'13 , Feb'13 & Mar'13 by specialty
    Specialty
     received_amount
    1 800
    2 5400
    4 1800
    Regards,
    Nagendra

  • How to build 2 hierarchies in time dimension

    Hi All
    I want to know how to build 2 hierarchies in time dimension in SAPBPC 7.5 NW.
    thanks

    Hi nilanjan chatterjee
    thanks for your feedback. please check my time dim below.
    we got two financial years.
    1. jan to dec ( thats my parenth1)
    2. apr to mar ( thats my parenth2)
    In usertime id i copied 2008 time ids for fy2009 jan sep and from oct to dec copied 2009 jan to mar time ids.
    ID                         Desc            parenth1        parenth2                               Timeid         usertimeid
    2009.Q1          2009.Q1          2009.TOTAL                                   20090001     
    2009.Q2          2009.Q2          2009.TOTAL                                   20090002     
    2009.Q3          2009.Q3          2009.TOTAL                                   20090003     
    2009.Q4          2009.Q4          2009.TOTAL                                   20090004     
    FY2009.Q1     FY2009.Q1                           FY2009.TOTAL                 20090001     
    FY2009.Q2     FY2009.Q2                            FY2009.TOTAL          20090002     
    FY2009.Q3     FY2009.Q3                          FY2009.TOTAL               20090003     
    FY2009.Q4     FY2009.Q4                           FY2009.TOTAL               20090004     
    2009.TOTAL     2009.TOTAL                                                      20090005     
    FY2009.TOTAL     FY2009.TOTAL                                        20090005     
    2009.JAN     2009.JAN     2009.Q1                                        20090100     20090100
    2009.FEB     2009.FEB     2009.Q1                                        20090200     20090200
    2009.MAR     2009.MAR     2009.Q1                                        20090300     20090300
    2009.APR     2009.APR     2009.Q2                                        20090400     20090400
    2009.MAY     2009.MAY     2009.Q2                                        20090500     20090500
    2009.JUN     2009.JUN     2009.Q2                                        20090600     20090600
    2009.JUL     2009.JUL     2009.Q3                                        20090700     20090700
    2009.AUG     2009.AUG     2009.Q3                                        20090800     20090800
    2009.SEP     2009.SEP     2009.Q3                                        20090900     20090900
    2009.OCT     2009.OCT     2009.Q4                                        20091000     20091000
    2009.NOV     2009.NOV     2009.Q4                                        20091100     20091100
    2009.DEC     2009.DEC     2009.Q4                                        20091200     20091200
    FY2009.JAN     FY2009.JAN                    FY2009.Q1                    20090100     20080400
    FY2009.FEB     FY2009.FEB                    FY2009.Q1                    20090200     20080500
    FY2009.MAR     FY2009.MAR                     FY2009.Q1                    20090300     20080600
    FY2009.APR     FY2009.APR                     FY2009.Q2                    20090400     20080700
    FY2009.MAY     FY2009.MAY                     FY2009.Q2                    20090500     20080800
    FY2009.JUN     FY2009.JUN                      FY2009.Q2                    20090600     20080900
    FY2009.JUL     FY2009.JUL                     FY2009.Q3                    20090700     20081000
    FY2009.AUG     FY2009.AUG                     FY2009.Q3                    20090800     20081100
    FY2009.SEP     FY2009.SEP                     FY2009.Q3                    20090900     20081200
    FY2009.OCT     FY2009.OCT                      FY2009.Q4                    20091000     20090100
    FY2009.NOV     FY2009.NOV                      FY2009.Q4                    20091100     20090200
    FY2009.DEC     FY2009.DEC                        FY2009.Q4                    20091200     20090300
    thanks

  • Multiple Value Based hierarchies per MOLAP dimension

    Hi,
    a) Is it possible to have multiple value based heirarchies in a single MOLAP dimension in OWB and deployed to analytical workspace ?
    Are there any pitfalls, that we need to be aware of...
    b) Can we have a mix of Value and level based heirarchies per dimension ?
    Thanks in advance,
    Chakri

    Hi Chakri
    Yes, you can have multiple value based hierarchies and also a mix of value/level based.
    Cheers
    David

  • Multiple Date Fields (Fact Table) - Linking with Time Dimension

    I have a fact table that has multiple date columns.
    I can make a time dimension, but it has to be joined to a particular date column. This becomes difficult because of the limit in having multiple date fields reference one time dimension. I can see possibly
    creating a date table which contains all dates, link to fact as well as time dimension table. I am trying to better visualize the table layout on this one. Or are there possibily better ways of looking at this senerio
    Any idea's

    Figured this one out; going to use one time dimension - what looking too much into the details in regard to this scenerio

  • Unable to use same dimension multiple time for a MOLAP cube?

    Hi,
    I am designing a MOLAP cube that uses the date dimension twice (start/end) but when selecting dimensions for the cube, it doesn't accept the 2nd time I select the date dimension.
    In the date dimension design I gave it 2 role names for this purpose.
    The error that comes up is: The MOLAP storage type does not support multiple references to the same dimension.
    Now I just found out that the User Guide states: Dimension roles can be created for dimensions that have a relational implementation only.
    So how does OWB support implementation of a startdate and enddate in one cube?
    Do we have to duplicate the date dimension in MOLAP multiple times? (Multiple deployment and population using the name of the role??)
    What solutions/work-arounds are in use out there? Any help is appreciated.
    Thanks,
    Ed
    (Oracle 10gR2, OLAP with A patch on Suse Linux x86-64)

    It keeps asking because they are recorded in the database and it can't find them. So they have been delete from outside iPhoto, and iPhoto doesn't know this.
    Simple fix: put the files back where iPhoto expects them to be. Otherwise...
    Try these in order - from best option on down...
    1Download iPhoto Library Manager and use its rebuild function. (In Library Manager it's the FIle -> Rebuild command)
    This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. 
    2. If this doesn't work then you'll need to create and populate a new library.
    To create and populate a new *iPhoto 6* library:
    Note this will give you a working library with the same Rolls and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
    Move the iPhoto Library to the desktop
    Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
    Go into the iPhoto Library on your desktop and find the Originals folder. From the Originals folder drag the individual Roll Folders to the iPhoto Window and it will recreate them in the new library.
    When you're sure all is well you can delete the iPhoto Library on your desktop.
    In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption. 

  • Reference same dimension multiple times in a cube

    Hi,
    I'm creating a cube with Analytic Workspace Manager. The cube needs to reference same dimension more than once. For example, in a movie ticket booking cube, there's a booking date and a show date , both should reference same pre-created TIME dimension. Because one dimension can be added to a cube only once, now my solution is to define 2 dimensions, i.e. BOOKING_TIME and SHOW_TIME, both are based on same underlying table and have exactly same levels/hierarchies/mapping, and then add them to the cube. I believe there must be smarter approaches out there, please advise.
    Thanks!
    Jim
    Edited by: user11955172 on 2012-12-10 上午2:36

    For hand written/custom sql going against the Cube:
    You're right that you can use one of the 3 time dimension based views (duplicated 4 times for time1/2/3/4 dimensions).
    If you need to use 2 out of 4 time dimensions in your query (by applying an application based filter/restriction) then you would need to alias the relevant view(s) 2 times and get your result.
    If you needed to use all 4 time attribute dimensions, then you need to alias the time dimension view 4 times.
    12 views represent the full spectrum of possible report/query usage scenarios available to users via these 4 time dimension views. A typical session with various reports/queries is unlikely to refer to all of them (possible but not likely).
    In different scenarios, any one of the 3 views - dimension view, h1, h2 view - comes into play for each dimension.
    In every query/report scenario, only 1 out of the 3 applicable views would be needed or suitable based on the query/report specifics.
    E.g:
    * If your query is at lowest level and is also referencing attributes/descriptions which pertain to >1 hierarchies, then the view v_time<N>d is the appropriate view to use. Neither vtime<N>h1 or vtime<N>_h2 will be able to give you the results you require if you have attributes defined exclusively in either hierarchy h1 or h2.
    * Setting the default hierarchy to either h1 or h2 determines which hierarchy view is expected to be used/preferred in cases where dimension is not referenced or where Top level of dimension is desired in query/report. E.g: Top level is same for both hierarchies h1 and h2 but read the Top Level values from h1 view as h1 is marked as the default hierarchy for dimension.
    * The level of the query is generally determined by the lowest level of the attributes/fields in your query. If you have attributes like Long_Desc, Short_Desc (available at all levels/all hiers) and you have 2 attributes from Hierarchy H1 and from levels L1 (one level above leaf) and L3 (higher than L1 by 2 levels)... then the query uses v_time<N>h1 and will apply a filter to choose/constraint levelname field = 'L1'.
    * Reporting tools like OBIEE etc. have security filters defined to ensure that the joins to missing dimensions and the appropriate dimension level filters appended to the query in a transparent "behind the scenes" manner.
    NOTE: By modeling the time based fields as different dimensions, you get the benefit of time series analysis along any of the 4 dimensions. You can create a Month-to-Date Revenue measure along "Show Biz Time" dimension and also create a Year-to-Date Revenue Measure based on "Booking Time" dimension. Also compare % variance of "MTD - Revenue - Show Biz Time" with corresponding value for Last year "MTD LY - Revenue - Show Biz Time". This is the benefit you get by breaking out the 4 columns in relational fact and modeling them as explicit time dimensions. You pay a small price in terms of cube space expansion, time dimension load increase but as acknowledged earlier, this dimension can be loaded incrementally, the full load process is done only initially. It is an offline process (batch) and does not hamper query performance.
    Regd
    3) In the underlying star schema, we have only one time dimension table, in the ticket booking fact table, we have 4 dimension columns referencing the same time dimension table. So it's intuitive to expect similar design in the cube. Current approach seems like replicating the dimension table for each dimension column.Do you have parentage along h1/h2 laid out in terms of different parent columns ... 06:30am should have parent D1 in h1 hierarchy (regular day) and parent=D1-1 in h2 hierarchy (business day)?
    h1=regular day hierarchy
    h2=biz day hierarchy
    In that case, perhaps you want "Booking Time" (Time1) to use view: v_time1_h1 by default and "Booking Biz Time" (Time3) to use v_time3_h2 by default.
    Using h2 hierarchy for Time1 or h1 hierarchy for Time3 would be illogical/invalid. Maybe you can simplify things by removing the hierarchies from olap model which dont apply to the dimension.
    HTH
    Shankar

  • SSAS Cube using multiple dimension hierarchies with same key

    How can I link two separate dimension hierarchies (driven from two base dimension tables) to the same attribute in the Cube? When I try this, only the common hierarchy levels between two dimensions show up under Browse. Other levels disappear. Details are:
    One SSAS 2012 Cube: Expense Daily Snapshot Each fact row has CostCentreSK attribute Two dimensions (with natural hierarchies) based on two separate DB tables. CostCentreSK is the key in both. (I know it sounds strange, but there is a good reason for this.
    Be happy to share details.)
    After processing when I browse the cube only the common levels between the two hierarchies show up.
    Expectation was that the individual hierarchies will show each of their levels. Please help.

    @Victor Rocca
    Some dimensions are common, like Dates and Codes, but mostly they are their own dimensions.  Visits
    and Actions facts have foreign keys from Events in them, so I would prefer to join directly, anyway.

  • 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 tune performance of a cube with multiple date dimension?

    Hi, 
    I have a cube where I have a measure. Now for a turn time report I am taking the date difference of two dates and taking the average, max and min of the date difference. The graph is taking long time to load. I am using Telerik report controls. 
    Is there any way to tune up the cube performance with multiple date dimension to it? What are the key rules and beset practices for a cube to perform well? 
    Thanks, 
    Amit

    Hi amit2015,
    According to your description, you want to improve the performance of a SSAS cube with multiple date dimension. Right?
    In Analysis Services, there are many tips to improve the performance of a cube. In this scenario, I suggest you only keep one dimension, and only include the column which are required for your calculation. Please refer to "dimension design" in
    the link below:
    http://www.mssqltips.com/sqlservertip/2567/ssas--best-practices-and-performance-optimization--part-3-of-4/
    If you have any question, please feel free to ask.
    Simon Hou
    TechNet Community Support

  • 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

Maybe you are looking for