Question:
Hi All,
In BW it is possible to create more than 1 hierarchy against an InfoObject. The two hierarchies can contain some nodes and leaves that are common to both and some that are discrete.
Is it possible to do the same in SEM-BCS or will this affect the consolidation processes?
Reason for asking is when we try to create a second hierarchy in BCS, once you enter a node into one hierarchy that is the same node that already used by the other hierarchy, the leaves between the two seem to self-synchronize (i.e. remove leaves from one and they disappear from the other). Is there any way around this?
Thanks and regards
SB
Answer:
Sounds like a bug to me because this is not the way EC-CS consolidation works.
Then again, you really should avoid using the same technical name for nodes in parallel hierarchies. If you ever need to change only one of your hierarchies without touching the rest you will be much better off having separate node names.
Hi All,
In BW it is possible to create more than 1 hierarchy against an InfoObject. The two hierarchies can contain some nodes and leaves that are common to both and some that are discrete.
Is it possible to do the same in SEM-BCS or will this affect the consolidation processes?
Reason for asking is when we try to create a second hierarchy in BCS, once you enter a node into one hierarchy that is the same node that already used by the other hierarchy, the leaves between the two seem to self-synchronize (i.e. remove leaves from one and they disappear from the other). Is there any way around this?
Thanks and regards
SB
Answer:
Hello:
It is possible to use the same node name in 2 hierarchies for 2 nodes.
But, the subtree below the 2 nodes are same then. This is the way from 31B to 35, perhaps will also keep the same in 40 ( it is being developed now )
While as you said, the leaves is removed, it should be a bug.
You could raise an OSS message for it.
Best regards,
Eric
Answer:
We created several hierarchies in our environment. The trick is to right click and select the create node option when creating the hierarchy instead of doing a drag and drop.
Try to follow this procedure to create your hierarchies, Kirk Anderson the BCS Platinum consultant in charge of the BCS ramp-up program is aware of this situation and hopefull SAP is working on fixing the drag and drop situation.
Carlos.