Ragged Hierarchies

We have a ragged hierarchy where there may be a case where the data level in a parent-child hierarchy is blank.
Is there a way to use the parent value instead of the blank value so that all of the levels of a parent child hierarchy in a ragged hierarchy have a value.
Doing this would result in repeated values for the data levels that are blank.
Ryan P. Casey • <a href="http://www.R-P-C-Group.com">www.R-P-C-Group.com</a>

How do I set Visual Studio and SSMS (Browse Cube) to use the SSAS Connection String that includes MDX Compatibility=2
Hi Rpcasey001,
MDX Compatibility is one of Special-purpose parameters connection string properties when connecting to Analysis Services. It's valid values include 0, 1, 2. 0 and 1 expose placeholder members; 2 does not. If this is empty, 0 is assumed.
In Visual Studio, I cannot find a place that we can specify this property. In SQL Server Management Studio, we can specify this property when connect to AS instance. (Options>>Additional Connection Parameters)
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Similar Messages

  • Ragged Hierarchies and extra joins

    We have an ORG_DIM with a three-level logical hierarchy (LVL-All, LVL-1, LVL-2, LVL-3 -- the leaf/detail level). The primary key is LVL3_KEY; LVL2_KEY and LVL1_KEY are level keys. We have a SYS_DIM with the trival (all/detail) logical hierarchy and SYS_KEY primary key.
    We have a base fact and two aggregate facts -- LVL1_FACT, LVL2_FACT and LVL3_FACT (level 3 is the base); the logical Fact - Lvls has an LTS for each of these physical fact tables. The base fact (LVL3_FACT) has LVL13_KEY and SYS_KEY as its primary key and also has columns LVL2_KEY and LVL1_KEY; the aggregate facts lose LVL3_KEY and LVL2_KEY, respectively.
    ORG_DIM represents a flattened skip-level hierarchy. (There are actually more levels and more tables, but I am simplifying the problem for this description.)
    We also have an ORG_STACK table (ORGNAME, ORGKEY, PARENTORGKEY, LFT, RT, STACKLVL), following a method for implementing ragged hierarchies proposed by Kurt Wolff and Joe Celko. The ORG_STACK table has three aliases -- ORG_PARENTS, ORG_CHILDREN and ORG_LEAVES. The first two are joined on (ORG_CHILDREN.PARENTORGKEY=ORG_PARENTS.ORGKEY). The latter two are joined on (ORG_CHILDREN.LFT BETWEEN ORG_LEAVES.LFT AND ORG_LEAVES.RT) -- a complex physical join. ORG_LEAVES joins to LVL3_FACT on ORG_LEAVES.ORG_KEY=LVL3_FACT.LVL3_KEY. The logical Fact - Lvls has a 4th LTS in which ORG_LEAVES and LVL3_FACT are joined.
    We run a query in answers that invokes columns from logical tables Dim - OrgChildren, Dim - OrgParents and Fact - Lvls; one of the columns from Fact - Lvls is mapped only in the LTS that joines ORG_LEAVES with LVL3_FACT. This query spins for a long time without returning any result, so we end up cancelling it. We intend to have a DBA look at it.
    The generated SQL includes those tables (ORG_STACK aliases and LVL3_FACT) plus ORG_DIM and SYS_DIM. We can see nothing in the query that requires ORG_DIM or SYS_DIM; how can we determine why these are included in the SQL?
    Queries that used columns from Dim - Org also showed poor performance after the other Dim - OrgXXX (the stack suff) were added. Presumably this was because the LTS for Fact - Lvls that maps to LVL3_FACT also joined the (much larger) ORG_STACK table via ORG_LEAVES. Adding the 4th LTS for that (leaving the 3rd LTS mapped only to LVL3_FACT) should have resolved this. However, the interesting this is that removing the logical join between Dim - OrgChildren and Fact - Lvls resolved this problem. If the problem was ORG_LEAVES and LVL3_FACT joined in the LTS, then removing a logical join should not have affected it.

    Chandra Kanth,
    Hope this helps you
    http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
    Thanks,
    Saichand.v

  • Support for ragged hierarchies?

    Are ragged (i.e. variable depth) hierarchies supported in Universe Designer? Do any of the Business Objects tools provide support for ragged hierarchies or is this considered an ETL/data modeling issue?
    We are embarking on a project using the Data Services, Universe Designer and Xcelsius tools and we are trying to figure out how to handle ragged hierarchies.
    Thanks!

    Hi Didier ,
    I have gone thought the document of Universe design tool :- SAP Business Objects XI 4.0 created on 2010-12-24 on SAP Portal .
    This document dont have any information regarding the Ragged Hierarchy .
    Can you please let me know whether downloads of SAP Business Objects BI 4.0  which are available on SAP Portal Supports ragged Hierarchy or We need to wait for next patch or release?
    Regards ,
    Jeevan

  • Fin Reports - Ragged Hierarchies

    Hi,
    Is it possible to define the level 1 members of a certain parent value in the report?  I have a ragged hierarchy and I need to get all level 1 members from the Cost of Sales member in the Accounts.   Can't figure out how to do that.
    Thanks in advance

    Yes.  This is possible in FR.  Here are the steps:
    1)  Select your account in the FR report grid (presumably in the rows).
    2)  Press the Account button to get your member selection window.
    3)  Select the "Lists" tab.  Select "Lev1, Account".
    4)  Select the "Functions" tab.  Select "Descendants" and select your "Cost of Sales" member.
    5)  Press the "View" button (upper right corner).  Select "Advanced".
    5)  Change your operator to "AND".
    Now you should have "Lev1, Account" AND "Descendants of Cost of Sales" in your "Selected" window.  Press "OK" and test.
    Hope this helps,
    - Jake

  • EIS and ragged hierarchies - Lev or Gen builds?

    I have a ragged hierarchy where the source table is setup for GEN builds (the columns for the GENs past the end of the branch are NULL). This doesn't seem to work for me - when I look at the SQL EIS used to load data, it has NULL for the dimension members. Do I need to switch this around and use the equivalent of Level builds?

    I think instead of nulls you just need the empty gens to be blank??

  • Do BI Beans support ragged or skip-level hierarchies

    Do BI Beans support ragged or skip-level hierarchies ?

    Hi Alexander.
    Well I am also a positive person ;)
    Here it goes....
    In the guide page 93/412
    Oracle® OLAP
    Application Developer’s Guide
    Release 9.2.0.4.1
    Part No. B10333-01
    "Dimension Tables with Complex Hierarchies
    If your source data is a star or snowflake schema, but the dimension tables include
    any of the following variations, then use the CWM2 APIs:
    -> Level columns containing NULLs, such as skip-level hierarchies
    -> Multiple hierarchies with different base levels (sometimes called ragged
    hierarchies)
    -> Multiple hierarchies with values mapped to different levels
    -> Parent-child dimensions
    Choosing a Tool for Creating OLAP Catalog Metadata
    If your schema contains parent-child dimension tables, then you must convert them
    to level-based dimension tables. The CWM2 write APIs include a package for this
    transformation."
    You can use the next three steps to add different levels and do the mappings you want!
    CWM2:
    execute cwm2_olap_level.add_level_to_hierarchy
    execute cwm2_olap_table_map.Map_DimTbl_HierLevel
    execute cwm2_olap_table_map.Map_DimTbl_HierLevelAttr
    Best regards.
    Odds

  • Best way to create hierarchies tables

    Good morning all,
    I wanted to discuss the best practices of creating hierarchies to be consumed by OBIEE. As far as I understand, OBIEE has been optimized to use flattened hierarchies, such as:
    ROW_WID CITY COUNTRY
    1 NEW YORK CITY USA
    2 MOSCOW RUSSIA
    3 KIEV UKRAINE
    4 SYDNEY AUSTRALIA
    5 ATLANTA USA
    Let's call it option 1. The only problem with this is that it has a potential to grow very wide. Also, There's a chance for confusion when there're duplicate entries, such as "New York" (city) and "New York State". Also, it's not always possible to define hierarchical relationships between data in a flat table - so-called ragged hierarchies. I found two major way of dealing with those (stack and flattening them out). Are there any other ways to deal with those? Specifically, I'm interested in dealing with hierarchies that involve complex positioning (a person might be a manager vertically, but managed horizontally - or - a person can have 2 managers - on different levels).
    Also, in the example above - can I create dimensional outriggers (assign surrogate keys instead of text values to the dim - such as having NEW YORK as 100, MOSCOW as 200)? Sort of snowflaking a dimension. I was asked to do a proof of concept for this - but haven't been successful so far. If yes, could you please provide a simple Dim Outrigger < Dim < Fact diagram.
    Thank you

    Thanks Peter - I've checked that document before (I believe it's based on Kurt Wolffe's document on Siebel Analytics which I checked as well).
    This option is fine if you're not going to do frequent changes - but in my case - it'll be a hell to maintain. We're sort of trying to prototype best solution - and it seems as flattening hierarchies is the best option, of course, given its limitations.
    Also, there's another option of taking a different path and splitting and then building separate hierarchies

  • OLAP on 11g and Materialised Views with Multiple Value-Based Hierarchies

    Hello OLAPians
    I am trying to setup Orable BIEE to report on an OLAP cube with pre-aggregated data. As OBIEE is not able to hook into the OLAP directly i have to create an SQL cubeview.
    Currently i am on a 10g OLAP environment and am using the oracle sample SQL cubeview generator to create an SQLview of my cube.
    The cube itself has multiple dimensions and these dimensions have multiple VALUE-based (ragged) hierarchies and dimension members can be shared across hierarchies also.
    Initially i had a problem running the view generator plugin because there is a bug within it that does not finish if there are multiple value-based hierarchies present. I was able to get around this by manually editing the limitmap for the cubeview and manually creating the SQL view.
    The question that i want to ask is how robust is the 11g materialised views with multiple value-based hierarchies and the sharing of dimension members across different hierarchies?
    Has anyone successfully been able to create a cubeview and import it into OBIEE without the hassle of manually editing the limitmap?
    A problem arises with the value-based setup whereby if the client creates a newer depth in the ragged hierarchy, i need to manually create the limitmap and the cube-view over again, and then re-map the BI Administration mappings.

    The simple answer to your question,
    how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
    But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

  • Multiple hierarchies with a shared higher level in OBIEE

    Hello all,
    I'm trying to create multiple hierarchies for a shared dimension in OBIEE. I have gotten these to work in the past when each hierarchy for the dimension all shares the common “grand total” level at the top, but I now I'd like multiple hierarchies that share a common higher level that isn't the grand total level.
    Here's what I'm trying to do with a Customer Geography hierarchy. I want to give the user the option to drill from the customer "Country" and go either into "Cities" or "States":
    Grand Total level
    --->Country level
    ------> State level
    ---------> Customer detail level
    ------> City level
    ---------> Customer detail level
    So "Country" is the common parent of "State" and "City", and "State" and "City" each have" Customer detail" as the lowest level. The Admin Tool let's me build exactly this in my RPD (with no errors/warnings), but when I go to drill on Country in an Answers report, I don't get the option to navigate down to State or City; it just automatically drills into the underlying states -- never shows cities.
    I guess I was hoping there'd be a pop up option to ask the user which path I wanted to drill down on (kind of like what shows up for multiple navigation targets in an Answers request).
    Am I missing a setup step in my RPD for this multiple hierarchy? Is a shared higher level multiple hierarchy even possible in OBIEE?
    Thanks,
    Jeremy
    Edited by: OBI Wan on Mar 19, 2009 3:29 PM
    Edited by: OBI Wan on Mar 19, 2009 3:30 PM
    Edited by: OBI Wan on Mar 19, 2009 11:20 PM

    Thanks mma for the help. I thought I saw in your reply this link as well to RittmanMead, but it's not showing up now?
    http://www.rittmanmead.com/files/Advanced%20Development%20using%20OBIEE%20(ODTUG%202008).pdf
    Anyway, on slide 37 of Rittman's presentation, that screen shot he has of Country, City, and State is exactly what I am attempting to do. I was hoping my issue would be a bit more straightforward than the recommended ragged hierarchy work arounds, but I may still have to do something like that in the end.
    This issue just seems more simple than ragged hierarchies, because I start from the same level and end up back at the exact same level (instead of different destination levels as can be the case in ragged hierarchies). I don't know -- maybe my example is ragged as well.
    If Rittman got that hierarchy in his screen shot on slide 37 to work like I'm trying to, then that would be perfect. :)

  • OBIEE 10g - Ragged & Skip Level Hierarchy

    Hi Frnds,
    I'm aware of the fact that OBIEE 11g supports Ragged & Skip Level Hierarchy. But I'm looking for some heads up while implementing the same on OBIEE 10g using Oracle DB as source. I have done this before for Essbase Data Source but now waiting for my Oracle dataset for design.
    Has anyone actually implemented in Real Time Project? Pls share your challenges like:
    - Dimensional Hierarchies Challenges
    - Drill Down Challenges
    - Report Challenges
    Thanks,
    Deepak
    Edited by: Deepak Gupta on Aug 11, 2011 5:18 AM

    Deepak,
    10g does not handle the idea of Skip hierarchies and the ragged hierarchies definitely has its limitations.
    We've implemented several projects using Essbase and SAP BW for Oracle BI 10g. The biggest issue is that in Answers creates a new column for each drill down selection when attempting to navigate down a hierarchy. Though this is klugy it does work and provides the data the user is looking for. It is however, not aesthetically please when compared to other tools or now Oracle BI 11g which satisfies this issue with a native drill-down tree folder structure.
    My opinion and advice would be to upgrade to 11g as soon as possible to enjoy these new features.

  • Problem with skip-level hierarchies

    Hi,
    I have created metadata using CWM2 procedures. These procedures allow define skip-level or ragged hierarchies.
    I created skip-level hierarchies by setting null values to several keys in dimension table.
    The result is... OLAP did not created cursor error, when I try to drill that hiuerarchy?
    Why?
    How to build BIBeans compatible skip-level hierarchies and?
    My next question: Is it possible to use BIBeans with fact tables which contain embedded totals?
    Slawek.

    Hello Vicky,
    Products created in R/3 can always be downloaded to CRM using the download object MATERIAL.
    But products created in CRM could not be recovered back unless you archive them in CRM.
    In order to delete the materials in CRM , you can use report COM_PRODUCT_DELETE_SINGLE or COM_PRODUCT_DELETE_ALL.
    You can then download these materials from R/3.
    Or you can have your own Z-report using the above standard report, where you can pass on the material id or range.
    Also,please note that before executing these reports, you need to make an entry in table COMC_PR_TOOL_REG.
    Hope this helps!
    Best Regards,
    Shanthala Kudva.

  • Ragged hierarchy - cube 2008

    I'm trying to create ragged hierarchy with no success. I need to hide the middle level (level 3) and I put the same code and name to the level 3 as in Level 2 (which is higher). But I keep seen all the levels. I'm using "OnlyChildWithParentName"
    option and I'm connected with MDX Compatibility=2 (I don't know how to set this property in the other way) .
    Do you have a solution to my problem?

    Hi Tatyanaa,
    According to your description, you are trying to create ragged hierarchy with no success, right?
    Generally, if we want to turn a user hierarchy into a ragged hierarchy (perhaps to avoid using a parent child hierarchy) we need to use the HideMemberIf property on the user hierarchy. Here is a blog which describe Ragged Hierarchies, HideMemberIf and MDX Compatibility,
    please see:
    http://cwebbbi.wordpress.com/2009/11/11/ragged-hierarchies-hidememberif-and-mdx-compatibility/
    Regards,
    Charlie Liao
    TechNet Community Support

  • Ragged hierarchy design

    Hi.
    I'm trying to design the implementation of a department dimension that has a ragged hierarchy and I'm seeking advice on how to do this.
    I'd like to start a dialog on the community's experience and best demonstrated practices on how to do this.
    Has anyone done this successfully? If so, what did you learn in the process and what did you do to ensure success.
    Thanks.
    Dan

    Hi. Sorry for the long delay...Got pulled in another direction...
    So, I'm revisiting ragged hierarchies. I understand pushing down/replicating the levels. Some more back story. I used the OWB Create dimension expert to generate the dimension, mapping, etc for me and it worked well. However, it does not push down the levels. For example, I have a leaf at level 5, but need it to be pushed down into levels 6 - 8.
    Has anyone out there done this sort of work in OWB before, if so, can you offer advice, tips, tricks, diagrams, code, anything? I'm simply stuck at this point.
    Thanks for your time.
    Dan

  • Unbalanced hierarchies in OBIEE+

    Hi everyone,
    We're starting to research and learn OBIEE+ in an effort to see if it can compliment what we're currently doing with the Hyperion toolset and the first stumbling block that I've encountered is with unbalanced (ragged) hierarchies. Does OBIEE+ natively support building a business model with unbalanced hierarchies? My data model is basically a star schema and my dimensions are stored in parent / child relationship tables rather than generational tables. Second question is if there is any native functionality within the product to handle parent / child relationship tables.
    Thanks!

    do search - There're few excellent blog posts describing in detail how to implement rugged hierarchies...
    www.rittmanmead.com/2007/06/21/obiee-data-modeling-tips-3-ragged-hierarchies/
    this one to get you started
    Message was edited by:
    wildmight

  • Analytic Workspace Manager - Hierarchies within hierarchies

    Hi,
    We have six levels of Sales Groups (SG) and two levels of Sales Personnel (SP).
    - SG1
    SP1- Sales Manager
    SP2- Sales Rep
    - SG2
    SP1
    SP2
    - SG3 ... so on and so forth
    We want to have drill down capability on SG1 so that we see SP levels underneath followed by the next level Sales Group i.e. SG2.
    My question is can we have hierarchies within hierarchies using Analytic Workspace Manager and can this be queried using Discoverer Plus for OLAP. If there is another way to do it, can someone please explain?
    Thanks again,
    -Esther

    I am not totally sure what you are trying to achieve as I think you might be confusing members with levels. From an OLAP perspective we support two basic types of hierarchies
    - Level based
    - Value based (Parent-Child)
    Within level based we additionally support:
    - normal
    - ragged
    - skip level
    Normal implies that you have a hierarchy where the each member for each level always has a parent at a the next level up in the hierarchy. Ragged hierarchies are where data is loaded at different levels within the hierarchy and skip level is where parents within a specific level are themselves defined at multiple levels.
    I am not sure if this answers your question, but you can find more information on how to manage hierarchies in the
    Oracle® OLAP Application Developer's Guide
    Section 3 Creating an Analytic Workspace
    Creating Hierarchies
    http://www.oracle.com/technology/products/bi/olap/OLAP_App_Dev_Guide_10.2.zip
    Hope this helps
    Keith
    Oracle Business Intelligence Product Management
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Beans http://www.oracle.com/technology/products/bib/index.html
    Discoverer: http://www.oracle.com/technology/products/discoverer/
    BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
    Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
    BI Samples: http://www.oracle.com/technology/products/bi/samples/
    Blog: http://oraclebi.blogspot.com/

Maybe you are looking for