Skip to Content
author's profile photo Former Member
Former Member

Defaulting Hierarchies

We are using a hierarchy on 0cust_sales. Not all our customers are assigned to a hierarchy. This causes problems in the report when they do sorts. We were told that we could not do anything about this in the query, but that we could in the load of the hierarchy into BW by defaulting those customers that are unassigned to the root of the hierarchy.

Sounds good. But now they are looking to me to do this and I can't find where logic like this would be placed. Can any one point me in the right direction?

Thanks,

Chris

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Nov 24, 2005 at 05:18 AM

    Hi Chris,

    I quess it was a talk about unchecking flag 'Supress unassigned noder' (Hierarchy maintenance, menu option Goto/Hierarchy attributes (or the button):

    http://help.sap.com/saphelp_sem350bw/helpdata/en/7d/ae45e9e9d4ba478f663bd12ee0fae0/content.htm

    Best regards,

    Eugene

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2005 at 04:04 PM

    Eugene,

    Thanks for your reply. It was very helpful. I don't think the 'Suppress Unassign Node' option that you mentioned will meet are exact needs because it filters out those that don't have a hierarchy. But in the link you provided, I found the following: 'When loading hierarchies, the hierarchy attributes are transferred from the old active version of the hierarchy. When loading via the PSA, they can be overridden by transfer rules.' I'm not loading the hierarchy through the PSA table so maybe that's why I wasn't able to see a transfer rule where I could over ride them.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 30, 2005 at 05:59 AM

    Hi Chris,

    I’m not agree with your statement “it filters out those [nodes] that don't have a hierarchy”.

    A little clarification. The default structure of a hierarchy (with unchecked 'Suppress Unassign Node' option) is the following:

    ROOT

    --LEVEL

    -


    LEAF

    ….

    ---UNASSIGNED

    A hierarchy is built for a characteristic, not for separate char values. In your case it is built for 0cust_sales. You may or may not include some particular 0cust_sales values into hierarchy. If in the TRANSACTION DATA the system encounters value included into the hierarchy structure, this value will be shown in reporting as appropriate leaf/node in the hierarchy. If encountered value was not set in the hierarchy structure, it’ll go to unassigned node.

    Checking 'Suppress Unassign Node' option will wipe out this node in the report. So, 0cust_sales values in transaction data that are not set in the hierarchy structure will be omitted.

    Here we need to return to your requirements. What exactly do you want to get, ‘cause it’s not very clear?

    Best regards,

    Eugene

    PS. Loading a hierarchy through PSA, I guess, has little to do with your question. That’s why I didn’t go into details about it.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Chris,

      Ok, now it's more clear.

      Just an idea: create a variable with replacement path on your customer IO. Set 'Replace variable with' = Query result. As a query name choose the query that you already have (with hierarchy).

      Create another query, put into rows customer IO, do not activate hierarchy for it, just restrict by the var you created.

      So, first query will give you a subset which you can use in the second query.

      Try it and let us know if it works.

      Best regards,

      Eugene

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.