For this release, the actions taken to balance will be done manually outside of Anaplan. We just need the ability to see the targets that each territory has.
On what basis, i need to update the "G4T Territory>Account#" list to proceed with "QUO01 Territory Account Validation" ?
https://community.anaplan.com/t5/Anaplan-Platform/Level-3-Sprint-2-US-2-1/m-p/66165
[ Correct me if i am wrong in my steps: I have created the Hierarchies [G1 Region, G2 Country, G3Territory list ] in Data hub and then created the System module in the Data Hub as per the SYS 05 sales planning model or {as per CSV file provided in the U.S}.]
Hi @xrprasadx ,
In one of the user stories it is explained how to build the hierarchy (what conditions to follow). As a suggestion, we want to reduce sparsity when creating this list. So think about what we need to do in order to reduce it.
Hope it helps!
Kind regards,
Costa
Unicorn Candy Company seems to be specifically requesting the Assign function per the UX Checklist. They must of seen this from an Anaplan Sales Rep.
The issue with the assign function is that it doesn't import a Code into the list when used. This is a terrible thing in a SPM model.
By NOT using the assign function and creating a simple import process with picklist selection (so I can get creative with codes which would allow for a better model experience down the line and more dynamic lookups as I can populate specific properties), I can streamline the assignment of accounts while making User Story 2.2 unnecessary by not allowing the assignment of a single account to multiple territories to begin with.
Would Unicorn Candy Company be okay with creating a process as it is a far better, more robust and safer solution? Or is there a specific reason they want the assign function?
If they must have the assign function, do we need to capture a finalization process user story where we can then import the codes into the list items that have been assigned?
We are very keen on using the Assign function and we require that after all assignments are made codes are aligned.
Was thinking exactly that !
@Guido.kaandorp is correct here.
What we would be able to do by not using the assign function is give actual scenario planning ability with picklists. You could create multiple views (something that is in my current wireframe) and allow them to compare different roll-up values. The only reason they would want the assign function is to move items around and play around with account to territory assignments, but it makes if difficult to see any comparison because values are constantly changing.
I will build using the assign function because I don't want to waste any more time, but I believe this certification exercise is making us build a less than ideal T&Q solution.