CRM Managed Account Types

Customers in different regions or countries have the flexibility to enable different DCR modes based on Account record types. Customers may define different DCR modes for certain types of accounts in certain countries to achieve more flexibility.

In some regions, certain types of accounts may not need to be DCR enabled. For example, Patient can be a type of Account that does not need to be DCR controlled. For compliance reasons, when an end user creates or edits the account, the account should be created/edited directly in CRM without creating any DCRs.

To enable this feature:

  1. Grant users Create permission on the Account, Child Account, and the Address objects to create the necessary Account record types.
  2. Enable the CRM_MANAGED_ACCOUNT_TYPES Network Setting that points to the corresponding Veeva Message with a list of the Developer Names of account record types and countries in the following format:

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

    For example, assume a CRM org is a multiple country org for Switzerland (CH), French (FR), Italy (IT) and Germany (DE)

    Patient_vod:ALL;;Nurse_vod:IT,DE

    This means reps can create or edit an account record type of Patient_vod without generating DCRs in all countries, and Nurse_vod account type in Italy and Germany.

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

When a user creates or edits an Account with the record type in the Veeva Message, the system checks the user’s country code (the 2 letter ISO country code on User object). If it matches the country code in the message, the setting is respected and no DCR is generated.

Third-Party Managed Account Types

In some cases, certain types of accounts in CRM are managed by 3rd party data providers other than Veeva Network, and it may not be legal for CRM to send DCRs to Veeva Network. Now customers can configure the system so a DCR is created for the 3rd party data provider, but not transmitted to Veeva Network.

To use this feature, enable the THIRD_PARTY_MANAGED_ACCOUNT_TYPES Network Setting that points to the corresponding Veeva Message with a list of Account record types and countries in the following format:

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

For example:

Pharmacy_vod:FR;; Laboratory_vod:ALL

This means when reps create or edit an account with the record type of Pharmacy_vod in France, a DCR is created, but it is not sent to Veeva Network. When reps create or edit a Laboratory_vod account type in all countries, the system creates a DCR, but does not send it to the Veeva Network.

Customers need to use custom processing to route the DCRs to 3rd party data provider to process.

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 3rd party. When users create a child account managed locally in CRM that links to the HCO, a DCR is not created.
  • The HCO parent account data is managed by a 3rd 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 record type is included in both the CRM_MANAGED_ACCOUNT_TYPES and THIRD_PARTY_MANAGED_ACCOUNT_TYPES for the same countries, 3rd party managed account types are always respected.

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