Forum Stats

  • 3,768,301 Users
  • 2,252,772 Discussions
  • 7,874,520 Comments

Discussions

AGG parent member and it's descendants of a dimension

User_BP7C5
User_BP7C5 Member Posts: 29 Green Ribbon
edited Sep 3, 2020 3:44PM in Planning and Budgeting

Hi,

We used to AGG just a section of Entity with the code:

SET AGGMISSG ON;

SET UPDATECALC OFF;

SET CLEARUPDATESTATUS OFF;

Fix ( FY19, Jan, @iDesc(Income_Statement), Input, Actual )

   "Total Europe";

Endfix

Now this doesn't work and we need to do:

SET AGGMISSG ON;

SET UPDATECALC OFF;

SET CLEARUPDATESTATUS OFF;

Fix ( FY19, Jan, @iDesc(Income_Statement), Input, Actual )

   @iDesc("Total Europe");

Endfix

When did this come about.  I'm certain the first code above worked as I have done it many times in the past in Essbase and Planning.

Thanks for any insight.

Tagged:

Best Answer

  • Krishna Chukkaluru
    Krishna Chukkaluru Member Posts: 164 Silver Badge
    edited Sep 3, 2020 3:40PM Accepted Answer

    Your first script will calculate only "Total Europe" member, it will aggregate data from its children. In below example it will aggregate data from "Level1_M1" and "Level1_M2" members and any data loaded to Level0_M1 member will not be aggregated to Level1_M1 and you may not see correct aggregation in "Total Europe" member. Your 2nd script will aggregate fine as you used iDesc which will include all the members in that hierarchy. Also, while defining the member name as calculation command, if any formula is applied to the member that will be calculated.

    "Total Europe"

          >Level1_M1

              >Level0_M1

          >Level1_M2

    Please check the one which was working for you earlier if the hierarchy had only 2 levels. Just a thought.

    Regards,

    Krishna

Answers

  • Krishna Chukkaluru
    Krishna Chukkaluru Member Posts: 164 Silver Badge
    edited Sep 3, 2020 3:40PM Accepted Answer

    Your first script will calculate only "Total Europe" member, it will aggregate data from its children. In below example it will aggregate data from "Level1_M1" and "Level1_M2" members and any data loaded to Level0_M1 member will not be aggregated to Level1_M1 and you may not see correct aggregation in "Total Europe" member. Your 2nd script will aggregate fine as you used iDesc which will include all the members in that hierarchy. Also, while defining the member name as calculation command, if any formula is applied to the member that will be calculated.

    "Total Europe"

          >Level1_M1

              >Level0_M1

          >Level1_M2

    Please check the one which was working for you earlier if the hierarchy had only 2 levels. Just a thought.

    Regards,

    Krishna

  • User_BP7C5
    User_BP7C5 Member Posts: 29 Green Ribbon
    edited Sep 3, 2020 3:44PM

    yeah.  So in the past it must have only had Lev0 members below it so it worked.  Be safe and always use @iDesc I think .

    Thanks