Hierarchy not in same order as in R3

[Former Member]

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

[Former Member]

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.

[Former Member]

Thanks but my users want the nodes in BW to be in the same order as in R3. They maintain them in R3 and are brought into BW via an infosource. Can this be done?

[Former Member]

Nodes would be in the same order, the position of leaves might change but not the nodes ...

[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!