To configure this feature:

1. Ensure Configuring Accounts 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	Read
   territory__v	R	n/a	description__v	Read
   user_territory__v	R	n/a	n/a	n/a

   * Create and Edit permission are optional to allow renaming

6. Navigate to Admin > Configuration > Objects > Account object.
7. Grant Edit access to the territory_field_section__v object control.

8. Add the territory_field_section__v object control to the appropriate layouts on the account__v object.

9. Navigate to Business Admin > Objects > Veeva Settings.

10. Select the territory_link_on_account__v Veeva Settings check box.

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.

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. For more information on viewing territory information on the Account Detail page, see Viewing Territories on Accounts.

To view territory fields on accounts:

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

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. 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
• ytd_activity__v - The total number of recorded calls in the year to date (YTD) for the account in the given territory, excluding planned calls. This field is updated when calls are saved.

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.

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 create a call for an account, the territory field record is updated for that account and territory when the call is saved or submitted
• The ytd_activity__v and last_activity_date__v fields on the tsf__v object are updated by a trigger on the call2__v object. The last_activity_date__v is set to the call_date__v value from the call record, and ytd_activity__v is incremented by one.

  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.

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.