Question:

The aim of this article is to explain the purpose of each Territory Utilities process along with the Salesforce Account Assignment Rules process briefly.

Answer:

1. Clearing the Veeva Cache is the first process. The Rebuild Veeva Territory Rules process requires clearing the Veeva Cache in order for the current or updated Territory Names to be queried and retrieved in the Veeva CRM instance.

In the Territory Utilities tab there are three types of jobs:

• Rebuild Veeva Territory Rules
• Test Territory Assignment
• Run Mass Assignment

SFDC (Salesforce) Account Assignment is considered the fifth process, which can be performed on the Territory Detail or on the Territory Model.

2. Rebuild Veeva Territory Rules
   
   This process creates one SFDC local Assignment Rule and criterion for all Territories. This Rule, with its criterion, ensures that the SFDC Assignment process considers the Territory VoD values. The Territory Name (Not the DeveloperName) is added to the criterion.
   As there is an AND connection among all SFDC Assignment Rules under a single territory, any customer-defined rules (Local or Inherited) is taken into consideration in the SFDC Account Assignment process later.
   In the event, that the name of the Territory is updated - the Veeva Cache is cleared - the Rebuild Veeva Territory Rules process deletes the previous SFDC Assignment Rule, criterion, in turn, creates a new updated Rule, criterion with the new Territory Name.
   
   
3. Test Territory Assignment
   
   This process populates the Territory test VoD field on Accounts based on their brick to terr and zip to terr associations. Territory Names (Not DeveloperNames) are populated. Account, Address inclusions, and exclusions are respected. The purpose of this field is to provide an estimation for the customer. Example: How many accounts are going to be assigned to which territories. It serves as a preview.
   
   
4. Run Mass Assignment
   
   This process populates the Territory VoD field on Accounts based on their brick to terr and zip to terr associations. Territory Names (Not DeveloperNames) are populated. Account, Address inclusions, and exclusions are respected. The SFDC Assignment process using the Veeva Territory Rules uses this field.
   
   
5. SFDC Account Assignment
   
   This process retrieves the Accounts, and respective Territory VoD values using the Veeva Territory Rules: customer-defined SFDC Assignment Rules (Local and Inherited).  It creates the AssociationCause = Territory2AssignmentRule ObjectTerritory2Association (OT2A) records.

It is highly recommended to review the following SFDC article which provides a detailed explanation of How Account Assignment Rules Work.

The two relevant SFDC objects related to SFDC Assignment Rules are as follows:

• ObjectTerritory2AssignmentRule - Stores the Rule record itself
• ObjectTerritory2AssignmentRuleItem - Stores the Criteria itself

The records of these objects may be managed using Data load. It is strongly recommended to take a regular backup of the records of these objects.

Related Documentation:

CRM Help Documentation: 

• Territory Management Overview

Salesforce Documentation:

• How Account Assignment Rules Work
• Run territory assignment rules when you edit an Account

Knowledge Article:

• Is It Possible to Create and Maintain Salesforce Assignment Rules Beginning with the Name of VT in Veeva CRM Manually?
• What are the Maintenance Steps of the Mass Assignment Process of the Territory Utilities Tool of Veeva CRM?
• Is it Possible to Stop any Type of Mass Assignment or SFDC Assignment Rule Jobs in Veeva CRM?
• During Mass/Test Assignment, How are Accounts Selected Based on the Include In Territory Assignment and Primary Fields of the Address Object in Veeva CRM?
• The Territory Mass Assignment is Unexpectedly Launched for Every Territory in Veeva CRM
• Is it Expected that the Mass/Test Assignment Process Updates Account Records Multiple Times in Veeva CRM?