About bram.kurstjens

Hi Asslam,   There are a few options and which one you chose kind of depends on how you want to treat the dummy items. If the dummy items should be treated mostly the same as normal items, then I would suggest to add the dummy items to the production list, so that you do not have to duplicate a lot of modules. I would make sure there is a clear indicator in the production list, which tells you whether it is a manual dummy or an automatic load.    I think my approach would be to copy the data from the dummy item to the real item. You can then decide to delete the dummy item and the user would see their input values on the real item (instead of building line items that combine dummy & real item data). Changing the dummy code to the real item would probably create a similar problem that the data you loaded on the real item will need to be transfered and would require an administrator to do the exercize, while I would prefer the user to do it. The following steps I would take:   - Create a mapping module where the user can choose which dummy item should be mapped to a real code. (You would probably want to filter this module to only show dummy items to avoid user mistakes). - Create a line item per input module that displays the mapping via a lookup - Create a view per input module that shows the mapping line item and the input line items and filter it to only show mapped items. You might also want to add a check here that the real item should not have any values. - Create import per input module that imports the input data from the dummy to the real item - Delete the mapped dummy items     Hope this helps,   Bram Kurstjens   ... View more

I would also put them in seperate line items, Month_ARPU, Quarter_ARPU, Year_ARPU with summary set to None and calendar set to month, quarter, year respectively and then 1 final one on month with summary set to formula: - IF Month_ARPU > 0 THEN Month_ARPU ELSE IF Quarter_ARPU > 0 THEN Quarter_ARPU ELSE Year_ARPU       ... View more

Hi René Im not completely sure where the circular reference comes from? It looks like your manual end result formula is: Baseline of Manual + YoY - YoY[LOOKUP: Year] How is the baseline of manual calculated? Perhaps it would be good to share a screenshot of the blueprint of your module + the formula that you try to insert that gives a circular reference for us to understand your issue better. KR, Bram Kurstjens ... View more

Hi Chris, The idea is that you can map your hierarchy to a time dimension and then use the functions available for the time hierarchy (previous()) and then map it back to your original hierarchy. This should be possible in any situation I think, but in your case it is probably easier to discuss this directly. I'll send a PM. ... View more

Hi Mark, The reason for it not being "best practice" is that the items in a list are likely to change over time. You do not want your formulas to stop working because a list was updated. However your Top Level item of a list is not likely to change and thus it is an exception to the best practice rule that Select is not smart to use. I would in your case advise to use the SELECT method. ... View more

Ok, I've built it anyway to make sure everyone is helped out on this topic. Again would not say that this is best practice:   First you need to create a time range just for this purpose. I've put it to 1 period (1 year) in the year 2030, any year will do. This will allow your calculation module (mentioned later) to have 365 intersects if you put it to 'days' or 12 if you put it to 'months'. If you need something in between or more then of course you can extend the period. The first module you need is one that creates all the intersects you need, in my case between product and month, I called it the hierarchy combination module: Import this filtered view into your combined hierarchy list, in my case called "Product - Month',. with Order as property.  Now create your "Final Module" the one that takes user input, in my case directly, of course you can apply formulas there as well. Pay special attention to the 'Date mapping' field, that will be useful later: DATE(2030, 1, 1) + 'Product - Month'.Order - 1 . Minus 1 so that we start at the first date, 2030-1-1 was the first date of my time range. If you have set the period to months, then this field should not be date, but time period month and the formula should be PERIOD(DATE(2030, 1, 1))  + 'Product - Month'.Order - 1. In your case the formulas for Good Book and Good Book closing receivables should still be empty. The next step is to create a calculation module that uses the time range. You could for size reasons only include the first and the last item (with the last item doing all the "SUM: Final Module.Date Mapping" that happen above), but to keep it as simple as possible, I chose to create every line item seperately. Finally add the two formula's in the final module that reference to Good Book and Good Book after closing receivables with a lookup on the Date Mapping.     I hope that clarifies it.   KR,   Bram Kurstjens ... View more

I would not suggest creating a combined hierarchy with time in it, I would rather combine the other lists if possible, but if you must then this might be a solution:   1 Create a time subset that includes the maximum amount of periods that you would need for any combination. 2 Make sure that your combined hierarchy has some logic to know the order and what is the start (e.g. a property that starts at 0 and adds 1 for each new list item 3 Map your hierarchy to the time subset (e.g. startdate + property rank) 4 Create a module that has the time subset with your previous formulas 5 Link the new module with the combined hierarchy module with the link you created in step 3.     If you are interested in this solution, but cannot seem to get it done, please let me know, then I'll build an example.     ... View more

Vignesh has the right answer, but just to add, this is not Anaplan specific. Anaplan is making use of the 'Tree structure' terminology to make a visual representation of the data hierarchy, explained on wikipedia here: https://en.wikipedia.org/wiki/Tree_structure The general idea is that the highest level (e.g. All Products) is the root of the tree, then each level below it are the tree branches and the last level are the tree leaves. With this representation in mind, it is easier to understand that you can go from a certain leaf to its branch to the next branch all the way to the root and that from the root you are able to reach all leaves. PS. It is a bit unfortunate that the picture is usually shown as vignesh did where the root is at the top and the leaves are at the bottom, leaving the tree upside down. ... View more

Indeed, this has been asked before: https://community.anaplan.com/t5/Anaplan-Platform-Discussions/How-do-I-sum-across-dimensions-other-than-time/m-p/48208#M6344 Please reply to the answers posted there, people are putting in effort to help you out, it is only decent to let them know whether they did. KR, Bram Kurstjens ... View more

Hi Madhu,   I'd suggest you would load the lowest level list first (without parents) with the complete file and load the file to a module containing the lowest level list.  From that module you can then create a view for each higher hierarchy (with isfirstoccurrence). Then create 1 action per hierarchy to import into the list, starting with the highest hierarchy. The last action you need to create is to update update your lowest hierarchy again, as the parents need to be assigned.   Then you would need a process that does all the actions: 1) Import file into lowest hierarchy list 2) Import file into module 3) Import from module into highest hierarchy list 4 - 9) import from module to other hierarchies 10) Import from module to lowest hierarchy list (updating the parents)   ... View more

Hi Iosman,   Unfortunately I have a very complicated answer for your very simple question, but it does work. It will require a few more line items though! If I understand correctly, you want to see the percentage of each product relative to its parent. As in the following screenshot:              Sidenote: I have a rather standard way to determine which level of the hierarchy the cell is refering to. I use this for filtering tables where I want to show a certain level, while I want to use synchronize selection on the dashboard (selecting levels in a view, disables the synchronize selection function), but it can also be useful for these kinds of formulas. In order for this to work, you need to know how many levels the list will have and it will require maintenance if you add another level.       Here are the steps to create this result: Create a line item "Ratio", set the value to 1 and set the summary to 'MIN' Create a line item "Lvl 2", set the value to 2 set the dimension to Product Group and set the summary to 'Ratio' with parameters: "Ratio / Ratio" Create a line item "lvl 3", set the value to 3 and set the summary to 'Ratio' with parameters: "Lvl 2 / Ratio" You now have a line item that shows a 1 when it is on total products, a 2 when it is on a product group and a 3 when it is on a product: Add a Product Group line item with format Product Group which refers to the parent of product PARENT(ITEM(Product)) Add a "Sales product group" line item which does a look up on Sales using the Product Group line item: Sales[LOOKUP: Product group] Add the last line item "Sales %" with as summary "FORMULA":  IF 'Lvl 3' = 1 THEN 1 ELSE IF 'Lvl 3' = 2 THEN Sales / Sales[SELECT: Product Group.All Products] ELSE Sales / Sales product group   The formula checks the level and determines its calculation based on that level so, If 'lvl 3' = 1 that means the current product dimension is on Total Products, thus 100%. If 'lvl 3' = 2 that means the current product dimension is on Product Group, thus Sales devided by the total sales. If 'lvl 3' = 3 that means the current product dimension is on Product, thus Sales devided by the sales of the relative product group.   Hope this is not too complicated!     KR,   Bram Kurstjens ... View more

Hi Taylor,   Lookup will only work if the line item you are using (Fiscal Week End Date) has the same list dimension as the module you are refering to (Calendar). So in this case your calendar module needs to be build with the same list as the format of your ' Fiscal Week End Date' line item. Just a note; if the calendar module is on the Anaplan time dimension Day then the format of 'Fiscal Week End Date' should be date.   Hopefully a bit better to understand, let's say the Calendar module is using the FDays list, where you have populated all the days you want. Then the 'Fiscal Week End Date' needs to have the format FDays.    If this currently is not the case, then you would probably need an additional line item, translating the 'Fiscal Week End Date' line item to the FDays list.  ... View more