Product costing in Anaplan

Frequent Contributor

Re: Product costing in Anaplan

Hi Einas,

Thanks a lot for your message and to clarify - this is a pre-build app from the app-hub that I have downloaded and are currently doing some testing on.

In this particular case, the module is used for rolling up the entire component requirement for a semi-finished good, that is, summarizing a specific component over all BOM levels (maximum of 9 in the model) for the specific semi-finished good.

I agree with you regarding the issue with having the two dimensions, but I don't currently see another way of doing it, since the module itself is very useful and I need to keep the functionality of it, but if possible, doing it in a way that doesn't use up the same size.

You can find the app here: https://community.anaplan.com/t5/supply-chain/Bill-of-Materials-Costing/ba-p/28128

Any thought?

 

Highlighted
Valued Contributor

Re: Product costing in Anaplan

Hi @fredrickstraube 

Unfortunately, I have been having issues accessing my workspace for about 4 days now (going crazy but support is helping me). So I can't really download the model and look at it but I promise I will do once I get my access issue fixed.

Here is how I saw others go around this issue:
Create a concatenated Key by combining the Product and SKU, this way you only have intersections you need. Honestly, I'm not a big fan of this solution for many reasons chief among them is the fact you will be concatenating 2 texts and you know how we feel about text 🙂 

 

The way I did it for my issue with the transactions (entities and GL accounts) is to create a list that I populate using an action where it has the hierarchy for the items I need
for example 
All Products 
----- Product 1
----------------SKU 1
----------------SKU 7

----- Product 2
----------------SKU 8
----------------SKU 10

 

The idea is that you build that hierarchy dynamically and then use it to dimensionalize the module instead of using the 2 lists Product and SKU, less size, less sparsity.

 

It worked in my case because we had a daily import from the transactional system so a process was running every day and I was able to add my action to it. The potential drawback is how often do you need to adjust this list, and is it feasible from a user perspective to ask them to run an action every time you create a new product??


For completeness... since I assume the model will have other modules dimensionalized by the Product or SKU list and you will probably need to access data from these modules, then this newly created list has to be created as an alternate list. That's a topic for a different time if you are interested. 🙂
 

Einas
"Give a Man a Fish, and You Feed Him for a Day. Teach a Man To Fish, and You Feed Him for a Lifetime"
Highlighted
Frequent Contributor

Re: Product costing in Anaplan

Hi Einas,

Thanks for your input, but the problem with doing it that way has to do with the hierarchies in Anaplan. In the model, a specific product can have up to 9 BOM levels (L1 -> L9).

Anteckning 2020-05-06 134609.png

A specific component, at a specific level, references an item in the list of all SKUs (list property). So for example, a product can have two Sub-assemblies (SA) in the L1 level, which then consists of raw materials (RM) in the L2 level. However, it could also be the case like below:

Products AParentComponent 1Component 2...
L1Product ASA_1RM_1 
L2SA_1SA_2RM_2 
L3SA_2SA_3RM_2 
L4SA_3SA_4RM1 
L5SA_4RM_3RM_4 
L6--- 
L7--- 
L8--- 
L9--- 

As you can see, it can be the case that a specific level is both SA and RM, as well as a specific RM (or SA) can be used on multiple levels. And of course, it can be more than just two components.

However, it can, of course, also be the case like below:

Products AParentComponent 1Component 2...
L1Product ASA_1RM_1 
L2SA_1SA_2RM_2 
L3SA_2SA_3RM_2 
L4SA_3SA_4RM1 
L5SA_4SA_5RM_3 
L6SA_5SA_6RM_4 
L7SA_6SA_7RM_5 
L8SA_7SA_8RM_6 
L9SA_8RM_7RM_8 

That is, different products goes down to different levels, some might stop at L1 and some could go all the way down to L9 (or even lower). This means that if I put L9 as the dimension of my module, only capture the information for the products that go down to L9, and the same goes for the other levels. I would somehow need the dimension of the module to capture ALL of the different levels, almost like I had a formula that applied to all the levels within the hierarchy. 

Does this make sense?

Thanks!