# Configuring CoA Component Matching Variants (QMS)

After <a href="/en/gr/63414/#define-ref-items">defining the global _Characteristics_ and _Units_</a>
, you must create CoA characteristic, unit, and organization matching variants to define various alternate terms and units of measurement to improve the accuracy of field value ingestion for <a href="/en/gr/69952/">CoA inspections</a>
.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: This feature is currently available only to Early Adopters. Contact your Veeva Representative for more details.</p>
    </div>
  </div>
</div>



## About Component Matching Variants {#variants}

CoA _Component Matching Variants_ informs Vault that there are similar terms (synonyms) that different languages, materials, suppliers, or supplier manufacturing sites use to define one (1) component. Matching the variants to its component helps to generate test results more accurately for each inspection plan requirement.

The _Component Matching Variant_ object has three (3) object types:

* **[Characteristic Matching Variant][1]**
* **[Unit Matching Variant][2]**
* **[Organization Matching Variant][3]**

### Component Matching Rules {#rules}

There are four (4) component matching rules you can use to define the logic to use to interpret data when creating a component matching variant:

* **Exact Match**: Used to map an exact value of a defined characteristic. Exact Match values are not case-sensitive.
* **Contains**: Used to map to a defined characteristic that comprises specific values.
* **Starts With**: Used to map to a defined characteristic that begins with specific values.
* **Ends With**: Used to map to a defined characteristic that concludes with specific values.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: In Vaults created prior to 22R1, the <em>Component Matching Rules</em> picklist may be labeled <em>Matching Type</em>.</p>
    </div>
  </div>
</div>



## Managing Characteristic Matching Variants {#character-mv}

You may need to create and manage characteristic matching variants to map synonymous supplier characteristics to the global <a href="/en/gr/63414/#define-ref-items">_Characteristic_ you defined</a>
.

For example, one (1) of your global _Characteristics_ for the _Material_ "Sugar" is "Moisture". Supplier A uses the synonymous characteristic "Water Content" and Supplier B uses "Water Cont. %". Knowing that both suppliers are implying "Moisture", you could create two (2) characteristic matching variant records to map "Water Content" and "Water Cont. %" to "Moisture".

### About Exact Match for Characteristics {#exact-match-char}

Vault can match exact variants from the CoA files to the global _Characteristic_ in a specific order. The following order is based on the following _Exact Match_ criteria for a particular _Characteristic_:

1. Exact match (inspection plan requirement) to the characteristic found.
2. If criteria 1 is not executed (no exact match is found), match variants where all four (4) fields are filled out: _Language_, _Material_, _Supplier Name_, and _Supplier Manufacturing Site_.
3. If criteria 2 is not executed, match variants where three (3) fields are filled out: _Language_, _Material_, and _Supplier Name_.
4. If criteria 3 is not executed, match variants where two (2) fields are filled out: _Language_ and _Material_.
5. If criteria 4 is not executed, match variants where one (1) field is filled out: _Language_.
6. If criteria 5 is not executed, match variants where no field is filled out and only the _Variant Text_ is found.

In the case where there are two (2) characteristic matching variants that meet the same criteria, the matching variant record is chosen randomly between the two (2) for the match. You must configure the <a href="/en/gr/69952/#coa-page-layouts">layout</a>
 for the _Characteristic_ and _Component Matching Variant_ objects to use this feature.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vaults using the legacy data model (prior to the 21R2 release) use the <em>Product Version</em> (<code class="language-plaintext highlighter-rouge">product_version__v</code>) field instead of the <em>Specific Product</em> (<code class="language-plaintext highlighter-rouge">specific_product__v</code>) field.</p>
    </div>
  </div>
</div>



### Configuring CoA Characteristic Matching Variant {#config-char-variant}

To configure CoA characteristic matching variants:

1. Navigate to the appropriate _Characteristics_.
2. Click **Create** in the _Component Matching Variants_ section.
3. Select **Characteristic Matching Variant** and click **Continue**.
4. Enter the **Variant Text**.
5. Optional: Select a **Component Matching Rule**.
6. Optional: Select a **Material**.
7. Optional: Select a **Supplier Name**.
8. Optional: Select a **Supplier Manufacturing Site Name**.
9.  Click **Save**. To create another characteristic matching variant, click **Save + Create**.

## Managing Unit Matching Variants {#unit-mv}

You may need to create and manage unit matching variants to map synonymous supplier units to the global <a href="/en/gr/63414/#define-ref-items">_Unit_ you defined</a>
. _Unit_ records can have duplicate names (in the _UoM_ field) as long as the _Type of Measurement_ picklist value is different.

For example, one (1) of your global _Unit_ for the _Material_ "Sugar" is "kilograms". Supplier A uses the synonymous unit "KG" and Supplier B uses "kilo". Knowing that both suppliers are implying "kilograms", you could create two (2) unit matching variant records to map "KG" and "kilo" to "kilograms".

### Configuring CoA Unit Matching Variant {#config-unit-variant}


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: As an alternative to manually creating variant records, we recommend using the <a href="/en/gr/824752/"><em>COA Ingestion Setup</em> panel</a>
 to guide you through the CoA variant setup process all in a single page.</p>
    </div>
  </div>
</div>



To configure CoA unit matching variants:

1. Navigate to the appropriate _Units_.
2. Click **Create** in the _Component Matching Variants_ section.
3. Select **Units Matching Variant** and click **Continue**.
4. Enter the **Variant Text**.
5. Optional: Select a **Component Matching Rule**.
6. Optional: Select a **Material**.
7. Optional: Select a **Supplier Name**.
8. Optional: Select a **Supplier Manufacturing Site Name**.
9. Click **Save**. To create another unit matching variant, click **Save + Create**.

## Managing Organization Matching Variants {#org-mv}

You may need to create and manage matching variants to map synonymous supplier organizations to the <a href="/en/gr/63414/#define-ref-items">_Organization_</a>
 you defined to improve the accuracy of address ingestion.

For example, one (1) of your _Organizations_ has different divisions that use different names to refer to themselves. Knowing that they are part of the same organization, you could create two (2) _Organization Matching Variants_ to map "CholeCap Intl" and "CC INTL" to "CholeCap International".

### About Organization Matching

Vault uses organization and address data to populate the following values on the _Inspection_ record when the _Analyze COA_ action runs:

* The _Supplier Manufacturing Site Address_ field, with the extracted address
* The _Supplier Site Fields Matched_ field, with the matched fields from the _Address_ associated with the _Organization_ in the _Supplier_ field of the _Inspection_ record

Vault matches the organization in a CoA file and extracts the address using the following guidelines:

* Vault searches for the _Supplier_ and _Supplier Manufacturing Site_ field values on the _Inspection_ record using _Organization Matching Variants_ associated with the _Organization_, if they exist.
* Vault prioritizes _Organization Matching Variants_ that match the _Inspection_ language. 
* If Vault finds multiple matches for an organization in a CoA file using _Organization Matching Variants_, Vault uses the address data associated with the organization to find the closest matching organization.
* Vault prioritizes <a href="/en/gr/76179/">_COA Matching Rule Variants_</a>
 configured for the _Supplier_ or _Supplier Manufacturing Site Address_ field before using _Organization Matching Variants_.
* Vault updates the values for _Supplier Manufacturing Site Address_ and _Supplier Site Fields Matched_ when users rerun the _Analyze COA_ action.

### Configuring CoA Organization Matching Variant {#config-org-variant}

To enable this matching strategy in your Vault, navigate to **Settings > Application Settings** and select the **Use OCR Data to Set Inspection Supplier Manufacturer Site Address** checkbox. You must also update the <a href="/en/gr/69952/#coa-page-layouts">layout</a>
 for the _Inspection_ and _Organization_ objects to ensure they include all relevant fields and related object sections.

#### Creating Organization Matching Variants

To create _Organization Matching Variant_ records:

1. Navigate to the appropriate _Organization_ record.
2. Click **Create** in the _Component Matching Variants_ section.
3. Enter the **Variant Text**.
4. Select a **Component Matching Rule**.
5. Click **Save**. To create another organization matching variant, click **Save + Create**.

[1]: #character-mv
[2]: #unit-mv
[3]: #org-mv