Territory Dimension Data Report
The territory dimension data report identifies the volume of territory data for each territory dimension and coverage type. You can use information from this report to determine the sequence for each assignment mapping and optimize assignment performance.
You must run this report only after you have created and activated your production territories.
Access the Diagnostic Dashboard to generate the territory dimension data report. The report shows the number of denormalized customer account-centric and partner-centric territory records for each territory dimension and coverage type. The function code field is used to specify a unique identifier for the attribute. Where dimensional territory coverage isn't defined, the report shows the counts for inherited customer and partner inclusions and exclusions that are manually defined.
This table shows an example of a territory dimension data report:
|
Function Code |
Count for INCLUSION |
Count for EXCLUSION |
Count for PARTNER_REGULAR |
Count for REGULAR |
|---|---|---|---|---|
|
AcTyp |
7 |
3 |
16 |
305 |
|
Acct |
0 |
0 |
16 |
313 |
|
Aux1 |
7 |
3 |
16 |
385 |
|
Aux2 |
7 |
3 |
16 |
385 |
|
Aux3 |
7 |
3 |
16 |
385 |
|
CSize |
7 |
3 |
13 |
336 |
|
Geo |
7 |
3 |
2 |
4 |
|
Indst |
7 |
3 |
14 |
268 |
|
OrgTp |
7 |
3 |
14 |
374 |
|
Prod |
2 |
3 |
16 |
171 |
|
Prtnr |
7 |
3 |
16 |
385 |
|
Schnl |
7 |
3 |
16 |
259 |
Once the report is generated, you must identify the sequence of mappings as follows:
-
Copy the report to a spreadsheet.
-
Sum up the count for inclusion, exclusion, partner_regular, and regular for each function code.
-
List the function codes in order from lowest total count to highest.
After you list function codes from lowest count to the highest, the report table should look like this:
|
Function Code |
Count for INCLUSION |
Count for EXCLUSION |
Count for PARTNER_REGULAR |
Count for REGULAR |
Total Count |
|---|---|---|---|---|---|
|
Geo |
7 |
3 |
2 |
4 |
16 |
|
Prod |
2 |
3 |
16 |
171 |
192 |
|
Schnl |
7 |
3 |
16 |
259 |
285 |
|
Indst |
7 |
3 |
14 |
268 |
292 |
|
Acct |
0 |
0 |
16 |
313 |
329 |
|
AcTyp |
7 |
3 |
16 |
305 |
331 |
|
CSize |
7 |
3 |
13 |
336 |
359 |
|
OrgTp |
7 |
3 |
14 |
374 |
398 |
|
Aux1 |
7 |
3 |
16 |
385 |
411 |
|
Aux2 |
7 |
3 |
16 |
385 |
411 |
|
Aux3 |
7 |
3 |
16 |
385 |
411 |
|
Prtnr |
7 |
3 |
16 |
385 |
411 |
With this information, you can now update the sequence for each assignment mapping. The function code with the lowest total count, Geo in this example, should be updated to have the sequence 1. The next lowest total count, Prod in this example, should have sequence 2, and so on. You must update the sequence similarly for every mapping in each mapping set, for every work-object and candidate-object combination.