Platform

LipChean_Soh · ‎10-12-2019

Hi @CarlCochez , Like how we normally do it, you assign Read/Write access to Modules for specific Roles. However there is a difference between classic dashboards and NUX. For 'classic dashboards', you cannot 'assign' a dashboard to a role in the 'Content' page, unless that role has Read or Write access to ALL the elements in that dashboard, be it module or actions. For NUX, you need not 'assign' a Page to a role (there's no place for you to do that anyway). If a role does not have Read or Write access to any module, you'll get the following error message at Card level within NUX. The image below shows that i (assigned to '1 Module Role') have R/W access to the module in the top Card, but i don't have access to the module in the bottom card. Please note that the above are behaviours currently observed for NUX. As more product releases are pushed out, the above might change to improve user experience and ease of model building. Thanks, LipChean

LipChean_Soh · ‎10-11-2019

Hi @Misbah I'm curious, can you show how you "r efer the Expected Return date & Incoming from First Module as Anaplan will automatically roll up the numbers from Days to Months" And what if there are multiple values to be aggregated to the same month? Thanks, LipChean

LipChean_Soh · ‎10-11-2019

Hi, You can use the POST formula as shown below. Note that you can enter different lead time, and the POST keyword will accumulate accordingly onto the same day. The 'Incoming' date calculated in 'Cee Cee From' isn't used in POST, i just put it there for reference purpose. Thanks, LipChean

LipChean_Soh · ‎07-27-2019

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

LipChean_Soh · ‎07-24-2019

Hi, Alternatively, you can use a standard feature within the import action shown below. Since the 'clearing' options appear on each tab, choose 'All items' for the list of which you intend to clear ALL items. Thanks, LipChean

LipChean_Soh · ‎07-10-2019

Hi, Can you perhaps explain what you're trying to achieve by creating a mock up in a spreadsheet and attaching the screen shots? Thanks, LipChean

LipChean_Soh · ‎07-10-2019

Hi, To your point about the 48 hrs validity, it refers to data files that you upload into Anaplan, it depends on the private/default settings that you can learn more about below: https://help.anaplan.com/anapedia/Content/Import_and_Export/Import_Data_into_Models/Overview_Private_Default_Files.htm?_ga=2.184610346.2085110697.1562746682-1239638901.1550667215 But once data from the data files are loaded into Anaplan, and if you accidentally deleted the model, then you should email Anaplan support immediately, Anaplan support might be able to help recover the deleted model. But generally speaking, if you're not sure whether a model should be deleted or not, i would suggest that you archive the model. Thanks, LipChean

LipChean_Soh · ‎07-05-2019

Hi, As much as everyone in this forum would love to help you, the problem you're trying to solve is too big. I suggest you break your problem into more manageable pieces, and ask more specific questions. Thanks, LipChean

LipChean_Soh · ‎07-05-2019

Hi, You can try the following: Assuming you have 3 Time Ranges shown above. Note the 'Time Scale' and 'Time Range' in the 'FY20 - FY21' line item. Please build according to DISCO, and build 'FY20 - FY21' in a separate System module. Thanks, LipChean

LipChean_Soh · ‎06-24-2019

@Vladimir I agree with @DavidSmith, i.e. " Can you ask to provider of the file to do this? It will simplify the problem because Anaplan is not an ETL tool" Remember, just because we can do it, doesn't mean we should do it. As mentioned at the beginning of my suggestion, the setup of Unique Codes should be done outside of Anaplan, since Anaplan is a client facing tool and not a database tool. Thanks, LipChean

LipChean_Soh · ‎06-24-2019

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

LipChean_Soh · ‎06-23-2019

Hi, You can perform 2 imports sequentially, i.e. the first from whatever source into 'All Entries', and then the second from 'All Entries' into 'Alphabets'. You can incorporate a delta mechanism, such that previously imported 'All Entries' are flagged, and not imported again from 'All Entries' into 'Alphabets'. Thanks, LipChean

LipChean_Soh · ‎06-23-2019

Hi, There are 2 lists, All_Entries corresponds to your longer list; Alphabets corresponds to unique members created from your longer list. The 'Code' line item is of 'Text' format, this is used to create the 'Alphabets' list through import action. The rest of the formulas are shown. Thanks, LipChean

LipChean_Soh · ‎06-23-2019

Hi, @Manuela_Apostol did a good post about this recently. You can refer to https://community.anaplan.com/t5/Anaplan-Platform-Discussions/Is-there-a-formula-to-get-the-current-date/m-p/47182#M5956 Thanks, LipChean

LipChean_Soh · ‎06-22-2019

Hi， What do you mean by ' filter unique codes throughout all dimensions including versions'? Perhaps you can show the expected end results in another screen shot? Thanks, LipChean

LipChean_Soh · ‎06-22-2019

Hi, If i just look at the first row, what are "BU", "UA", "2610", "1", "302066"? Why is the Code for row 1 and 2 the same? Why do you have different separators of _ and *? Thanks, LipChean

LipChean_Soh · ‎06-22-2019

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

LipChean_Soh · ‎06-22-2019

Hi, I'll be helpful if you can create and share an excel mockup of what you're trying to achieve. Thanks, LipChean

LipChean_Soh · ‎06-22-2019

Hi, The keyword you're looking for is YEARVALUE. I've attached a simple example of dividing yearly value by 12 below. Thanks, LipChean

LipChean_Soh · ‎06-21-2019

Hi, The issue you're facing is not uncommon, and you're right to recognize there's a better alternative to storing these unique combination of Division_Product. You should check out 'Numbered List' to help you achieve what you want. https://help.anaplan.com/anapedia/Content/Modeling/Build%20Models/Lists_and_Roll-ups/Numbered_Lists/Numbered_Lists.html Thanks. LipChean

LipChean_Soh · ‎06-14-2019

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

LipChean_Soh · ‎06-13-2019

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

LipChean_Soh · ‎06-13-2019

Hi @karank , Yes, Rank is a simple List with members from 1 to X. X should be a number less than the highest number of 'Transactions' list found within any 'Materials' list, if we refer to my illustration above. And it's always safer to put in a buffer for X, since it won't contribute that much Workspace to the module 'Find Transactions', i.e. # of Materials multiplied by # of Ranks. Thanks, LipChean

LipChean_Soh · ‎06-12-2019

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

LipChean_Soh · ‎06-12-2019

You're welcome @ArunManickam

LipChean_Soh · ‎06-12-2019

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

LipChean_Soh · ‎06-12-2019

Hi, Before we talk about the solution, i do want to talk about 'In Anaplan, just because you can, doesn't mean you should'. All of us love Anaplan, because it's super flexible and we feel empowered. But we must realize that Text must ONLY be used where ABSOLUTELY NEEDED, and not as a means to capture everything from the source system (at least i think that's why you did what you did). Text takes up a lot of workspace, and it consumed a lot of server overhead in the background, dragging the overall performance of your model. Please talk to whoever needed, be it the Database folks or the business users to make sure the source is number formatted before sending it over to Anaplan. I might be wrong in my assumption, and please correct me if i'm wrong by providing more context. Do explain the above effects to the client. Having said that, please see if the following works. Do note that i'm using ROUND, VALUE keyword, and the 'Decimal Point' options in the number format page. Thanks, LipChean

LipChean_Soh · ‎06-07-2019

Hi, You can use DCA as shown below: Thanks, LipChean

LipChean_Soh · ‎06-06-2019

Hi, Do see if the following time dependent Sales to Plan relationships shown below works for you. The 'Plan' formatted list is a field you can assign to different Sales at different point of time. To prevent yourself from entering new/old Plan ID every month, you can use the formula shown below to update itself with previous Plan ID unless there's a change in this month's Plan ID. Then subsequent modules can refer to 'Plan ID (Final)' for an up to date Sales-Plan assignment. Another observation i made is that you use 'Plan ID' as the Code of Sales ID. I would strongly suggest against it, because we should use CODE the way it's intended, i.e. as a unique alphanumeric texts to identify the particular list member, so that Inbound/ Outbound integration is made easier. Having a good CODE naming convention is important towards Connected Planning. Thanks, LipChean

LipChean_Soh · ‎06-06-2019

Hi Elaine, I'm still confused with your requirements. What do you mean by tagging? Can you create an example of what list 1 and list 2 are? What are the name of the subsets, and what business problems you're trying to solve? Thanks, LipChean

Platform

Academy

Master Anaplanner

Programs

About LipChean_Soh