Parent child list to ragged hierarchy

jjwikselaar
Contributor

Parent child list to ragged hierarchy

Hi, I am looking for a way to automatically create a ragged hierarchy for all possible combinations. The input is a simple file with only the parent - child combinations.

I've attached a screenshot of the parent child combination and how the ragged hierarchy should look like.

 

I think it is possible to do this when I combine the parent child list and ragged hierarchy list in one module and then create each level step by step, but I would like to avoid combining the 2 dimensions as the list will be extremely large!

 

Any ideas / suggestions?

Thanks,

JJ

4 REPLIES 4
rob_marshall
Moderator

Re: Parent child list to ragged hierarchy

@jjwikselaar 

 

Have you looked at this training, it might be able to help:

 

Hub Model Hierarchy Management (305)

https://community.anaplan.com/t5/On-Demand-Courses/Hub-Model-Hierarchy-Management-305/ta-p/202

 

 

Rob

jjwikselaar
Contributor

Re: Parent child list to ragged hierarchy

Thanks for the link @rob_marshall , but I should have been clearer in my description.

In my case it will be a many to many relations. It is for a bill of material setup.

 

For example:

F1 (Finished good) need components: C1, C2

F2 (Finished good) need component: C1

C1 component need component: C3

So in this case C1 has parents: F1 and F2

 

To create ragged hierarchy I need to find all possible combinations, which are:

F1

C1-F1

C2-F1

C3-C1-F1

F2

C1-F2

C3-C1-F2

rob_marshall
Moderator

Re: Parent child list to ragged hierarchy

@jjwikselaar 

 

Take a look at David Smith's attachment in this thread:  https://community.anaplan.com/t5/Anaplan-Platform/Bill-of-Material-Explosion-Best-Practice/m-p/82044...

 

Pack a lunch as it is long, but I am thinking it will be what you need.

 

Rob

jjwikselaar
Contributor

Re: Parent child list to ragged hierarchy

Thanks, that is very useful!
It is needed though to have the dimensions (BOM and children) combined in one module which might result in a very big model.... but I guess we need to accept that.
Will try to set it up like this to see what happens!