Custom VCdb, also referred to as Custom Vehicle Tables, allows you to create and manage custom vehicle data in PDM. This is useful when you need to add vehicles or configurations that are not available in the standard Auto Care VCdb.
Before adding or changing custom vehicle data, confirm that the vehicle or configuration does not already exist in the Auocare VCdb. If the vehicle exists there, use the standard vehicle data instead of creating a custom version.
Because Custom VCdb affects application data, it should be used carefully. Incorrect or unnecessary custom vehicle records can create duplicate data, invalid application combinations, or confusion when importing, exporting, and validating application records.
When to use Custom VCdb
Use Custom VCdb when the Autocare VCdb does not contain the vehicle or configuration you need.
Common examples include:
Vehicles not officially sold in the USA
Regional vehicle variations
Custom configurations that are not available in Autocare VCdb
Vehicle combinations needed for internal cataloging or customer-specific data
Custom VCdb should not be used to replace Autocare VCdb data when the correct vehicle already exists.
When not to use Custom VCdb
Custom VCdb should not be used as a replacement for Autocare VCdb data.
Avoid using Custom VCdb when:
The vehicle already exists in Autocare VCdb
The issue is caused by an incorrect application setup
The issue can be resolved by selecting a different standard Make, Model, Year, Submodel, Region, or configuration
The custom record would duplicate an existing standard VCdb record
Best practices for using Custom VCdb
Check the standard VCdb first: Before creating a custom vehicle, confirm that the vehicle or configuration does not already exist in the standard Autocare VCdb.
Avoid creating duplicate custom vehicles: Do not create multiple custom vehicle IDs for the same vehicle combination. Duplicate custom vehicles can make it difficult to manage applications and may lead to inconsistent data.
Use clear and consistent values: Make sure values such as Make, Model, Submodel, and Region are entered consistently. For example, avoid creating separate values that mean the same thing, such as using different spelling, spacing, or abbreviations for the same vehicle name.
Be careful when changing an existing custom vehicle ID: it can affect application records that already use that vehicle. Review the impact before making changes.
Test before making large changes: If you are new to Custom VCdb, create a small test scenario first. This can help you understand how custom vehicles are created, selected, and used in the Applications segment before making larger updates.