Skip to Content
author's profile photo
Former Member

A Problem with hierarchy

Hi all,

I've a problem with hierarchie's leaves.

The client wants to see a leave under two differents nodes of the hierarchy.Indeed this leave was registred under Node A until 1999 and then under Node B (2000 to 2005).

In the report, he wants to see the sales of this leave under Node A and simultaneously the sales under Node B, maintening the hierarchy actived on the rows. The problem is that in the report the records of the sales are doubled and it not seems possible to see the "temporal split".

Instead it works fine if i do not use the hierarchy but two different infobjects for node and for leaves, but in this case i don't have the hierarchy in the report.

Can someone help me?

Thank U

Alex B

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • author's profile photo
    Former Member
    Sep 13, 2005 at 10:17 AM

    Hi,

    Have you seen the concept 'Time dependent hierarchy

    structure'.

    Take a look on the site:

    http://help.sap.com/saphelp_bw32/helpdata/en/80/1a6702e07211d2acb80000e829fbfe/frameset.htm

    With rgds,

    Anil Kumar Sharma .P

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Sep 13, 2005 at 10:43 AM

    Thank u,

    but if i set my hierarchy time dependent, for exemple with a key date, i can see or the sales of that leave under Node A or the sales of that leave under Node B, but not together in the report.

    Alex B

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 22, 2005 at 12:47 PM

    Hi,

    You can try to play with link nodes:

    http://help.sap.com/saphelp_nw04/helpdata/en/b3/fa3d3806136268e10000009b38f8cf/content.htm

    Best regards,

    Eugene

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      To show the report as your reqirement , Do not take 'teams' as child node to 'Location' .Take them as two independent characterstics,i.e, take both of them as characterstics in Infocube. At the time of data loading ,the R/3 system has to findout the team for the location of the record.This will be done by customer exit.

      With rgds,

      Anil Kumar Sharma .P

  • author's profile photo
    Former Member
    Sep 28, 2005 at 09:55 AM

    Hi,

    we have resolved (by using the suggest of Anil Kumar Sharma) the problem by writing one Abap program and One Abap routine on the update rules.

    The Abap program read the H_Table of 0orgunit and organizes the records in another table (ZHUO) with this order:Mand - Code Sales Org - Datefrom - DateTo - Livel1 - Livel2 -..- Livel 7. Then we create Seven infoobjects and wrote a start routine thats loop at datapakage selects the record from the table created and put the codes of the livel 1 into the Infoobject 1, level 2 into the infoobject 2..etc etc. In this way i utilize an internal hierarchy but i have the complete history of the hierarchy. I dont think it is possible by using external hierarchies.

    So in the report i see each node or subnote classified by level and i see the presences/absences (KF), done under node A or under node B, by viewing also the temporall split if i drill down 0calmonth.

    I hope it is usefull

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Alessandro, Anil,

      It was not the answer I was hoping for, but thank you for your suggestions. We also had thought of a similar approach but hoped that time dependent hierarchies could provide a simpler solution.

      I am amazed this is not possible with time dependend hierarchies, I've checked with a lot of consultants and everybody seems to think it is possible (just that nobody ever seems to have used it with a client).

      Is there anybody here from SAP who could tell me if this functionality exists or not.

  • author's profile photo
    Former Member
    Sep 30, 2005 at 09:09 AM

    Hi Rob,

    I think that the problem is not the time dependence of the hierarchy, but the fact that the hierarchy is external, in that case in the dimension table you have only Dim - Sid and then in the Htable Sid - Node Id.

    In other words you don't have the information about leaf (node A, Node B). Instead if you put entire hierarchy on the dimension table (internal hierarchy) you have this information Dim - Sid (node a) - Sid (node b) etc etc. I hope it's clear, if you want i'll send u by mail a screen paint of an internal hierarchy on the report.

    Regards,

    Alex B

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Alessandro,

      thank you. I do understand the difference between the internal and the external hierarchy. (We had both scenarios in our blueprint) The reason we went with the external was because the client maintains this in his R/3 Org. Structure. Now having to flatten that into the cube seems silly to me. The data is available in the hierarchy (i can see the validity dates) but apparently cannot be used for display.

      I'm just flustered, I always thought this was the whole point. And all people I've checked with had the same impression...