Forum Discussion

Ghizlane's avatar
Ghizlane
New Contributor II
3 days ago
Solved

Percent Consolidation Behavior

Hi,

We are currently attempting to exclude a specific entity from the main consolidation process for reporting purposes. This entity is no longer within scope, but we would like to keep it in its current position in the hierarchy to preserve historical data. We also need to continue importing data into this entity for reporting purposes. Our objective is to set the consolidation percentage to 0% so that it no longer consolidates going forward.

After updating the Percent Consolidation to 0%, we are not seeing any impact. The entity continues to consolidate in the application.

For context, the Ownership Type is set to Full Consolidation and the Consolidation Algorithm Type is set to Custom.

Is this expected behavior? If so would you have any workaround solution ?

Thank you for the feedback and help!

Application Properties
Consolidation
Metadata
  • Ghizlane's avatar
    Ghizlane
    1 day ago

    Hi,
    We found out that in the rule, this api.ExecuteDefaultShare(100) call 
    was overriding the logic we were looking to achieve.

    Thanks for the support !

5 Replies

  • T_Kress's avatar
    T_Kress
    Icon for OneStream Employee rankOneStream Employee
    3 days ago

    Yes, the % Consolidation should work as follows:

    • Assuming you have no custom consolidation BRs
    • I set CO4 to 0% Consolidation to Parent TOT_CO starting in 2025M3
    • You can see it rolls up in 2025M1 & 2025M2 but the full YTD amount does not roll up starting in 2025M3 (first screen shot in green)
    • This is also dependent upon your scenario settings of YTD vs Periodic for the "Consolidation View" scenario property  
    • If your scenario is set up with YTD Consolidation View then in the first month when you set the % to 0, it will reverse the full YTD amount for that entity to its parents (green below)
    • If your scenario is set up with a Consolidation View of periodic, then it will behave like the second screen shot (black below) below


       

     

    But it does work.  As to how just depends on scenario Consolidation View setting.

  • Ghizlane's avatar
    Ghizlane
    New Contributor II
    2 days ago

    Hi T_Kress and thanks you for the quick answer!

    We tested this in a YTD view, since our Actual scenario consolidates in YTD.

    We attempted setting consolidation to 0%, ownership to 0%, and also tried the standard ownership types, but none of these changes had any effect, the entity continues to consolidate.

    The only approach that seems to stop the consolidation is switching the ownership type to Custom1 and adding logic in the API_Consolidate rule. That said, we find it unusual that setting the percentage to 0% does not produce the expected behavior.

    Do you have any thoughts on what might explain this?

    Thank you

    • rhankey's avatar
      rhankey
      Contributor III
      2 days ago

      All you should need to do is set PercentConsolidation=0, for the Parent/Child relationship in question.  PercentConsolidation stops the out of box functionality from consolidating (aggregating) the child entity to the parent.  We use this method routinely to "move" entities over time from one parent to another. 

      PercentOwnership and OwnershipType requires custom logic to do anything.  If you are also having to mess with one or both of these to get your desired outcome, you will need to look at your specific consolidation logic to figure out what is going on.

      • Ghizlane's avatar
        Ghizlane
        New Contributor II
        1 day ago

        Hi,
        We found out that in the rule, this api.ExecuteDefaultShare(100) call 
        was overriding the logic we were looking to achieve.

        Thanks for the support !

    • T_Kress's avatar
      T_Kress
      Icon for OneStream Employee rankOneStream Employee
      2 days ago

      After you change PercentConsolidation to 0, you will need to run a Force Consolidate to see changes.