Reference: Relationship mapping and crosswalk logic
This reference lists the mappings used to synchronize HCP–HCO and HCO–HCO relationships between Reltio and Veeva Vault CRM. It also highlights how crosswalks are used to manage record identity across systems.
Relationship field mappings
| Reltio URI | Reltio UI attribute value | Veeva Object | Veeva Vault field |
|---|---|---|---|
| configuration/relationTypes/OrganizationHierarchy/attributes/Status | _ | child_account__v | status__v |
| configuration/relationTypes/OrganizationHierarchy/attributes/HierType | _ | child_account__v | hierarchy_type__v |
| configuration/relationTypes/HCPisAffiliatedWithHCO/attributes/Department | _ | affiliation__v | therapeutic_area__v |
| configuration/relationTypes/HCPisAffiliatedWithHCO/attributes/AffiliationType | _ | affiliation__v | role__v |
| configuration/relationTypes/HCPisAffiliatedWithHCO/attributes/AffiliationStatus | _ | affiliation__v | status__v |
| configuration/relationTypes/HCPisAffiliatedWithHCO/attributes/IsPrimary | _ | affiliation__v | primary__v |
| configuration/relationTypes/HCOHasAddress/attributes/Primary | _ | address__v | primary_cda__v |
| configuration/relationTypes/HCOHasAddress/attributes/AddressType | Home | address__v | home_cda__v |
| configuration/relationTypes/HCOHasAddress/attributes/AddressType | Mailing | address__v | mailing__v |
| configuration/relationTypes/HCOHasAddress/attributes/AddressType | Shipping | address__v | shipping_cda__v |
| configuration/relationTypes/HCOHasAddress/attributes/AddressType | Business | address__v | business_cda__v |
| configuration/relationTypes/HCOHasAddress/attributes/AddressType | Billing | address__v | billing_cda__v |
| configuration/relationTypes/HCPHasAddress/attributes/Primary | _ | address__v | primary_cda__v |
| configuration/relationTypes/HCPHasAddress/attributes/AddressType | Home | address__v | home_cda__v |
| configuration/relationTypes/HCPHasAddress/attributes/AddressType | Mailing | address__v | mailing__v |
| configuration/relationTypes/HCPHasAddress/attributes/AddressType | Shipping | address__v | shipping_cda__v |
| configuration/relationTypes/HCPHasAddress/attributes/AddressType | Business | address__v | business_cda__v |
| configuration/relationTypes/HCPHasAddress/attributes/AddressType | Billing | address__v | billing_cda__v |
Crosswalk logic and ID handling
The following table outlines how crosswalks are used to maintain identity, track merges, and prevent duplicate records between Reltio and Veeva Vault CRM.
| Context | Behavior | |
|---|---|---|
| Merge handling (Reltio) | The _crosswalkTree API is used to identify winning and losing records. Vault records linked to the losing crosswalk are end-dated. | |
| Vault-to-Reltio identity | Veeva IDs (veevaid__v, veeva_network_id__v) are stored as part of Veeva Vault crosswalk value in the Reltio entity. | |
| Reltio-to-Vault identity | Vault ID is pushed to Reltio as a crosswalk after successful creation or DCR approval. | |
| Record linking | The following relationship types use crosswalks to define the linkage between related objects in Vault CRM. Each crosswalk value is constructed using Vault object IDs from the associated records: | |
| Relationship type | Crosswalk format | |
| HCPHasAddress | accountObjectId : addressObject Id | |
| HCOHasAddress | accountObjectId : addressObject Id | |
| HCP-HCO relationship | HCPAccountObjectID:HCOAccountObjectID | |
| HCO-HCO Affiliation | ParentHCOAccountObjectID:ChildHCOAccountObjectID | |
| Crosswalks are used to uniquely identify relationships in Vault CRM and prevent duplication during sync | ||