Multiple hierarchies for 0ORGUNIT ?

We currently extract the hierarchy ORGEH from SAP R/3 (HR). A new organizational structure is now being created in R/3 which needs to be extracted in to BW (v3.5). However, with the mixture of users we have, some still want to use the old structure while others want to use the new structure. This poses a few questions:
1) Can you have more than one hierarchy associated with 0ORGUNIT? I assume you can.
2) For any reports that use the old hierarchy but now need the new hierarchy, is it a case of changing the hierarchy in the query or is it more complicated than that?
3) For some existing reports, there is a requirement to report historical data but this would mean using both hierarchies. Is this possible and if so how?
4) Could the change in hierarchy structure mean changes are required to roles & authorisations? How can we identify if changes are needed or not?
Any advice will be welcome.

You can't have both hierarchies of a single infoobject displayed on a non structured report at the same time (i.e. in cases where you aren't using a structure and just drilling in 0ORGUNIT).
You can however, setup a variable so that as part of the report parameters, the user selects the hierarchy for viewing meaning they can view the data in the old hierarchy and then click refresh/change variables, select the old hierarchy and compare.
Alternatively, you will need to have a fixed structured report. In such a case, you can have a selection within the report that displays the same KF against each of the hierarchy. In such cases, you are usually only displaying a single node of the hierarchy at a time which is less flexible.
e.g.
HIER1     OTHER CHARS  KF1
HIER2     OTHER CHARS  KF1

Similar Messages

  • How to use multiple hierarchies for a single char in single query

    Hi,
    Is there any way that we can use multiple hierarchies for a single char in single query. I tried and it just allows me to select one hierarchy even if I use hierarchy variable.
    I have a requirement where user wants to see information related to a cost center with different cost center groups in different hierarchies (every year has different cost center group hierarchies).
    Suppose I want to see information related to a cost center from year 2001-2004.in these four year cost center may have been associated to different groups depending upon that year hierarchy. How can I do that?
    Thanks
    Jona

    Nope. Now way to do this.
    There is always just one hierarchy assigned to a characteristic. And even if the hierarchy was time dependent, it only reads it for one key date and not according to transaction data.
    Regards,
    Beat

  • Hyperion Planning : multiple hierarchies for a dimension ?

    Hi,
    Is it possible into planning 9.2 to manage multiple hierarchies for a dimension ?
    I didn't found that in the documentation but I had already listened that there is a workaround to do that.
    Regards

    Hi,
    I would like for the entity dimension used two differents hierarchies (two differents relation Parent/child), one for example used by the accounting service and an other used by the sale service.
    The level0 member are the same but parents are differents in these two hierarchies.
    It's something possible to do into OFA or EPB and I would like to do the same into Hyperion. planning.
    Regards

  • Defining multiple hierarchies for single dimension in Administrator?

    Hello,
    We are attempting to define multiple hierarchies in a single dimension in Administrator. The following two examples are representative use cases for what we're trying to do:
    DateDim
    ----By Calendar Quarter
    --------By Calendar Month
    ------------By Week
    ----------------By Day
    ----By Fiscal Quarter
    --------By Fiscal Month
    ----By Calendar Month
    --------By Week
    Note that "By Calendar Month" can't really be a shared level because we do not want to include "By Day" in the third hierarchy.
    ServiceLocationDim
    ----By Sales Region
    --------By State
    ------------By City
    ----By State
    --------By City
    ------------By Zip
    ----------------By Store
    Note again that "By State" can't be a shared level because its children differ in the two hierarchies.
    The goal is to have multiple drilldown paths supported. If there is a different way to do this in Administrator that does not use hierarchies, that would be acceptable.
    Can anyone point me in the right direction?
    Thanks,
    Matt Warden
    Balanced Insight, Inc.
    http://www.balancedinsight.com

    Hi,
    when defining multiple hierarchies in a dimension, the lowest level needs to be the same for each hierarchy...that's a prerequisite.
    But I think you can define them this way...and restrict your 'drill' level on your fact table...as I think you will have a different aggregation level overthere.
    So for your dimension you'll set the logical level on the lowest level and in your fact you can play with the logical level depending on to the drill level?
    Can that help you?
    A.

  • Multiple hierarchies for one dimension

    Hi
    I'm building a repository with The administration tool of OBIEE. the data source is an Oracle 10g datawarehouse created with OWB.
    There is a geographic dimension with 4 different hierarchies and I want to create the same hierarchies in my repository.is it possible with OBIEE??
    NB: The 4 hierarchies share some of the logical columns.
    Thanks

    Hi...
    Are you looking for This
    Just try.. it
    Thanks & Regards
    Kishore Guggilla

  • Can Multiple Hierarchies for Entity fits into Consolidation? Please respond

    Hello Gurus,
    Here is a strange requirement from our Buisness Users. We are implementing BPC 7.5 NW primarily for Consolidation.
    High Level Managerial Team wants Consolidated Statement by Operational G/L Account (Have only 1500 GL Accounts hence requested to go for Op GL)  by Entity (Company Code).
    But now they want to compare this Consolidated Actuals with Budget and hence they changed the scope and were requesting to bring in Consolidated Fin Statements by Enity, Account, Profit Center, Cost Center, Functional Area and Segment.
    Question 1:
    Is this possible to have all of these Dimensions in One Main Application? By the way they are doing Managerial Consolidation.
    Question 2:
    As Eliminatiosn will be done on Entities, are these Eliminated Results reflects on all other Dimensions like say Cost Center, Functional Area, Profit Center and Segment. Based on my knowledge I have told them they can only see these Dimesions in Reports but dont expect to have the Eliminations done on any of these add on Entities.
    They are fine with that but they wish to see Eliminated Results to be reflected by Segment also. Which in other words they are wishing to see Elimnations of Legla Entites (Company Codes) at two different Roll Ups One at Consolidation Group Level and One at Segment Level
    Is this a possible scenario or not?
    From my understanding that the Entity Structure is maintained with 2 Parent H1 Propetrties. If it is possible can Dynamic Hierarchies will help us in any way?
    Kindy help us with quickest possible solution.
    Thanks,
    BIBPC

    Based on my experience of other consolidation SAP modules, especially SEM-BCS and ECCS, for such requirements you would need to defined what we called "consolidation matrix", that is to say create a structure where you need to combine the Entity dimension and the other core dimension (Segment or Profit Center for example). The purpose is that the system would then include both dimensions in the consolidation calculations. Example : the inter-unit eliminations should have to be performed between entities and Segments. So in other words, you would need two dimensions with the type "Entity".
    But when you read the official SAP help, it's said that a BPC application can only have one dimension of type "Entity"...
    There might be a workaround such as creating another application where you perform you management consolidation. That's for example how they did in the SAP starter kit.

  • Support for Multiple Hierarchies defined for the same GL Segment

    Hi,
    In our eBS setup, we have multiple hierarchies defined for a GL Segment.
    OOTB, BI Apps 7.9.6.3 provides support for 10 Segments, and it's corresponding Hierarchies (1 Hierarchy for each Segment).
    My question here is whether OOTB BI Apps 7.9.6.3 supports Multiple Hierarchies for the same Segment?+
    Thanks,
    Ab

    no it is not supported OOTB as of today
    you need to customize ETL mappings and OBIEE metadata to include hierarchy identifiers from the EBS segment definitions.
    Then you have to consider that filtering a hierarchy identifier becomes mandatory during query execution to avoid aggregation of duplicated values.

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

  • Dimension Design - Single Dimension with Multiple Hierarchies

    Morning,
    the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
    We have an institution dimension with the following characteristics:
    Characteristics
    Dimension: Institution
    Levels:
    1. Total Bank (TB) Level
    2. Peer Group (PG) Level
    3. Institution Level
    Hierarchies:
    1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
    2. ALL the hierarchies have a TB level and an Institution level
    3. None of the hierarchies have the same leafs
    4. Some of the hierarchies leafs can overlap
    Design:
    We are considering two approaches for the institution dimension levels:
    a)
    Levels:
    Hierarchy 1 TB Level
    Hierarchy 1 PG Level
    Hierarchy 1 Inst Level
    Hierarchy 2 TB Level
    Hierarchy 2 Inst Level
    Hierarchy 3 TB Level
    Hierarchy 3 Inst Level
    Note:
    This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
    At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
    b)
    Levels:
    1. Total Bank (TB) Level
    2. Peer Group (PG) Level
    3. Institution Level
    The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
    The cube associated with this dimension have approximately 80 million records.
    Please advise on any best practices or design considerations that we need to take into account.
    Thanks

    No, it is not possible to have multiple hiearchies in a PC logical dimension.
    The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
    Short story even shorter it is not possible.
    Longer...
    In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
    On another note...
    Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
    That was a great question, please award points if this answered your question or it was helpful.
    Cheers,
    Christian
    http://www.artofbi.com

  • Discoverer support for multiple hierarchies

    Hi all,
    is it true that Discoverer supports only a single hierarchy per Analytic Workspace dimension?
    If this is true what is the recommended work-around:
    - create an AW dimension per hierarchy?
    - forget about analytic workspaces and take a ROLAP approach?
    - other?
    thank you in advance for any hints
    Nikos

    I'm not a discoverer user, so what I say might not apply, but in general it usually doesn't make sense to select members from multiple hierarchies. This would give end users of a report the ability to select values that don't accurately represent the total levels displayed.
    I guess my questions would be:
    a) what business value does picking dim values from multiple hierarchies serve?
    and
    b) it is possible in discoverer to simply not select any hierarchy and just choose the dimension values without one? Would that solve your problem?
    I guess high level this doesn't sound like either a bug or non-functional support issue, it sounds more like intended functionality.
    Let us know what your needs are! Maybe we can give a better answer if we know what business problem you are trying to solve.
    Thx,
    Scott

  • Multiple KPI for the same Initative or Perspective

    Hi all,
         Here we are facing a problem with a customer BSC model that we need to adapt to SAP SSM
       The customer has the following  BSC structure ":
       1)  Multiple KPIs for ONE Perspective ( in SSM the maximum that we have it is a Perpective related to one KPI )
       2)  Multiple KPIs for an Objective ( Ok, SSM  is OKJ in this point )
       3)  Multiple KPIs for an Initiative ( in this customer they use a Initiative as a lower level of the Objective )
           ( in SSM a Initiative is associated only with one KPI if necessary )
       As we can see the itens 1 and 3 I see a limitation to adopt in SSM cause SSM  does not provide a n for n relationship ( Multiple KPIs for One Perspective and
         Multiples KPIs for a same Initiative )
       Does somebody knows how can I solve this kind of SAP SSM tool limitation ?
       Regards,
          Alfred

    Alfred,
    Index KPIs is going to be the solution for each of these questions.
    1) Multiple KPIs for ONE Perspective ( in SSM the maximum that we have it is a Perpective related to one KPI )
    SSM is set up in a hierarchical structure, so that the assumption is that KPIs drive Objectives and Objectives drive the status of the Perspectives. If you have multiple KPIs that are going to drive the status of a Perspective, you would have to create an INDEX KPI in Set KPIs. Then you can assign that KPI as the status driver for your Perspective.
    2) Multiple KPIs for an Objective ( Ok, SSM is OKJ in this point )
    Index KPIs need to be created.
    3) Multiple KPIs for an Initiative ( in this customer they use a Initiative as a lower level of the Objective )
    Initiatives are set to be tied to Perspectives and Objectives and you have the option of setting a Status for that Initiative based on a KPI. Again, you can create an Index KPI if you need multiple KPIs to drive the status of an Initiative
    The reason that you have to create these in Set KPIs and then assign that Index KPI to Perspectives and Initiatives is that you need to use that Set KPIs area to set and define the relationships and relative values of the combined KPIs.
    Regards,
    Bob

  • Multiple Hierarchies in one dimension - comments?

    multiple hierarchies
    Hi Experts,
    I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
    a) still enables users to choose the hierarchy in a dashboard prompt
    b) reduces maintenance to a minimum
    The dimension groups ages into several different groups like the example below:
    Hierarchy1 Hierarchy2
    Age......Groups........Groups.....
    0........0-2...........0-5
    1........0-2...........0-5
    2........0-2...........0-5
    3........3-5...........0-5
    4........3-5...........0-5
    75.......70-75.........70-80
    76.......76-80.........70-80
    Right now I've implemented this by defining one dimension having one hierarchy:
    Total
    ....Hierarchy
    .......Group
    .........Age
    The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
    Columns in the logical table (and of course in the underlying LTS) are:
    Column               mapped to hierarchy-level
    - Hierarchy          Hierarchy               
    - Hierarchy_id          Hierarchy
    - Group          Group
    - Group-id          Group
    - Age               Age
    Advantages:
    A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
    Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
    Disadvantages:
    A new grouping needs manual steps to implement
    - a new physical table
    - a new LTS attached to the logical table (including the fragmentation content)
    Thanks for your time and comments
    Regards
    Andy

    multiple hierarchies
    Hi Experts,
    I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
    a) still enables users to choose the hierarchy in a dashboard prompt
    b) reduces maintenance to a minimum
    The dimension groups ages into several different groups like the example below:
    Hierarchy1 Hierarchy2
    Age......Groups........Groups.....
    0........0-2...........0-5
    1........0-2...........0-5
    2........0-2...........0-5
    3........3-5...........0-5
    4........3-5...........0-5
    75.......70-75.........70-80
    76.......76-80.........70-80
    Right now I've implemented this by defining one dimension having one hierarchy:
    Total
    ....Hierarchy
    .......Group
    .........Age
    The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
    Columns in the logical table (and of course in the underlying LTS) are:
    Column               mapped to hierarchy-level
    - Hierarchy          Hierarchy               
    - Hierarchy_id          Hierarchy
    - Group          Group
    - Group-id          Group
    - Age               Age
    Advantages:
    A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
    Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
    Disadvantages:
    A new grouping needs manual steps to implement
    - a new physical table
    - a new LTS attached to the logical table (including the fragmentation content)
    Thanks for your time and comments
    Regards
    Andy

  • Using HLEVEL Property with Multiple Hierarchies

    Hello,
    I am trying to use the HLEVEL property on a dimension to indent the rows different amounts. Easy stuff, except I'm doing a row expansion on hierarchy 3 (H3).  Using EVPRO(AppName, MemberID, "HLEVEL") always returns the HLEVEL from H1.  If you select the same member ID in the member selector under different hierarchies and click the Properties button you can see a different value for HLEVEL, but I can't figure out how to get that in a report using EVPRO.
    Is there a way to tell EVPRO specifically which hierarchy to use when returning the value for HLEVEL?
    Thanks!
    Paul Petersen
    Akili

    Mike,
    please check the answer in this other post:
    EVPRO with multiple hierarchies
    It's for the MS platform, but it's the same for Netweaver.
    EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
    Regards,
    Simmaco

  • Drill with multiple Hierarchies

    Hi,
    I have defined multiple hierarchies in an OLAP universe (like state>region>customer>product or state>region>customer segmentation>Product or state>region>product ...) in order to use the drill functionnality in webi.
    In our scenario, each webi report should use only one hierarchy and we don't want the user to have the choice between the different hierarchies when he drills down. So is there a way to define in a webi report what hierarchy should be used?
    Thanks,
    Gabriel

    hi,
    As 'State' object is the starting point for both the Hierarchies,
    Please duplicate the state object and place it in other class. (as two objects with same name shouldn't exist in same class)
    Now edit  the second hierarchy such that new State Object will be the starting point.
    Also , please ensure that 2nd WEBI report uses new State Object in Query Pane.
    This will prevent 1st hierarchy in 2nd webi report.
    I tried this out and it's working.
    Regards,
    Vamsee

  • Multiple Hierarchies from Single Dimension Table in OBIEE-11g?

    Is it possible to have Multiple Hierarchies from Single Dimension Table in OBIEE-11g?
    Like 1)Year-Qtr-Month-Weeks 2)Year-Month-Days

    Hi,
    or if your lowest level is the same like
    Day->month->year->Total
    Day->businessMonth->businessyear->Total
    Then yes, it is.
    Create the first, then you start to create the second by adding your top(business year) level on the same level as the one you have (year) both under your total.
    Then when you would add your second base level, there is a special option for it, something like use other hierarchy level/shared level (sorry can't recall and does not have a connection right now) then you select your existing day level under your businessmonth level.
    Hope this helps,
    Regards,
    D

Maybe you are looking for