Skip to main content
hamburger menu Created with Sketch.
We are currently experiencing an issue with creating new support tickets from the Help Center portal. Some users are unable to select the appropriate form when submitting their tickets. We are working to resolve the issue.

Search the Knowledge Base

Explanation of the Territory Utilities and Salesforce Assignment Rule Processes in Veeva CRM

  • Updated

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Notes:
  • Brick-to-terr and/or zip-to-terr records must have multiple Territory Names (Not DeveloperNames) populated in the following format: ;territoryname1;territoryname2;territoryname3;
  • Brick-to-terr and/or zip-to-terr records must have the Territory Name (Not DeveloperName) populated in the following format: ;territoryname1;
  • Clearing the Veeva Cache is necessary before rebuilding the Veeva Territory Rules process. The assignment processes, Mass / Test Assigning, and SFDC Assignment may be initiated on the entire hierarchy, on specific territory branches, or specific territories.
  • The status of SFDC Assignment Rule jobs can be checked by navigating to Jobs -> Background Jobs.
  • It is strongly discouraged to remove Territory2AssignmentRule ObjectTerritory2Association (OT2A) records with manual or data loading methods. The necessary data/custom rule changes need to be made and these OT2A needs to be removed by the SFDC Assignment Process.
  • The Mass Assignment processes do not start the SFDC Assignment Process automatically.

Related Documentation:

CRM Help Documentation: 

Salesforce Documentation:

Knowledge Article:

 

Powered by Zendesk