Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Accounts/CreatingAccounts/StampingCountryInformation.htm

## Stamping Country Information for Account and User

To enable business users to track and report on activity data by country, country information can be automatically stamped on transactional records. The country value is copied from the User and/or Account object.

For example, a business administrator who has access to records from multiple countries wants to view Approved Email activity by country. He creates a report grouping the records by the country\_account\_\_v field. This report gives the admin a clear understanding of the distribution of email recipients by country.

**Who can use this feature?**

* Business Admin Users — Browser
* [Understanding Stamping Logic](#Understanding)
* [Viewing Activity by Country](#Viewing)
* End Users — Browser
* [Understanding Stamping Logic](#Understanding)
* [Stamping Country Information for Account and User](#Stamping)
* Users do not require an additional license

### Configuring Stamping Country Information for Account and User 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 **Business Admin > Objects > Veeva Settings** **> Global Veeva Settings**.
3. Populate the **enable\_country\_dimension\_\_v** Veeva Setting with a value of 1 at the Vault level (Global Veeva Setting). The default value is 0, which means transactional activity is not tracked by country.

   This setting enables the feature for all users in the Vault. Profile-level enablement is not supported.
4. Enable the [enable\_country\_state\_language\_cda\_\_v](../../General/AppendixACustomSettings.htm) Veeva Setting at the Application Profile level to use the country\_cda\_\_v field when determining the country. (This step is optional.) If there is no setting at the Application Profile level, the Global Veeva Setting is used instead.
5. Navigate to **Business Admin > Objects** **> account\_\_v**.
6. Populate the country\_code\_\_v or country\_cda\_\_v field on the account\_\_v object (depending on the enable\_country\_state\_language\_cda\_\_v Veeva Setting).
7. Navigate to **Business Admin > Objects > user\_\_sys**.
8. Populate the **country\_code\_\_v** field on the user\_\_sys object.

#### Optional Configuration

To enable users to override the field values listed for the objects in the following table.

The override works only when the value in the transaction object is not blank.

1. Navigate to **Admin > Users & Groups > Permission Sets**.
2. Select the appropriate permission set.
3. Select the **Objects** tab.
4. Grant the following permissions:

   | Object | Object Permission | Object Type | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | account\_\_v | CRE | All applicable object types | * country\_\_v * country\_cda\_\_v * country\_code\_\_v | Edit |
   | call2\_\_v | CRE | All applicable object types | * country\_account\_\_v * country\_user\_\_v | Edit |
   | em\_event\_\_v | CRE | All applicable object types | country\_user\_\_v | Edit |
   | inventory\_monitoring\_\_v | CRE | All applicable object types | country\_account\_\_v | Edit |
   | medical\_inquiry\_\_v | CRE | All applicable object types | country\_account\_\_v | Edit |
   | medical\_insight\_\_v | CRE | All applicable object types | * country\_account\_\_v * country\_user\_\_v | Edit |
   | multichannel\_activity\_\_v | CRE | All applicable object types | * country\_account\_\_v * country\_user\_\_v | Edit |
   | order\_\_v | CRE | All applicable object types | * country\_account\_\_v * country\_user\_\_v | Edit |
   | remote\_meeting\_\_v | CRE | All applicable object types | country\_user\_\_v | Edit |
   | sent\_email\_\_v | CRE | All applicable object types | * country\_account\_\_v * country\_user\_\_v | Edit |
   | user\_\_sys | CRE | All | country\_\_v | Edit |
5. Navigate to **Admin > Configuration > Objects**.
6. Place the **country\_code\_\_v** and **country\_cda\_\_v** fields on the appropriate account\_\_v layouts.
7. Place the **country\_\_v** field on the appropriate user\_\_sys layouts.
8. Place the **country\_user\_\_v** field and the **country\_account\_\_v** field on the appropriate object layouts.

   Refer to the table above for a list of applicable objects.

### Understanding Stamping Logic as

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

All objects listed in the table above are enabled for stamping and use the following shared stamping logic:

* Shared stamping logic retrieves the value from the country\_code\_\_v field on the User object from the Owner field on the stamped object. For example, when a user records a call, the country\_user\_\_v field on the call2\_\_v record is set to US if the country\_code\_\_v field on the call owner's User record is set to US. In this case, the correct User record to pull the country code from is identified from the Owner field on the call report.
* Shared stamping logic retrieves the value from the country\_code\_\_v or country\_cda\_\_v field (depending on the enable\_country\_state\_language\_cda\_\_v Veeva Setting) on the Account object from the account\_\_v field in the stamped object. For example, if a user records a call for a German physician and the enable\_country\_state\_language\_cda\_\_v setting is set to No, the country\_account\_\_v field on the call2\_\_v record is set to DE because the country\_code\_\_v field on the HCP’s Account record is set to DE. In this case, the correct User record to pull the country code from is identified from the account\_\_v field on the call report.

  The application uses the ownerid\_\_v field on the following types of records to determine if a profile-specific enable\_country\_state\_language\_cda\_enablement\_\_v Veeva Setting is present. If no profile-specific setting is present, the global Veeva Setting is used.

  * call2\_\_v
  * inventory\_monitoring\_\_v
  * medical\_inquiry\_\_v
  * medical\_insight\_\_v
  * order\_\_v
  * multichannel\_activity\_\_v
  * sent\_email\_\_v

  For Multichannel Activity records, the record owner's profile configuration is used to determine if the country, state, and language enablement Veeva Setting (enable\_country\_state\_language\_cda\_enablement\_\_v) is active, and the account country is stamped accordingly. This ensures territory-specific data remains accurate across all multichannel interactions.

### Viewing Activity by Country as

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

To view activity by country, business admin users can create a report grouping records by the country\_account\_\_v field. This report gives the business admin a clear understanding of the activity distribution by country. For information on creating reports, see [What are Reports?](https://vaultcrmflightpath.veeva.com/doc/Content/Analytics/ReportsDashboards/3_whatAreReports.htm)

### Stamping Country Information for Account and User as

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

When a user creates a transactional record, Vault CRM automatically stamps the country value on the record, unless the user enters a country value manually.

When a user edits an existing transactional record, Vault CRM only stamps the value if the field is not already populated, to avoid overwriting any manually-entered data. The value initially stamped on the transactional record is retained unless a user updates the country value in subsequent record edits.

If a user manually clears the country value by selecting None, Vault CRM retrieves the country value and stamps it on the record.

Country records for United Kingdom regions are automatically updated across all Vaults to ensure data consistency. The country records for "United Kingdom (Northern Ireland)" and "United Kingdom (excluding Northern Ireland)" are automatically created or updated with their correct system codes, "XI" and "XU" respectively.

### Related Topics

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

[Previewing an Account During Creation](PreviewinganAccountDuringCreation.htm)