Planning Analytics

 View Only
  • 1.  hierarchy multi PAW

    IBM Champion
    Posted Fri October 07, 2022 05:17 PM
    Edited by System Fri January 20, 2023 04:28 PM
      |   view attached
    Hi everyone,

    I have 5 years experiences with TM1, but i am still a newbie on the new version of TM1 (Planning Analytics Workspace).

    I have an client who want to make a fusion with their affiliate (in terme of TM1) but they want to keep all structure of affiliate (they will fusion soon but right now, they want to make a slow move)

    there are a lot of work, then i try to make my question as simple as possible.

    Then they want to make a dimension like "Company_account" with all the account of group but with the different hierarchy.

    for exemple :

    - 1 hierarchy Total with all account
    - 1 hierarchy Total_Company with all account of holding company (structured by holding company)
    - 1 hierarchy Total_Affiliate for each Affiliate with all account of each affiliate (Structured by each affiliate)

    [b]Usually, i just create a lot of consolided element then try to make something like photo "hierarchy - real hierarchy"[/b]

    One of my friend tell me that from now, TM1 can do a multi hierary virtuel that work only on PAW but it work very well and i have to try.

    Then i make a research about that, i found that we can use this function if we dont have so much need for active form (as can do almost all my old report to PAW exploration view).

    My plan is make a dimension with a Total element with all account, then for each account, i will put some attribut that help me create all the hierary virtuel by TI.

    as i never use before, please give me a feedback about this function on PAW !

    - if i create a new hierarchy virtuel in a old dimension, will it affected my old TI process and my old rules? ( i ask this question because i read in a article that we have to put hierarchy reference to make rule work (for exemple [b]not [/b]DimensionName:ElementName [b]but [/b]DimensionName:HierarchyName:ElementName)

    - why we should use hierarchy virtuel? what beneficial that i have compare to old systeme ? (consolided hierarchy)

    - what is the best pratice for this?

    - is my plan good enough to maintain the hierarchy virtuel?

    Thank a lot for all help!!

    same post in TM1 forum : https://www.tm1forum.com/viewtopic.php?t=16322






    ------------------------------
    Duong DAU
    Consultant EPM Finance Transformation & Performance - Micropole


    M +33 (0)7 62 61 85 33
    F +33 (0) 4 26 99 60 81
    131 Boulevard Stalingrad / 69100 Villeurbanne
    ------------------------------
    #PlanningAnalyticswithWatson


  • 2.  RE: hierarchy multi PAW

    Posted Tue October 11, 2022 11:34 AM
    Hi Duong

    Your approach is a good way to transition to a single account structure. You can even use security if you want some user groups to see only specific hierarchies.

    Alternative hierarchies are very useful! First of all, you can make your dimension navigation super clean. I personally try having a single top consolidated element for each dimension/hierarchy (except measure dimensions), as you can expect that element to contain the grand total value. If you need roll ups, you just use a different alternative hierarchy. Now when you fully expand the dimension you don't see duplicate elements. It much more easier to navigate compared to using multiple top consolidated elements.
    You can use the same dimension for different analysis, for instance you can create a hierarchy by attribute or simply organize elements in a different way.
    You just need to keep in mind the leaf level elements are shared across all hierarchies and you cannot have the same named elements as a leaf element in hierarchy 1 and as a consolidated element in hierarchy 2
    In one of my projects, I have a requirement to keep historical hierarchy snapshots,  alternative hierarchies help with this a lot. Imagine keeping historical consolidation nodes within a single hierarchy 
    TM1 also creates LEAVES alternative hierarchy automatically.
    Sometime you have to duplicate rules for alternative hierarchies (as I remember there was a request to allow rules to apply for all hierarchies)
    Similar to dimension security, you define security for alternative hierarchies 
    You also define security for elements in alternative hierarchies

    There are many other advantages

    ------------------------------
    Vlad Didenko
    Founder at Succeedium
    TeamOne Google Sheets add-on for IBM Planning Analytics / TM1
    https://succeedium.com/teamone/
    ------------------------------



  • 3.  RE: hierarchy multi PAW

    Posted Wed October 12, 2022 08:41 AM
    Good summary on alternate hierarchies, Vlad!
    I could just add that going with the hierarchies is also beneficial in some cases for performance,

    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------



  • 4.  RE: hierarchy multi PAW

    Posted Fri October 14, 2022 02:31 PM
    I could just add that going with the hierarchies is also beneficial in some cases for performance...
    That's a very good one @Svetlana Pestsova​! Indeed, sometimes you can significantly reduce the number of elements per hierarchy which could significantly improve the performance.

    ------------------------------
    Vlad Didenko
    Founder at Succeedium
    TeamOne Google Sheets add-on for IBM Planning Analytics / TM1
    https://succeedium.com/teamone/
    ------------------------------