Forum Stats

  • 3,853,717 Users
  • 2,264,259 Discussions
  • 7,905,435 Comments

Discussions

Missing an account in aggregation

JanGLi
JanGLi Member Posts: 650 Bronze Badge
edited Oct 5, 2017 8:06AM in Financial Consolidation

Hi,


We want to exclude an account member in aggregation in HFM.

E.g.

pastedImage_2.png

instead of 400 we want 300.

In hyperion planning we simply used to just change our member property and it won't aggregate. But in HFM we couldn't find anything like this for HFM. Is this possible to achieve this by changing member property? or by any other way?

Regards

Tagged:
USER1211

Best Answer

  • CBarbieri
    CBarbieri Member Posts: 1,011 Gold Trophy
    edited Oct 4, 2017 12:55PM Answer ✓

    "Aggregation" and "Consolidation" mean two different things in HFM and are controlled in different ways:

    1) Aggregation is HFM's built-in summation of base members in the accounts, customs, view, and period dimensions. This is based on the metadata attributes. For accounts in particular, the account type determines whether data in A3 should sum to Acc Parent. As Eric suggested, the type "GROUP LABEL" neither stores data, nor aggregates to it's parent. All other types aggregate to the parent account member, though whether they add or subtract is based on the type.

    2) Consolidation is the term which describes whether data in this account should be included in Sub Consolidate (or default consolidation logic). An account that does not consolidate would have data in it up through [Parent Total] in the value dimension, in a base entity, but would not be passed along to [Proportion] or [Elimination]. Unchecking "IsConsolidated" as Alex_UK suggests, would apply this behavior,

    Depending on your exact requirements there may be other ways to handle this. We could leverage the "Enable Custom X Aggregation" for account A3 would prevent the custom dimension members associated with this account from aggregating to parent customs. The data in the account could still be consolidated otherwise.

    From a rules perspective, if you don't want the amount passed up to the parent you can also omit it from the custom consolidation routine, or redirect the amount to a different account-custom intersection.

    You can also erase the amount by using Sub Calculate in conjunction with the specific POV where you don't want it. Use HS.Clear for this.

    If you can provide more details as to how this should behave across multiple dimensions, I'm sure we can give you a more clear answer.

    - Chris

Answers

  • Alex_UK
    Alex_UK Member Posts: 52 Red Ribbon
    edited Oct 4, 2017 8:56AM

    In terms of consolidation, you can change the account (A3) metadata account property 'IsConsolidated':

    pastedImage_0.png

    But for account aggregation, you would need an account type that is not aggregated to the parent level.

    See page 84 of the HFM admin guide (or search for 'Account type Behaviour'). You might need a dynamic account or something.

    You could also script it in the rules.

    JanGLi
  • ericerikson
    ericerikson Member Posts: 608 Bronze Trophy
    edited Oct 4, 2017 9:20AM

    Hi. You could change the account type to grouplabel but then it won’t hold data. Maybe add a new parent solely for the account and make the new parent GL. Or move the account out of the hierarchy.

    Eric

    USER1211JanGLi
  • CBarbieri
    CBarbieri Member Posts: 1,011 Gold Trophy
    edited Oct 4, 2017 12:55PM Answer ✓

    "Aggregation" and "Consolidation" mean two different things in HFM and are controlled in different ways:

    1) Aggregation is HFM's built-in summation of base members in the accounts, customs, view, and period dimensions. This is based on the metadata attributes. For accounts in particular, the account type determines whether data in A3 should sum to Acc Parent. As Eric suggested, the type "GROUP LABEL" neither stores data, nor aggregates to it's parent. All other types aggregate to the parent account member, though whether they add or subtract is based on the type.

    2) Consolidation is the term which describes whether data in this account should be included in Sub Consolidate (or default consolidation logic). An account that does not consolidate would have data in it up through [Parent Total] in the value dimension, in a base entity, but would not be passed along to [Proportion] or [Elimination]. Unchecking "IsConsolidated" as Alex_UK suggests, would apply this behavior,

    Depending on your exact requirements there may be other ways to handle this. We could leverage the "Enable Custom X Aggregation" for account A3 would prevent the custom dimension members associated with this account from aggregating to parent customs. The data in the account could still be consolidated otherwise.

    From a rules perspective, if you don't want the amount passed up to the parent you can also omit it from the custom consolidation routine, or redirect the amount to a different account-custom intersection.

    You can also erase the amount by using Sub Calculate in conjunction with the specific POV where you don't want it. Use HS.Clear for this.

    If you can provide more details as to how this should behave across multiple dimensions, I'm sure we can give you a more clear answer.

    - Chris

  • JanGLi
    JanGLi Member Posts: 650 Bronze Badge
    edited Oct 5, 2017 8:05AM

    Thanks for such elaborate answer @CBarbieri

    We thought of this but couldn't do it since we want aggregation on other members of all custom dimensions.

    We are thinking of moving out it from hierarchy

    or

    might use rule.... (Acc Parent - A3).


    Regards

This discussion has been closed.