it is a requirement because we want those who are level 3 model builders to know how to use it.
Hi @Guido.kaandorp ,
In a real life scenario we might use a different approach which is more solid in terms of code creation. The main reason for using this way of creating the items, as Chris pointed out, is to practice a different way for managing lists items. For example when we work in the new UX, one of the features for creating items in a list is highly similar to the Assign function from Model 3.
I wish you all the best with the build! Hope this helps.
Kind regards,
Costa
@Guido.kaandorp nice to read that you have the same line of thinking. 😎
Hi Chris,
In that case, US have 4 territories, so how will I assign an account (say - the account is based out of New York). Is there a process to identify these accounts among different territories? Identify by geography?
Thanks
AB
Hi Chris,
Pertaining to the territory assignment, currently we have weight based on 2 factors, could you provide some additional description of these factors:
1. Revenue (Potential/ Actual based on final target value): Is this based on the Sales reps present in each territory and their previous experience and capacity in terms of a $ value? Can we quantify the Small/Medium/Large segmentation in $ value?
2. Support Requirement(Small/Medium/Large Segmentation): Can we assume a numerical quantification to assign the level of support required as Small = 1, Medium = 2, Large =5, where we can determine that 3 small accounts require as much support that 1 Large account would? Could you provide further description of the level of support by account segment?
3. I am also assuming that the territory in your company is based on the Geographical territory within each country and that you would be providing the data file, based on discussion with questions asked by other builders, is that a fair assumption?
Thanks and best regards,
Mann
1. Revenue (Potential/ Actual based on final target value): Is this based on the Sales reps present in each territory and their previous experience and capacity in terms of a $ value? Can we quantify the Small/Medium/Large segmentation in $ value? I am assuming you are talking about commission for sales reps and not the Final Sales Targets for the accounts. In both cases, we do not use the segmentation for any calculations. For the Sales Reps commision, we look at their role and tenure to establish a commission and attainment rate based off of assumptions which will be given to you. While the Segment might influence the decisions on which accounts to Hold or Override, we do not calculate values based upon it.
2. Support Requirement(Small/Medium/Large Segmentation): Can we assume a numerical quantification to assign the level of support required as Small = 1, Medium = 2, Large =5, where we can determine that 3 small accounts require as much support that 1 Large account would? Could you provide further description of the level of support by account segment?
This is out of scope for this release. You will be given assignments.
3. I am also assuming that the territory in your company is based on the Geographical territory within each country and that you would be providing the data file, based on discussion with questions asked by other builders, is that a fair assumption? That is correct.
These assignments will be held for the year, there is no need to build in any functionality to account for reassignment. We just want to make sure we can finalize them and assure they will have a proper code.
Hi Anaplan Team,
In US 2.2 -2.3, We are setting up the count calculation for QU001 and QU002 modules. Till now, Only a Territory file is provided to be loaded in Hub with out any account mappings. To complete this we need account data for the territory which is not available yet.
To finish 2.2 - 2.3, How do I know the Account to Territory mapping? Should I use the assign process to set up a sample mapping till actual data is provided