Reference data is a list of values which are not directly used by the application, but can be used by other interfacing applications. Reference data is used to manage the entire vehicle, configuration, engine, transmission, and so on.
Populate target attributes based on Reference table
Whenever a new entity is created, the system triggers the new Governance Rules which are part of the ACES app, which validates the imported attributes against the Reference Tables and auto-populates the target attributes which helps to improve the system performance.
Scenario 1
Consider a scenario where vendor imports the Catalog record with Brand AAIAD "BCVC", and PartType Id "14566" into the system. Whenever a Catalog is created, the system triggers the Business Rule, which validates the Brand, PartType, and Vendor ownership Id values against the AZ Category reference table (database).
Result: If the Brand, PartType, and Vendor ownership Id value match with the table, the system populates the AZ Category, AZ Subcategory, and AZ Team attribute values for the imported catalog and their respective Application groups. You can view the populated attribute values at the Catalog and Application Group level, which improves the system performance.
Scenario 2
Consider a scenario where the vendor imports the Catalog record with Brand AAIAD "BCVC", and PartType Id "14566" into the system. Whenever a Catalog is created, the system triggers the business rule which validates the Brand, PartType, and Vendor ownership Id combination against Authorize Catalog reference table.
Result: If any of the combination matches, the system auto-populates the Is Catalog Pre Approved attribute value to True. You can view the attribute value at the respective Catalog level.
Scenario 3
Consider a scenario where the vendor has previously imported the Catalog with 3 Application records into the system. When the same Catalog is imported with 2 Application records, the 2 Application records are created in the system. In this scenario, the previously imported Application records are dropped.
Whenever the Net Change status of the "Application" is Dropped, then the system triggers the business rule which validates the Net Change Status based on AZ Net Change Status reference table.
Result: If the Net Change Status value is "Dropped", the system populates the Drop Application attribute value to "True". You can view the populated attribute value at the Application level. For more information, see Application Drop Management.
Scenario 4
Consider a scenario, where the vendor imports the Catalog and Application records with Part Type Id "54116" into the system. Whenever a Catalog and related Applications are created, the system triggers the business rule, which validates the PartType against Auto Parts Classification and Parts Relationship reference tables.
- ACES Parts Classification reference table: The system validates the Part Type (Part Terminology ID) against the Auto Parts Classification reference table. If the Part Type is available in the reference table, then the system auto-populates the ACES Parts Classification attribute value with the 'Part Classification' column value.
- Parts Relationship reference table: The system validates the Part Type (Part Terminology ID) against the Parts Relationship reference table. If the Part Type is available in the reference table, then the system auto-populates the Related PIES Parts Classification attribute value with the 'Related Parts Classification' column value.
Result: You can view the auto-populated attribute values at the Application level.
If the 'Part Type or Part Terminology ID' is not available in the Parts Classification reference table, then the system copies ACES Parts Classification and populates the same value for the Related PIES Parts Classification attribute.