To configure this feature:

1. Ensure Configuring Accounts is complete.
2. Define the fields on the address__v object that should be copied from the parent business account address to the child business or person account address. This setting can be defined as a global setting or as a country-specific setting.

• As a global setting:
• Navigate to the Veeva Message acct_hier_addr_copy_fields
• Clone this message and activate it per standard Veeva configuration (for more information on activating Veeva Messages, see Managing Vault Messages and Veeva Messages)
• Designate the specific address__v fields to be copied for your organization. Enter the desired field names in a comma separated list. For example: id,name,city__v__c,address_line_2__v__c,state__v__c,zip__v__c

  Do not include the primary__v field in this setting.

• As a country-specific setting:
• Clone the acct_hier_addr_copy_fields Veeva Message and rename it to acct_hier_addr_copy_fields_[CountryCode]. For example, acct_hier_addr_copy_fields_[de] for Germany.

  The country code must match the two digit country code identifier from the country__v picklist on the address__v object.

• Designate the specific address__v fields to be copied for your organization. Enter the desired field names in a comma delimited list. For example: id,name,city__v__c,address_line_2__v__c,state__v__c,zip__v__c
• Ensure the country-specific Veeva Message is Active

When there is a country-specific Veeva Message, address inheritance copies the fields listed in the country-specific message instead of the global message.

3. Set child account address fields to read-only:

• To prevent child account addresses from changing repeatedly when changes are made further up the account hierarchy:
• Create an Object Type with the same API name as the Object Type in use by the parent business account address, then add _child as a suffix. For example, companymaintained_child
• Create Object Type-specific layouts limiting edit permissions for the desired fields on the address record. When child address records are created via Address Inheritance, the system looks for the _child Object Type value and applies the associated layout properties to the copied child address.

  If there are no _child Object Types, then the Object Type for the parent business account address is applied to the child account address.

4. Add the copy_address__v check box to child_account__v layouts, if users create parent-child account relationships using the Member Of related list on account records (optional). This gives users the option to manually enable address inheritance when creating child accounts.

• Alternatively, if address inheritance always applies to manually created accounts:
• Set the default value for the copy_address__v field on the child_account__v object to selected, eliminating the need to expose it in the layout

Preparing Account Data

Admins must first load account data, parent account addresses, and account hierarchy information into Vault CRM:

1. Load all parent business accounts into the system.
2. Load all child person accounts and business accounts into the system.

   Ensure the copy_address__v field is selected on all child_account__v records where address inheritance should apply.

3. Load addresses for all parent business accounts and, if applicable, any unique addresses for child business and person accounts into the system.
4. Load the child_account__v records linking parent business accounts with children business and person accounts into the system.

Copying Address Information to Child Accounts

To copy address information from parent to child accounts in bulk, admins can enable real time address push for asynchronous updates.

1. Configure the default value of the no_address_copy__v field on the address__v object to be deselected.
2. Enable the Enable Realtime Address Push Veeva Setting.

Real Time Address Push asynchronously updates child account address data whenever the parent account is modified. This allows administrators to process the account-level data changes.

Address Inheritance for Data Loaded Accounts

When address inheritance is enabled and a new account is created using Data Loader's web services API, the following occurs:

• All addresses from the selected parent business account are copied to the newly created child account record. If additional fields are not defined in the acct_hier_addr_copy_fields Veeva Message, then the following fields are copied to child account address records by default:
• name (address line 1)
• address_line_2__v
• city__v
• zip__v
• The controlled_address__v flag on the child account’s address record is selected, populating the controlling_address__v field with the parent address’s record ID
• The copy_address__v check box remains selected on the child_account__v record, ensuring any future updates to the parent address record are copied to the corresponding child account address records

Addresses are copied to child accounts based on the following conditions:

• The controlling_address__v’s ID on the child address matches the parent address’s record ID
• The controlled_address__v check box on the child address is selected

An account’s primary address cannot be inactive or have inactive child addresses. When marking the child of a primary parent address as inactive, admins must also remove the child address’s relationship to the primary address.

When a child account record is deleted, the address inheritance process deletes the controlled address from related Person Account records using the trigger veeva_child_account_address_clean on the child_account__v object.

Address Inheritance for Manually-Created Accounts

To manually create child account records, select the New Child Account action from the Member Of related list on a business account’s record.

If the copy_address__v field is on child_account__v layouts, select the copy_address__v check box to copy the parent account’s address information to the child account address.

All address processing occurs only online. Inherited addresses do not display for mobile device users until a subsequent sync and execution of the address batch process.

When users add a new parent account and select Save, and the parent account is the only parent for the child account, the new parent account is saved as the primary parent.

There may be some delay in copying the addresses depending on the number of records processed.

When address inheritance is enabled and a new primary parent account is assigned to a child account, the primary address copied over from the parent account is set as a primary address for a child account.

Overriding Address Inheritance when Data Loading Accounts

For organizations with managed data environments, admins can override address inheritance when importing records using the Data Loader. To override address inheritance and ensure a business address’s record is not copied to child records when data loading records:

1. Disable the Enable Realtime Address Push Veeva Setting.
2. Select the no_address_copy__v field on the address__v records for the desired business accounts.
3. Import the appropriate records.

Once the import is complete, the value in the no_address_copy__v field is cleared.

The no_address_copy__v field is strictly for administrative use. It should not be added to any layout. Since the field value is cleared after the record is imported, it could cause confusion for a user if exposed in the UI.