Anaplan Level 2

Sprint 1

  • Data Hub - a main repository for data, other models (i.e. Spoke Models) pull data from the Data Hub Model to perform analytics and other stuff

  • Data Validation in Data Hub - Create a Boolean line item that checks if a code output is bad (aka bad usually means the field is blank), lastly create a saved view that has all the bad data output fields filtered using the Boolean line item

    • Data validation should be done in Data Hub not in Spoke Models

  • Deleting from list using selection - If you have a lot of data to delete, it’s best to create a Boolean line item that you manually check off or create a code that will check off all requested deletions, and then use the Action → Delete from List using selection to do the deletion

  • Flat list vs. Hierarchal list in Data Hub

    • Flat lists - do not have a parent and are usually the only type of list in a Data Hub

    • Hierarchal lists - do have a parent and are for data visualization/analytics for end users, and usually, H lists are only in Spoke Models

  • Time Setting Module - These modules are used to filter data to specific ranges to view, import, and export

  • Import Errors

    • Invalid Parent Error - This happens when you import a child and the parent list does not exist or can’t be found because you chose the wrong source column

      • Fix it by populating the parent list or assigning the correct parent source column

  • Saved View - this is a filter of module columns, used to import to another module or list that only needs specific fields, data validation, and more

  • Show Selection vs Hide Selection

    • Show selection will hide any new line items created while hide selection will not

  • Action - recorded data imports, exports, and delete

  • Process - a set of previously done actions, that can be initiated like an automated workflow

  • Numbered List vs Standard List

    • Numbered lists are identified by code only, standard lists can be identified by name or code

  • Default File Option

    • Import Private Setting - File will be deleted off Anaplan after 48 hours

Sprint 2

  • Demand Planning Process Roles

    • Product Family Manager - Determines the anticipated sales of all products based on last year’s sales and projected sales, from a top-down approach called the Demand Forecast

    • Account Demand Manager - Alters the Demand Forecast anticipated sales of specific products to be more realistic based on specific customer areas, from a bottom-up approach

  • Initial Demand Forecast (Current Year Projected Sales) = Historic Volumes AKA Baseline Demand Forecast (aka Last Year Sales) * Volume Growth Rate

    • The Product Family Manager will determine the volume growth rate and apply it to the P1 Product Family level which will then be applied to P2 Product levels and then the actual products’ P3 SKU level

    • Account Demand Manager will make manual adjustments to specific products at P3 SKU level based on their knowledge of local customers after the Product Family Manager has applied the growth rate

  • Anaplan Front to Back Model Approach - Figure out which roles will have UX access and then think about what info is needed based on the roles

    • 1 Understand what business processes are completed by each role

      • Ask questions like what actions do they do, what data needs to be inputted and where does the data come from

      • Opt. Use an RACI (Responsible, Accountable, Consulted, Informed) Matrix

    • 2 Draw the Process

    • 3 Create a timeline to map the user roles to check for concurrent Issues

    • 3 Verify the process with end users

  • Graph Types

    • Grid - Show large sets of specific values where it is not important to see trends or comparisons

    • Line Chart - Show trends over a continuous timeline

    • Bar or Column Chart - Comparing values across different line or list items

    • Pie Chart - Comparing parts of a whole

  • Graph Differences

    • Bar Charts and Pie Charts are not used to compare values over time

    • Stacked Column charts are best for displaying part to whole relationships and how they impact the whole over time

  • Call to Action Approach - provide the user with the elements that require attention and the way to solve them (aka hand hold the user with instructions)

  • How to Group a Dashboard when there isn’t a natural order

    • A) Summary info first, then details, and provide navigation to other dashboards

    • B) Use the landing dashboard to tell the model story and key summary info, and provide navigation to other dashboards

  • How to make a Dashboard more user-friendly

    • Include a graph that is helpful to the dashboard

    • Change the language to be more user-friendly

    • Change the way the info is organized

  • Functions should only be created once and be added to a system module if it will be referenced several times

  • When to use SELECT

    • Compare Actual and Forecast variables

    • Generic Time settings like Actual/ Current Period Year, Year to Date, etc.

  • Avoid nested formulas because when one variable is updated all variables in the nested formula will be recalculated increasing the model workload, instead calculate each variable in its own line item