on 2023 Nov 03 8:10 PM
Using the new Hierarchy with Directory functionality I have been able to load multiple hierarchies for different node types to display, however the order of the nodes appears to be tied to the NODEID instead of using the ChildID/NextID fields that are present in many other SAP hierarchies. Can anyone confirm if this is true?
The help document (Creating a Hierarchy with Directory | SAP Help Portal) shows an example of a heirarchy being pulled from S/4 that includes the ChildID/NextID fields. I have included them in my tests but they do not seem to have an impact on the final display of the hierarchy.
I will admit it took me a bit to get all the steps from the help working so it is possible I missed something that is preventing the display from using those fields so I thought I would ask what others are experiencing.
Thanks.
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a very poorly documented functionality. We have been trying to get it to work since its release. We have a support mesasge open as well. I saw this error and I have solved this error in the comment (not the error on the original post) by adding and association to the Hierarchy Dimension. .
Define the association like below from GL Hierarchy Node to G/L Account Hierarchy Directory.
Toni,
I agree with Abhijit and I think you need to add an association to the directory object. This is step 3 of Prepare the Hierarchy Entity section.
Hope that helps.
User | Count |
---|---|
58 | |
10 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.