L3 Percentage calculation Not Matching

Dikshant

L3 Sprint 1 - User Story 5

My Percentage is not matching

This is my Ratio. Let me know where I'm going wrong.

Accepted answers

Kanishq17

hi @Dikshant

I believe your formula of

PY sales by country and prod family is wrong , since you are referring to forecast data , the value should be actual PY sales by country and prod family i,e PY

i have referred PY sales numbers

then this ratio aggregated by country and prod family should be 1 since basically ratio is of account sale by country and prod family associated with that account

hope this helps

All comments

JaredDolich

@Dikshant

Not sure I see the calculation breakdown but you do have a lot of subsidiary views that could be the cause. Generally we only use subsidiary views when we need them for filtering (exports and reports). For planning, it's usually better to rely on system modules that carry the mapping. In this way we calculate the value once and refer to it often from one place. This also avoids issues with synchronizing calculations since the calculation is only coming from one place.

Chapter 2 - Anaplan Community (2.01-06) Avoid Subsidiary Views.

Dikshant

@JaredDolich
Those subsidiary views are referring to system modules only. Just making Time Scale to None as it was an unnecessary dimension.
Do you think of any other reason for those percentages to be correct as per the Level 2 Requirements?

Kanishq17

hi @Dikshant

I believe your formula of

PY sales by country and prod family is wrong , since you are referring to forecast data , the value should be actual PY sales by country and prod family i,e PY

i have referred PY sales numbers

then this ratio aggregated by country and prod family should be 1 since basically ratio is of account sale by country and prod family associated with that account

hope this helps

Dikshant

Thank you for your response. Yes, I do realize this and corrected it already.

Quick Links

Can you help?

Unanswered questions

Azure SQL Connection, database name with Hyphens in Data Orchestrator
I am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
12.4.1 Activity: Create Saved View for Non Employee Expenses
Hi, for some reason my shipping costs are the same over every month and I don't know what to do to fix it.
Workaround for Formula & Closing Balance summary methods together in Polaris
Hello folks, Does anyone know how to work around the Polaris limitation of using the Formula or Ratio summary method alongside the Closing Balance within the same line item? I have a Business Unit list where the total (All BUs) must display the Corporate (1 of 20 leaf items under All BUs total) number of Unique Customers.…