Managing CDA fields

CDA fields can be managed by Veeva OpenData or they can be locally managed.

Veeva-managed fields are populated by Veeva OpenData. Locally managed fields are updated through data loads and change requests or they are populated using the CDA Sync process.

Quick reference

Field Management Type Method Used to Populate Fields
Veeva-managed All fields OpenData country subscriptions, ad hoc downloads
Locally managed Calculated fields CDA Sync process
Locally managed Non-Calculated fields Data loading, change requests (DCRs)

List of fields

For the complete list of HCP, HCO, and Address fields and their details, see CDA kernels.

OpenData-managed CDA fields

Most CDA fields are managed by Veeva OpenData for OpenData records.

OpenData field details

A list of the fields with high-level details is provided in the sections below.

Download the following files for more information about the fields:

Calculation of CDA Fields 25R3.1 February 19th 2026.xlsx

  • Field ownership

  • Field calculation rules for each country / region

Network CDA - Data dictionary 25R3 December 12th 2025.xlsx

  • List of entities, fields, and reference lists.

Populate CDA fields on OpenData records

Veeva-managed CDA field values will be pushed to your Network instance through your OpenData subscriptions or ad hoc downloads as usual.

Note: The CDA Sync setting does not need to be enabled in your Network instance to receive OpenData in these CDA fields.

To populate field values:

  1. Enable at least one CDA field in your Network instance.

  2. Run a full OpenData country subscription to update all records that are downloaded in your Network instance.

    1. Open an OpenData country subscription (System Interfaces > OpenData Subscriptions).

    2. In the Updates to OpenData records section, select Update all records.

    3. Save your changes.

The next time the subscription runs, you will receive updates for all the OpenData managed CDA fields that you have enabled.

Report on countries that need CDA field updates from OpenData

To identify which countries need to be updated, run a query to see the records that do not have the Veeva ID (veevaid__v) field populated.

HCP query

SELECT
        primary_country__v,
        COUNT (*)
    FROM
        hcp
    WHERE
        veevaid__v IS NULL
        AND record_owner_type__v = 'VOD'
    GROUP BY
        primary_country__v
    ORDER BY
        COUNT (*) DESC

HCO query

SELECT
        primary_country__v,
        COUNT (*)
    FROM
        hco
    WHERE
        veevaid__v IS NULL
        AND record_owner_type__v = 'VOD'
    GROUP BY
        primary_country__v
    ORDER BY
        COUNT (*) DESC

Example results

After running the HCP query, you can see that there are US and UK records that need to be updated.

On the UK and US OpenData subscription configuration, choose the Update all records setting.

The next time the subscription runs, all Veeva-managed CDA fields that are enabled in your Network instance will be populated on the records.

Locally managed CDA fields

Some CDA fields and their values are managed in your Network instance. These are custom fields, but they have the __v suffix.

Tip: Field labels can be added, edited, and removed for any language for these fields. If you customize a label, any changes that Veeva makes to the label will not overwrite your changes.

Populating locally managed fields

There are two types of local fields:

  • Calculated - Fields are read-only. The values are mapped to the legacy field values and are populated through the CDA Sync process.

  • Non-calculated - Updates can be made directly to the field through data loading and data change requests (DCRs).

Quick reference

Type Uses CDA Sync? Data Loading Behavior DCR Behavior
Calculated fields Yes Load data into the legacy fields using an import file.

CDA Sync populates the values to the mapped CDA fields.

Submit changes to CDA fields.

CDA Sync maps the values to the legacy fields for Data Stewards to process.

Non-Calculated fields No Load data into the CDA fields using an import file. Submit changes to CDA fields.

Details are available below.

Calculated fields

Some locally managed fields are calculated fields. This means that the field values are populated by the CDA Sync process in your Network instance.

Update calculated fields

CDA Sync automatically runs in your Network instance during data update jobs, for example, source subscriptions, data updater, DCRs, and merges.

The process calculates the CDA field values using internal country-based rules or by mapping the corresponding legacy field value.

Note: CDA Sync must be enabled so calculated fields values can be populated.

To update calculated fields:

  • Load data into the mapped legacy fields

    The CDA Sync process will map the legacy field values to the calculated CDA fields.

    Important: If calculated CDA fields are included in the import files, the data will be overwritten when CDA Sync runs.

  • Submit data change requests on calculated CDA fields

    The CDA Sync process will map the values to the legacy fields for Data Stewards to process.

For details, see CDA Sync and CDA DCRs.

Non-calculated fields

These fields are populated by updating the field directly through data loading or data change requests (the same way you update legacy fields).

  • Data loading - Include the non-calculated fields in the import files.

  • Change requests - Submit DCRs on the non-calculated fields.