201 Intermediate Model Building Section 8 actvity #10 Numbers don't match

I'm working on Section 8 of IMB and the numbers in the sub-region Goal set don't match for US South and US Central. The totals in the bottom row do match with the guide and instruction video, but these specific sub-regions don't. PY Sales and Sub-region % are correct, but the Projected Goal is not. All other sub-regions seems to be correct.

I have included screenshots from my module, the formulas I used and the instruction video to show the difference

Instruction_video_33431.png

Formulas_33431.png

Sub-region_goal_set_my_module_33431.png

Accepted answers

Evalinde

Solved the problem! I used the Projected Goal iso the Final Goal. Fixed it.

All comments

PaulRitner

In Sub-region Goal Set, the Projected Goal line item pulls the Final Goal from Region Goal Set.

Evalinde

Hi Paul, I think that is what I did. The formula I used for the Projected Goal in the Sub-regio Goal Set module is 'Sub-region Percent' * Region Goal Set.Projected Goal[LOOKUP: Parent]

I find it very confusion also that it is only for these two sub-regions that I have issues and the other ones are correct. Or maybe that's a coincidence?

Evalinde

Solved the problem! I used the Projected Goal iso the Final Goal. Fixed it.

Quick Links

Can you help?

Unanswered questions

Importing from Data Hub: Incorrect or Missing Mappings in Target Model
When importing data from a Data Hub to another model, I'm seeing values in the target model that don't exist in the source. For example, seller assignments are being tagged with subregions that aren't present in the source data - some assignments are missing expected tags, while others are mapped to seemingly random…
ANAPLAN XL View
Hi, I need help in pulling a specific view in Anaplan XL. The first grid should display attributes of various projects, while the second grid should present the monthly financial data for these projects. Thanks in advance.
Add list members to a selective access list
Hi, I am working on a solution where the User should only have access to write/edit the list members that they add from an Action on the frontend. This action adds another list member to a selective access list. The problem is, in order to run the action, you need access to the entire list, so you would see all list…