To configure this feature:

1. Grant end users Read and Edit permission to the account__v, child_account__v, and address__v objects to create the necessary account__v object types.
2. Ensure the appropriate values for the country_code__v picklist on the account__v object are made available to the necessary account__v object types.
3. Ensure the THIRD_PARTY_MANAGED_ACCOUNT_TYPES Network Setting is populated with the corresponding Veeva Message.
4. Populate the THIRD_PARTY_MANAGED_ACCOUNT_TYPES Veeva Message with a list of account__v object types and countries in the following format:

   <Account Object Type>:<Country Inclusion List>;;<<Account Object Type>:<Country Inclusion List>

   For example:

   pharmacy__v:FR;;laboratory__v:ALL;;

   This means when users create or edit pharmacy__v type accounts in France, a DCR is created, but is not sent to Veeva Network. When reps create or edit a laboratory__v type account type in all countries, a DCR is created, but is not sent to Veeva Network.

“ALL” is a reserved key word that needs to be specified if it should apply to all available countries.

When users create or edit an account with an object type and country listed in the THIRD_PARTY_MANAGED_ACCOUNT_TYPES Network Setting, a DCR is created but is not sent to the Veeva Network.

Customers need to use custom processing to route the DCRs to a third-party data provider.

For a child account, if either the parent or the child is included in THIRD_PARTY_MANAGED_ACCOUNT_TYPES, the user will create the child account without creating DCRs. For example:

• The HCO parent account data is managed by a third party. When users create a child account managed locally in Vault CRM that links to the HCO, a DCR is not created.
• The HCO parent account data is managed by a third party. When users create a child account managed by the Veeva Network that links to the HCO, a DCR is not created.

If an account__v object type is included in both the CRM_MANAGED_ACCOUNT_TYPES and THIRD_PARTY_MANAGED_ACCOUNT_TYPES for the same countries, third-party managed account types are always respected.

These two settings overwrite the user’s default DCR settings. For all object types/countries not included in the settings, the user’s default DCR setting is respected. The object type name, not the object type label, should be used in the settings.