Level 2 Model building - Sprint 1: flat lists vs system modules

SChua

Hi everyone,

 

I'm confused about some concepts related to data hubs:

-Why do we build both flat lists and system modules in the data hub? Is Anaplan not able to import from lists?

-Why did we create a hierarchical list in the data hub when we were told it's best practice not to?

einas.ibrahim

Hello @SChua 

 

I'm happy to answer your first 2 questions. They are actually good questions and deserve an explanation.

Regarding your third question, It is against the rule to post exam questions or solicit direct answers to exam questions.

I recommend you delete that part of your post and I'll answer the other 2 points on the modified post

SChua

Hi @einas.ibrahim ,

 

Thanks for the reply; I deleted the image but would still like to know the logic behind it - why would it cause an error to load product details in before the product flat list?

 

einas.ibrahim

Hello @SChua 

 

Let's address your questions one at a time:

 

1. Why do we build both flat lists and system modules in the data hub? Is Anaplan not able to import from lists?
   System Modules have many benefits such as improving performance or organize data (PLANS). One of which is to build Lists hierarchies.
   You want to store your lists in a flat manner in the Data Hub but in a way that will allow the spokes models to build or refresh their hierarchical list.
   You may ask why don't we store the lists in the right hierarchy in the data hub, to begin with? and an answer would be:
   1. Hierarchical lists take more space than flat lists. We don't use hierarchical lists in the data hub so we don't need to store them there either.
   2. If we store the hierarchical lists in the data hub and then want to build or refresh the lists in the spokes model, we won't have an option but to import from List to List (data hub - spokes). While Anaplan is technically capable of doing so, it is much slower and resource-intensive than importing from a module (saved view) 

System modules are a way to store the list hierarchical information in a flat manner.
Consider the System Module below Sys06 Country Details in the Data Hub

It helps us recognize the parent -Region - for every country in a flat manner. We can use this module (saved view) to create the Hierarchical List Country in the the spoke model.

 

 

2. Why did we create a hierarchical list in the data hub when we were told it's best practice not to?

I believe the training asked us to build these "try it" hierarchies just to test building a hierarchical list from a system module. You are supposed to delete them or ignore them.

 

3. Why the loading order matter?

1. Generally speaking, if you are loading 2 lists, then you can't load the child (G2 Country for example) before the parent (G1 region) because we need to reference the parent of the country when we are loading the list.
2. If you are loading a module dimensioned by a particular list, then you need to ensure that list exists first.

SChua

Thanks a bunch; This is really helpful!

einas.ibrahim

@SChua 

I'm glad you found it helpful. If you have other questions in the future mention my name in your post @einas.ibrahim and I should get notified to look at your question.

 

Good Luck

Jamez

@einas.ibrahim Thank you so much for the explanation but I have one question relative to the this point.

You told us that it´s no necessary to use hierarchical lists in the data hub but in our Anaplan Level 1&2 we introduce hierarchical list on the Data Hub as activity.

Maybe I am little be confused, could you help me?

Jamez

In fact we use hierarchal list in both models Data Hub and Spokes but we ony use flat list on the firs one

Jamez

Jamez

einas.ibrahim

@Jamez

We use flat lists in the Data hub and hierarchy list in spokes.