About LipChean_Soh

Hi,   Do see if the following works.     Your requirements are interesting in the sense that it's a combination of P&L and Balance Sheet in 1 view. I think you'll have to split the line items so that 1. Cash Movement deals with movement  2. Cash Position deals with final Balance Sheet value. 3. Cash deals with a combination of movement (only for Months) and Balance Sheet value (only for Quarter, Year)   To scale for a full Balance Sheet, you'll have to use 3 different modules using the same philosophy above.   Thanks, LipChean ... View more

Hi,   To be honest, the setup of Unique Codes should be done outside of Anaplan, since Anaplan is a client facing tool and not a database tool.   Having said that, please see if the following works. 1. Concatenate.All combines all All Entries.Code using TEXTLIST. 2. All Entries.'Count 2' counts the number of All Entries.Code in the entire list. 3. All Entries.'Unique Code 2' grabs All Entries.Code where All Entries.'Count 2' = 1   Thanks, LipChean ... View more

Hi,   There are 3 lists. 'L2 Prod#' rolls up to 'L1 Division'. These 2 lists help keep sparsity low, since each Division sells specific Products. 'Product Flat' is the list of available Products. Users can assign specific 'Product Flat' to the different 'L2 Prod#', and the name is reflected as the 'Display Name' of 'L2 Prod#' the numbered list.   'L2 Prod# Sales' module is where you enter sales for different products sold under each Division. 'Product Flat Sales' module is where the aggregation by Product happens.  Note the keyword SUM.     Thanks, LipChean ... View more

Hi,   ALM should be implemented as part of every Anaplan implementation, the benefits are obvious: 1. There'll be segregation of duties between model builders and business users. 2. Model builders can build freely in Dev without fear of a massive roll back. 3. Business users won't suffer massive roll back in the middle of a budget cycle.   Having said the above, whether a List should be a Production or Structural list comes down to whether a List member is to be added during run time/ production or added through ALM.   In most cases, it's quite clear whether a list is Production or Structural. Production List members are created in Source System or by business users during Production, whereas Structural List members are more slowly changing or fixed, and we can rely on Model Builders to add in Dev and 'Compare & Sync'.   However if you are not sure whether a list is Production or Structural, it's best to leave it as Structural first, because changing a list from Structural to Production in the future will retain the list members in your production model; however if you change a list from Production to Structural in the future, then your production model will have the same lists as your Dev model (which in most case is a small list of dummy members for testing members). As a result you'll lose data in Production model.   To answer your question, once you know a list is supposed to be Production List, you should start to plan the formula change from SELECT to LOOKUP. Yes it'll require some effort now, but it's necessary because properly implemented Data Hubs and ALM are crucial elements to achieving Connected Planning.   Thanks, LipChean ... View more

Hi,   Do see if the following works. I have scrambled the order of Start and End Date. Promo uses 'Day' as the Time dimension. Do switch off the summary of this module to save some workspace. Please make sure that Start Date of an entry is the same as the End Date of a previous entry.     Thanks, LipChean ... View more

Hi,   You can use TimeSum as shown below: A single entry in 1 time period is ok, and nothing is highlighted.   If more than a single entry is entered, then both entries are highlighted in red.     Note that the 'Check' module does not have Time as list. 'Total of All Periods' is not turned on either.   Thanks, LipChean   ... View more

Hi,   I want to mention about 1 point in advance, i.e. RANK has a cell limit as mentioned in https://help.anaplan.com/anapedia/Content/Calculation_Functions/All/RANK.html?_ga=2.1143538.25158203.1560335469-1239638901.1550667215   So if it's possible to load in the previous posting date as mentioned by @Manuela_Apostol  and @JV271090 , we should do so.   However i still want to discuss a possible solution that might be useful, if not with your particular issue, then maybe with some other issues.    .    'Transactions' is a list that rolls up to 'Materials'. 'Rank' is a list, with a property 'Previous Rank' of 'Rank' format. (Please create this in a SYSTEM modules as part of DISCO)   'Transaction Module' has the 'Posting Date', and the general idea is to rank the 'Transactions' within each 'Material'. Then the 'Rank' number is converted to 'Rank' list, so that we can then send it to another module 'Find Transaction'.   'Find Transaction' will place the relevant 'Transactions' sequentially for each 'Material'. And referring to Rank.Previous Rank, we can then find the Previous Transaction.   Back in 'Transaction Module', we can then populate 'Previous Transaction', and subsequently populate 'Previous Posting Date' and then calculate 'Days since Previous'.   Changing the summary method of 'Days since Previous' will give you the average of 'Days since Previous' at Materials level.   Thanks, LipChean ... View more

Hi,   Assuming you're using the standard versions, and not a custom version, you can try the following, which is also suggested by @bdeaton . I only attached some screen shots for your reference.     Note the 'Formula Scope'.   Thanks, LipChean ... View more