I am just about to start a new project where the idea is to build a full product costing, with complete BOM and routing in Anaplan. I have a pretty good idead of how to do this, but it would be great to get some input from you guys before I actually start building. There is one thing which I think will be a bit more challenging, which is related to BOMs. It has to do with the fact that some raw material, let's assume steel in this case, is used in multiple products, which makes it impossible to use the build in Anaplan hierarchy, since many products can obviously have steel as a component. Then I would need to add steel multiple times (one time for each product) which wouldn't be ideal since it would mean that I would have to maintain the raw material steel in multiple places in my model (perhaps not an issue with steel, but other more complex raw material will need maintenance)
Also, another question: A final product might have a semi-finished good as a component, and I am not really sure how to incorporate that into the full BOM. What I want to achieve in the end is that you can look at "product A" and see all raw materials as well as the semi-finished goods used for that product, and then be able to click on the semi-finished good and see the raw materials and semi-finished goods for that one an so on...
Any input or suggestions are highly appreciated, thanks a lot in advance!
The best is to record first the BoM as " inversed flat", where you record for each item what it can produce:
the list is like this: First we have a material list that contains all items and then a numbered list that will have a child for each otther item it is used to produced
From there you can make your calculation (in this example quite simple). Note that the depth of the BoM isn't dynamic in our example, and I don't think you should make it (unless it changes often at your client's). Having it dynamic will make the formulas very hard to read. But you can create x level in addition to the current depth so that no changes are required in the near future.
Finally, I'd advise also having a hierarchical list with a level for each BoM level where you can aggregate the data once you have calculated it o a flat level, for presentation.
Thanks a lot for your suggestions. I have looked quite a bit at the Anaplan Bill of Material Costing App in the App hub, and I think it uses quite a nice structure and way of handling the BOM breakdown and multiple components.
My problem at the moment has to do with model size. As soon as I start to increase the number of products and components, the model size increases very quickly, and after just a few hundred products and a few thousand components, the upload crashed due to model size.
As far as I can tell, there is one module which is quite a bit larger than the other ones, see picture:
As far as I can tell, the main reason this module is so large is that it uses both the list of finished products as well as the entire SKU list.
Does anyone know a way to work around this so that I can retain the same functionality (rolling up the component requirement for each SKU) but having a smaller module, so that I can upload more products?
Sorry, I realized I wasn't very clear. 3.000.000 cells in that particular model is with a very limited amount of products and components (a few hundred I think).
My problem with your solution is that the app is very limited the way it is, and my plan was to add quite a lot of functionality to it, however, I don't want to do that if I'm only limited to a few hundred products and components, since my case requires several thousand of products/components.
Hi @fredrickstraube From the blueprint screenshot you provided, it seems like you are dimensionalizing the module by Products and SKU lists. That's what causes the module/model to blow up in size because when you think about it you are providing an intersection for each product and every SKU not to mention the versions lists.
Can you tell me what is the need to have both lists as dimensions?
I believe I had a similar issue in Finance where I have a large number of "entities" - that's your Product Lists - and even a larger number of GL accounts - that's your SKUs. An entity can be linked to one or more GL accounts but not the whole list of accounts. that's what having the 2 dimensions in the module mean.
If I understand your logic better maybe the solution I found would work for you.