Warning 39092: Column is first under presentation hierarchy but not a grand total level — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Warning 39092: Column is first under presentation hierarchy but not a grand total level

Received Response
22
Views
3
Comments
Mark.Thompson
Mark.Thompson Rank 6 - Analytics Lead

In an RPD that started its life in 11g and has been migrated to 12c, I now see a consistency check warning in 12c: "[39092] Presentation level "Budgets"."Time"."Year" is first under presentation hierarchy, but logical level it is associated with is not grand total level."

Year has always been the topmost level of this Time hierarchy. It has never had a topmost parent level that represents a total of all values at the Year level.

I want to clear this consistency check warning, and I know I need to tick a "Grand Total Level" checkbox to do so.

Do I need to add a true Grand Total level as a parent of Year, and tick the checkbox on that level?  I have no business need for such a level, so I would be doing so only for the purpose of clearing this warning.  (Side note: This RPD started its life in EBS, so there are about 300 of these warnings. Adding a true Grand Total level for each of them will be a pain.)

Or can I simply tick that checkbox on the existing Year level? That feels wrong, because Year is not a true grand total level.  But I can't find any documentation that describes what the Grand Total level checkbox does behind the scenes, the real, true reason why it is important, so I can't determine whether ticking the Grand Total checkbox for Year is a good thing or a bad thing.

Can someone share the purpose behind the Grand Total level checkbox at a deeper level than what is found in the documentation?  And then also answer my question above: Do I have to add a true Grand Total level?

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner
    Mark.Thompson wrote:Do I need to add a true Grand Total level as a parent of Year, and tick the checkbox on that level?

    tl;dr: If you want to get rid of the warning? Yes. You must configure the hierarchy with a proper grand total level i.e. a parent of "Year" and "Grand Total" checked.

    Mark.Thompson wrote:Or can I simply tick that checkbox on the existing Year level? That feels wrong, because Year is not a true grand total level.

    Of course  not. Just like "Continent" isn't the grant total of a geo hierarchy ;-)

    Mark.Thompson wrote:Can someone share the purpose behind the Grand Total level checkbox at a deeper level than what is found in the documentation? And then also answer my question above: Do I have to add a true Grand Total level?

    The purpose is to have a Grand Total to which all children get aggregated to. All years, all continents, all product roll-ups.

    Again: Yes, you have to add the grand total level if you want to get rid of the warning.

    Note: "WARNING". It's not an error. It's a warning.

  • Mark.Thompson
    Mark.Thompson Rank 6 - Analytics Lead

    Thank you, Christian.  Yeah, I know it's just a warning, but I'm sort of picky about having a clean consistency check.

    Allow me to restate part of my question: Why was the Grand Total checkbox unimportant in 11g, but then became important in 12c?  Did something change between 11g and 12c so that perhaps something that worked just fine in 11g now fails in 12c without that checkbox?  Or is it just a new warning in the 12c consistency check that wasn't there in 11g?

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    With every version thy add more checks and controls. Like previously it was ok to have a business model where you mixed logical dimensions without hierarchy with properly configured logical dimensions and that's gone for example and a hard error now.

    Backstory: When they started making cloud versions they started becoming more and more draconian for the very simple reason that cloud by definition means black-boxing of many things. So they had to find ways to ensure that there are as few things as possible which can potentially go wrong when shoving an RPD into the cloud.