Working with inherited addresses

Network Address Inheritance automatically applies the address of a parent HCO to its child HCP or HCO record as a locally managed address.

Supported records

Address inheritance is supported on locally owned HCP, HCO, and parent HCO records.

The inherited address is created as a locally managed address on the child HCP or HCO.

Example

HCP	Parent HCO relationship	HCO	HCP copied address	Result
OpenData / Third Party	OpenData / Third Party	OpenData / Third Party	NA	Address inheritance is not applied when all records are managed by Veeva OpenData or Third Party sources.
OpenData / Third Party	Gray	Gray	Gray	Address is inherited as local data.
Gray	Gray	Gray	Gray	Address is inherited as local data.
Gray	Gray	OpenData / Third Party	Gray	Address is inherited as local data.

Records not supported

Address inheritance is skipped when all involved records are managed by OpenData or a third party data source.

Inherited address updates

When the parent address is updated, the changes are passed down to the address on the child record.

Addresses are updated through the following actions:

• after processing a data change request
• during a data load
• after running the address inheritance refresh job

The following behaviors apply for updates to each specific entity.

HCO updates

• If an HCO address changes, the copied address on the HCP is updated when the HCP record is changed or during an address Refresh Job.
• If an HCO address status is inactive, the copied address status is updated to inactive during the address Refresh Job.

HCP updates

• If an HCP address changes on any of the configured synced fields, the address will no longer sync with its corresponding HCO’s address.

Parent HCO updates

• If a parent HCO relationship changes, the inherited address configuration re-runs to determine whether the copied address should be disqualified.
• If a parent HCO status is inactive but has other active relationships to the same HCO, the HCPs copied address status is not updated.

Address fields

When address inheritance is applied, fields are copied from the parent HCO address to create the inherited address on the child HCP or HCO record.

Copied fields

The following fields are copied by default.

• address_line_1__v
• address_status__v
• address_type__v (not used when the country is China)
• address_verification_status__v
• administrative_area__v
• country__v
• locality__v
• premise__v
• postal_code_primary__v
• postal_code__v
• thoroughfare__v

Custom fields

Administrators can add custom fields in the address inheritance configuration.

Custom primary address fields are not available in the configuration.

Address ordinals

Address ordinals are not inherited from a parent address.

View inherited addresses

On the child HCP or HCO record profile, inherited addresses can be identified on the address summary card.

The summary card displays "Inherited from <Parent HCO corporate name>". Click the parent HCO name to scroll to the affiliation card on the profile page.

The Synced badge displays the inheritance status.

• Synced - The address is copied from a parent address.

• Unsynced - The copied address has been changed and is no longer linked to a parent address.

• Disqualified - The previously synced address no longer exists.

Hover over the badge to view information about the parent HCO that the address was copied from.

Expanded address data

Click the summary card to display the address details.

Fields that are inherited from the parent address display the Synced icon.

Unsynced addresses

When changes are made to addresses, inherited address can become unsynced or disqualified from the parent address.

Events that unsync addresses

• Manual updates to the inherited address on the profile page

  Users can manually change the inherited address fields. For details, see Edit inherited addresses.

• Data loads

  Inherited addresses can be changed through a data load.

• Data change requests

  Data Stewards can processes changes submitted for inherited addresses or manually edit the address on change requests.

Events that disqualify addresses

• Changes in the Network Address Inheritance configuration

  If the configuration is updated and an address no longer applies, it will be disqualified. For example, if the configuration is changed to update Professional addresses only, Mail Only addresses will be disqualified.

• Parent address is inactivated

  Inherited addresses are disqualified if the parent address is no longer active.

• Veeva OpenData merges addresses

  When addresses are merged by OpenData, an existing unsynced address in your local instance can remain unsynced. This usually happens if changes are made to a copied OpenData address, causing it to become unsynced from its HCO. If OpenData then merges that address into a winning address, the copied address will remain unsynced when you receive the updates from OpenData because the parent address is now a Merged_Into address and cannot be re-synced.

  For details, see Merged addresses from OpenData.

Resync addresses

Addresses that are unsynced can be re-synced using the following methods:

• Manually re-sync the inherited address on the Profile page.

  When the Profile page is in Edit mode, hover over the Unsynced icon on the inherited address and click the Re-Sync button that displays.

  

• Run the Refresh Job Schedule in the Network Address Inheritance configuration.

  The identifies and syncs out-of-sync addresses with their parent address. It will update the inherited address if the parent address has been updated more recently than the child address.

  For details, see Refreshing inherited addresses.

• Load data through a source subscription.

  Set the value of the parent_address_sync__v field to R in the imported file. If the address meets the criteria, the field value will be updated from R to S.

  For details, see Link addresses by loading data.