Qdb Validations

When you ingest an ACES XML with a qualifier, the application validates a qualifier ID and qualifier text of an application against the approved Qdb database. The qualifier are of two types:

Standard qualifier: In this type of qualifier, the text is fixed or static. For example, Air Conditioner.
Param-based qualifier: In this type of qualifier, the text is variable or dynamic. For example, Bumper width . Here, Bumper width can have multiple values, such as 60mm, 100mm, and so on.

If the qualifier ID and qualifier text is valid, then the application is created with the valid qualifier, else it gets rejected. The Qdb validation is available to the user for review with a valid error message under the "Task Details" section.

Valid Qualifier

A given qualifier ID in the ACES file is considered valid if:

It is found in the Qdb table.
The Qualifier has no value in NewQualifierID field.
The Qualifier text matches with Qualifier text in the Qdb table across all languages.

Note:

The Qdb Validation feature must be enabled to add a valid qualifier.

Scenario 1: Valid Standard qualifier

Consider an application is to be added that has a standard qualifier ID “20887” and qualifier text “Aftermarket”. The following is a sample ACES XML:

<App action="A" id="182" >
	<BaseVehicle id="7953"/>
	<Qual id="20887">
		<text> Aftermarket
            </text>
	</Qual>
	<!-- 2002 Suzuki Aerio -->
	<Qty>1</Qty>
	<PartType id="pcdbclass63651"/>
	<!-- Windshield Wiper Blade -->
	<Position id="104"/>
	<!-- Front Right Position -->
	<Part>18B</Part>
	<AssetName>IC_Hook1</AssetName>
</App>

The application validates the qualifier ID “20887” and the qualifier text “Aftermarket” in the Qdb across multiple locales. Upon validation, the application persists the data for the qualifier ID and qualifier text matching to the records in the Qdb tables for different locales.

Upon selecting the locales, the application displays the persisted text for all corresponding locales. A sample screenshot is displayed.

A sample screenshot of application created with Qualifier is displayed.

Scenario 2: Valid Param-based qualifier

Consider an application is to be added that has a param-based qualifier ID “931” and qualifier text “- x Screw”. The following is a sample ACES XML:

<App action="A" id="1" validate="No">
	<BaseVehicle id="648"/>
	<SubModel id="189"/>
	<Qual id="931">
		<text>
			<p1 type="size"/>-
			<p2 type="size"/> x 
			<p3 type="size"/> Screw
		</text>
	</Qual>
	<Qty>4</Qty>
	<PartType id="18411"/>
	<Part>JGS-2-911-N5345</Part>
</App>

The application validates the qualifier ID “931” and qualifier text “- x Screw” in the Qdb. Upon validation, the application persists the data for the qualifier ID and qualifier text matching to the records in the Qdb tables.

A sample screenshot of the persisted data is displayed.

You can view the parameter values in the Qualifier Attributes tab.

A sample screenshot of application created with Qualifier is displayed.

Invalid Qualifier

A given qualifier ID in the ACES file is considered invalid if:

It does not exist in the Qdb table.
The qualifier ID exists in the Qdb table but there is a value in the NewQualifierID field including “-1” that represents an administrative or technical errors.
The Qualifier text does not match with Qualifier text in Qdb table across all languages.

Scenario

Consider a scenario where an application is to be added that has a valid qualifier ID “1686” and invalid qualifier text “Directional Front Rotor”. The following XML contains:

<App action="A" id="1" validate="yes">
	<BaseVehicle id="648"/>
	<SubModel id="20"/>
	<Qual id="1686">
		<text>Directional Front Rotor</text>
	</Qual>
	<Qty>4</Qty>
	<PartType id="18411"/>
	<Part>JGS-2-911-N5345</Part>
</App>

Here, the qualifier ID matches with the Qdb database, however the Qualifier text does not match with the qualifier text in Qdb. As the qualifier is invalid, system rejects the Application with an error message. The App groups associated with it will also get rejected.

Task Completion Message:

Note:

If a given qualifier is received in different languages in the ACES XML file:

The application creates the Note entity only once for all instances of the qualifier being received across all locales.
The application creates applications independent of the qualifier text language.

Configure Qdb Validation

To enable the Qdb validation, you must configure the following.

File Details:

Download the following JSON file:
automotive-aces-validationconfig.json
Configure the following details:
In automotive-aces-validationconfig.json file > data.jsonData.autocarevalidations object, set the "enabled" parameter in “qdbvalidations{}” to true.

Upon successfully uploading the validation configuration for the respective tenant, the QDB Validation feature is enabled. For more information on how to upload, see Upload Tenant Seed Data, and login as a user with the appropriate credentials.

QDB Version Validations

When the ACES XML file is uploaded, it is checked for the supported Qdb versions. You must ensure to upload the XML files with relevant versions.

Upload_Aces_xml-QDB

Qualifiers in File Submission Report

The total number of qualifiers in the XML file is viewed in the file submission report as seen in the screenshot below:
The total number of Qdb errors are viewed as seen below:

Errored or Rejected Applications

The Errored or rejected applications due to invalid qualifiers can be viewed in the errored apps.csv (Example: file rejected_applications_130376-USA_20231023090534.csv) with Reason as “Invalid Qualifier ID per Qdb” in .csv
qdb-errored-application-csv

Qualifier for multiple languages

Upon import of ACES XML file, a qualifier in the xml file is validated with the AutoCare Qualifier table, based on the Qualifier ID. If the Qualifier ID is mapped to the required locale (in this scenario, we see that Qualifier ID is mapped to all the required locales en_US, es-MX and pt-BR), then the Application considers that Qualifier text for the mapped locales.

The following table depicts the sample Qualifier Text in multiple locale:
qualifier-autocare-database-table

Let us consider a Qualifier with ID “997”and qualifier text “1st Design Main Bearings”. The Qualifier table has the ID mapped to all the required locales. The system will consider the text with associated locales to be ingested.

<App action="A" id="1">
        <BaseVehicle id="1"/>
        <Qual id="997">
      <param value="5 1/2" uom="in" altvalue="31/2" altuom="cm">5 1/2in</param>
            <text> 1st Design Main Bearings            
            </text>
        </Qual>
        <!-- 2002 Suzuki Aerio -->
        <Qty>1</Qty>
        <PartType id="11223"/>
        <!-- Windshield Wiper Blade -->
        <Position id="104"/>
        <!-- Front Right -->
        <Part>18B</Part>
        <AssetName>IC_Hook1</AssetName>
    </App>

Result: The Qualifier text upon successful validation is considered for ingestion.

Task Completion Message:
task-completion-qualifier-ingestion