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

Hierarchy not in same order as in R3

I have an account hierarchy in BW that doesn't match exactly how the hierarchy appears in R3. Even though all the nodes are there, the order of the nodes, particularly the leaf level (account numbers, in this example) aren't in the same order as in R3 within a given higher level node. Is this normal or indicative of a problem of some type?

Example:

R3

NODEA

ACCOUNT 1

ACCOUNT 2

BW

NODEA

ACCOUNT 2

ACCONT 1

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 10, 2007 at 05:05 PM

    Its normal. Issue would be if you see the lowest nodes are assigned to someother higher node than what it needs to be, if they fall under the same node as assigned... nothing to worry about.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Based on when the user created/delted/changed/shifted the nodes/leaves in R/3..an unique serial id is generated and amaintained in R/3 for each NODE/leave...and stored in the table and that's what is read by the extractor.

      If its a reproting issue you can controle this using sorting orders in the analyzer!

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.