Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Accounts/ManagingAccountInfo/WorkingwithTerritoryFields.htm

## Working with Territory Fields

The Territory Field object (tsf\_\_v) stores data specific to an account and territory relationship. Territory Field management allows users to maintain and view territory-specific fields for a particular account. Many of the fields in this object are auto-populated from other processes; the fields cannot be deleted or modified. New fields can, however, be added to the object.

This feature is essential for ensuring that sales representatives and other users have visibility into key interactions, status updates, and relevant data within their designated territories. Managing this information on the Account Details page improves accuracy and contextual awareness.

For example, if a user wants to know when the last interaction in her territory was made with an HCP, she can look at territory-specific fields and see the last interaction in the value for the territory. This section also contains information about whether the HCP is a target for this specific territory.

**Who can use this feature?**

* Business Admin Users — Browser
* [Viewing Territory Information](#ViewingBusAdmin)
* [Creating Territory Field Records](#Creating)
* [Defining Territory Field Layouts by Account Type](#Defining)
* [Defining Allowed Products by Territory](#ProdAlign)
* End Users — Browser, iPad, Windows
* [Viewing Territory Field Information](#Viewing)
* [Updating Territory Field Information](#Updating)
* [Using Territory Field Information for iPad](#Using)
* Users do not require an additional license

### Configuring Territory Field Management for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
All Users](#)

To configure this feature:

1. Ensure [Configuring Accounts](../AcctConfig.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select **Objects**.
5. Grant the following permissions:

   | Object | Object Permission | Object Type | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | tsf\_\_v | CRE\* | All applicable object types | * account\_\_v * yearly\_call\_activity\_\_v | Read |
   | tsf\_yearly\_activity\_\_v | R | n/a | * call\_count\_\_v * tsf\_\_v * year\_\_v | Read |
   | territory\_\_v | R | n/a | description\_\_v | Read |
   | user\_territory\_\_v | R | n/a | * user\_\_v * territory\_\_v | Read |

   \* Create and Edit permission are optional to allow renaming
6. Grant View access to the **territory\_field\_section\_\_v** object control on the account\_\_v object.
7. Grant View access to the **view\_user\_territory\_section\_\_v** object control on the account\_\_v object.
8. Navigate to **Admin > Configuration > Objects > Account**.
9. Add the **territory\_field\_section\_\_v** section control to the appropriate layouts on the account\_\_v object. This section allows users to view territory-specific field values for the account.
10. Add the **view\_user\_territory\_section\_\_v** section control to the appropriate layouts on the account\_\_v object. This section allows users to view which territory the account is assigned to, and all users assigned to that territory.
11. Navigate to **Business Admin > Objects > Veeva Settings > Veeva Global Settings**.
12. Select the **Territory Link on Account** Veeva Settings checkbox.

### Using Territory Field Information as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
Business Admin Users](#)

#### Viewing Territory Information

To view territory information for an account, select the Territory Fields related list on the account record.

#### Creating Territory Field Records

Territory field records can be created manually, by data loading, or through a third party integration. In addition, territory field records are automatically created when any of the following occur:

* When users save or submit a call report for an account without a territory field record, a territory field record is automatically created for that account and territory combination. The My Preferred Address (address\_\_v) and/or My Preferred Location (preferred\_account\_\_v) fields on the new territory field record are automatically populated with the address and location selected on the call report.
* At the end of the Account Wizard, one record on the tsf\_\_v object is automatically created for each territory and account profile combination, if any fields from the tsf\_\_v object are set as required on the layout

#### Defining Territory Field Layouts by Account Type

Admins can customize territory field layouts to display different information depending on the type of account selected. To define tsf\_\_v layouts by account object type, create a territory field object type with the exact same API name as the corresponding account’s object type.

When adding custom account object types, also create corresponding custom territory field object types.

#### Defining Allowed Products by Territory

To enable organizations with parallel sales teams to appropriately align and target accounts with targeted product messaging, admins can define a list of allowed products for each territory. Users can only select product details, samples, BRCs, and promotional items included in the allowed products list when recording a call.

For example, an end user is assigned to Territory 101. The allowed\_products\_\_v field on the territory field record for Territory 101 is populated with Cholecap;;Labrinone. When the user records a call with an HCP in Territory 101, the user can only select either Cholecap or Labrinone from the list of detail products.

To define allowed products for a specific territory, populate the allowed\_products\_\_v field with a double semicolon delimited list of product names. The product names must exactly match the product names in the Product Catalog. For example, Cholecap;;Restolar;;Labrinone

Allowed products are also stored on territory field records. For more information, see [Defining Allowed Products](../../Call_Reporting_2/Restrictions/AllowedProd.htm).

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)
End Users](#)

End users can view and edit territory field information for accounts.

#### Viewing Territory Field Information

Territory field values are available via the Territory Field section on the Account Detail page.

To view territory fields on accounts:

1. Navigate to the **Account Detail** page.
2. Expand the **Territory Field** section.

![](../../../Resources/Images/Accounts/TerritoryManagement/TerritoryOnAccountDetails.png)

The following fields on an account's territory field record are used to capture territory-specific information:

* last\_activity\_date\_\_v - The most recent date a call was made to the account for the given territory. When users save or submit a call report, the last\_activity\_date\_\_v field on the account's territory field record is set to the call\_date\_\_v value from the call2\_\_v record. This date persists across calendar years and reflects the most recently saved or submitted call, even if that call occurred in a prior year. The last\_activity\_date\_\_v field does not include dates for planned calls.
* my\_target\_\_v - Determines whether the account is specifically targeted in that territory
* preferred\_account\_\_v (My Preferred Location) - Lookup to the location for the account on the territory field record. This is a business account affiliated with the account on the territory field record. Affiliations can be created through the Sphere of Influence, Stakeholder Navigator, or Account Hierarchy.
* territory\_\_v - The name of the territory for which the territory field record applies
* yearly\_call\_activity\_\_v - The total number of recorded calls in the year to date for the account in the given territory, excluding planned calls. This field is updated when calls are saved or submitted. This count automatically resets at the beginning of each calendar year.
* To support annual resets for the yearly\_call\_activity\_\_v field, call counts are captured on a separate tsf\_yearly\_activity\_\_v record for each calendar year. The call\_count\_\_v field on the current year’s tsf\_yearly\_activity\_\_v record is the basis for yearly\_call\_activity\_\_v values.

If a user is assigned to multiple territories, the territory fields object control displays the first record based on alphabetical sorting of the name\_\_v field on the territory\_\_v object.

#### Addresses in Accounts

When an account has multiple addresses, the preferred address for the territory, stored in the tsf\_\_v object, is used. If a preferred address is not identified, the primary address displays. The primary address is the main address for the account.

#### Updating Territory Field Information

A territory field record is created immediately after the account\_territory\_\_v record is created, so all accounts always have a territory field record for all territories to which they are or have been assigned.

Users with Create and Edit object permission for the tsf\_\_v object can edit territory field records. In addition, territory field information is automatically created or updated when any of the following occur:

* At the end of the Account Wizard, one record on the tsf\_\_v object is automatically created for each territory and account profile combination, if any fields from the tsf\_\_v object are set as required on the layout
* When users save or submit a call for an account, the territory field record is updated for that account and territory combination:
* The yearly\_call\_activity\_\_v field displays the call count from the current year's tsf\_yearly\_activity\_\_v record, while the last\_activity\_date\_\_v field reflects the most recent call activity regardless of year

  The account and territory combination on the territory field record must match the assigned territory and account on the call for the record to update.
* When a field value, for example, route\_\_v, is updated in an account’s Territory Fields related list, the territory field record is updated as well

If records do not exist for the account and territory combination, a new territory field record is created. The Name field on the new territory field record automatically populates with the Territory ID. Users can edit the record and change the name if they have Create and Edit object permission on the tsf\_\_v object.

Users receive an error message if they attempt to create a duplicate record. The external\_id\_\_v field on the tsf\_\_v object is a unique concatenation of the account and territory. A trigger on the external\_id\_\_v field prevents users from creating duplicate records.

#### Using Territory Fields for iPad

On the iPad platform, territory specific fields display inline on the Account Detail page. Users in other territories can select an account to see their territory information. If territory field layouts are customized by account type, the order and type of tsf\_\_v fields displayed follows the appropriate layout for the account object type.

![](../../../Resources/Images/Accounts/TerritoryManagement/TerritoryFieldiPad.png)

Users can edit territory-specific fields on mobile devices, if they have the appropriate permissions. Territory field records are updated when users populate tsf\_\_v fields. Unpopulated fields still display.

Once the address\_\_v field on the tsf\_\_v object is populated, it is no longer updated when users save or submit subsequent calls for the account. This prevents the address\_\_v value on the territory field record from being overwritten.

### Related Topics

[Managing Account Hierarchies](AccountHierarchy.htm)

[Sphere of Influence](Sphere_of_Influence.htm)

[Accounts Overview](../AcctOverview.htm)