QualityOne Vaults enable you to improve the accuracy of CoA file ingestion by defining COA Matching Rules to extract data associated with critical fields. As users work with CoA files for inspection, some files may use slightly different terminology to describe the same fields and values from your organization. While analyzing a file prompts Vault to extract fields and values, Vault may not recognize some terms and language to populate field values in the Inspection Sample Test Result section accurately. To increase the accuracy of field value ingestion, you must define COA Matching Rule records to guide Vault to match specific key COA Matching Field values to the extracted analysis results for Inspection Sample Test Results.

You can define a COA Matching Rule record for the header or table section of the file by including the key field value that your organization utilizes and the data type expected from the extracted analysis result. You must also define the required variant texts for each matching rule. You can also define matching rules and variants for header values in a CoA file that may not have an accompanying key field. After configuring COA Matching Rule records, you must create COA Matching Rule Variant records for each matching rule to ensure that Vault will accurately match various alternate terms to the applicable matching rule.

The accuracy of CoA file ingestion is essential to extract the correct data needed when analyzing different CoA formats provided by your suppliers. If you don’t configure CoA matching rules, Vault maps only exact matches for header information and table column values from the CoA file to fields in your Vault.

Matching Rule Types

There are three types of matching rules:

  • Header Key: Used to match key standard fields found in the document information section of a CoA file to extract the value associated with the key field. For example, you can configure “Customer” as a matching rule variant of the “Supplier Name” matching rule. The header keys are standard fields defined in the COA Header OCR Data object, such as Supplier Name. You can additionally define up to three supplemental header key fields to help Vault extract information from a CoA file that may not be available as standard Header Keys, such as material. These fields are standard fields on the COA Header OCR Data object defined as Supplemental Field 1, Supplemental Field 2, and Supplemental Field 3. If configured by your Admin, creating matching rules and variants for supplemental header key fields can help Vault identify the Inspection Plan for an Inspection if none is provided.
  • Header Value: Used to match header values that may not have an associated header key field. Vault searches the entire CoA file, not only the header area, for configured header values. For example, you can configure the expected material description value from a certain supplier as a variant of the header value matching rule for the material description. The header values are associated with standard fields defined in the COA Header OCR Data object as Supplemental Field 1, Supplemental Field 2, and Supplemental Field 3. You can define header values for any Header Key fields. You can create up to ten variants for header values, so they should be generic enough to apply to all CoA files in your Vault. If a header key and header value COA Matching Rule exists for the same supplemental field, we recommend that both matching rules are configured to locate the same content on the document.
  • Table Column: Used to match key standard fields found in the column header of a CoA file to extract the values associated with the key field. For example, you can configure “Test” as a matching rule variant of the “Characteristic” matching rule. The table column keys are standard fields defined in the COA Test Results OCR Data object, such as Characteristic.

Sample CoA File

CoA Matching Fields

For each Matching Rule Type, there are key standard fields that Vault uses to match with:

  • For Header Key:
    • Item Code (item_code__v)
    • Item Name (item_name__v)
    • Purchase Order (purchase_order__v)
    • Purchase Order Line Item (purchase_order_line_item__v)
    • Supplemental Field 1 (supplemental_field_1__v)
    • Supplemental Field 2 (supplemental_field_2__v)
    • Supplemental Field 3 (supplemental_field_3__v)
    • Supplier Date of Manufacture (supplier_date_of_manufacture__v)
    • Supplier Expire Date (supplier_expire_date__v)
    • Supplier Item Code (supplier_item_code__v)
    • Supplier Manufacturing Lot Code (supplier_manufacturing_lot_code__v)
    • Supplier Manufacturing Site Address (supplier_mfg_site_address__v)
    • Supplier Manufacturing Site Name (supplier_manufacturing_site_name__v)
    • Supplier Name (supplier_name__v)
  • For Header Value:
    • Item Code (item_code__v)
    • Item Name (item_name__v)
    • Purchase Order (purchase_order__v)
    • Purchase Order Line Item (purchase_order_line_item__v)
    • Supplemental Field 1 (supplemental_field_1__v)
    • Supplemental Field 2 (supplemental_field_2__v)
    • Supplemental Field 3 (supplemental_field_3__v)
    • Supplier Date of Manufacture (supplier_date_of_manufacture__v)
    • Supplier Expire Date (supplier_expire_date__v)
    • Supplier Item Code (supplier_item_code__v)
    • Supplier Manufacturing Lot Code (supplier_manufacturing_lot_code__v)
    • Supplier Manufacturing Site Address (supplier_mfg_site_address__v)
    • Supplier Manufacturing Site Name (supplier_manufacturing_site_name__v)
    • Supplier Name (supplier_name__v)
  • For Table Column:
    • Characteristic (characteristic__v)
    • Max (max__v)
    • Min (min__v)
    • Specification (specification__v)
    • Test Method (test_method__v)
    • Test Result (test_result__v)
    • UoM (unit_of_measure__v)

Configuring CoA Matching Rules

After creating the COA Matching Rule records, ensure you create the appropriate COA Matching Rule Variants as needed for each matching rule.

To configure CoA matching rules:

  1. Navigate to Business Admin > Objects > COA Matching Rules.
  2. Click Create.
  3. Optional: Enter a description for the matching rule.
  4. Select a Matching Rule Type.
  5. Select a COA Matching Field. This is the key standard field Vault uses to match with, such as Supplier Name (supplier_name__v).
  6. Optional: Select a Data Type. This defines the format of value that Vault expects from the Expected Value Format field in the COA Matching Rule Variant records. The Expected Value Format field does not require a format if you leave this field blank.
    • If you choose Date, ensure you define a valid date format in the Expected Value Format field. If you do not define the Expected Value Format, Vault makes a “best guess” based on commonly used date formats.
    • If you choose Text, you may use a Regex format defined in the Expected Value Format field.
    • If the COA Matching Rule Type is Header Value, selecting Date is not supported.
  7. Click Save. To create another matching rule, click Save + Create.

Configuring COA Matching Rule Variants

After configuring the required CoA matching rules, you must create CoA matching rule variants to define various alternate terms for each matching rule to improve the accuracy of field value ingestion. See Configuring CoA Matching Rule Variants for more details.

Limitations

The following limitations apply to CoA matching rules:

  • You cannot update the Matching Rule Type on a COA Matching Rule if the matching rule has any active Matching Rule Variants.
  • Header Value type COA Matching Rules cannot have a Data Type of Date.