The system validates applications having the same brand, part terminology, position, notes, or qualifiers with different part numbers and the VCdb attributes configuration, which are set at two different levels where one of the applications covers the more detailed one.
For example, consider multiple application records with the same brand, part, position, notes are imported into the system. The system sort Vehicle Identification and VCdb attributes as per the XSD and are grouped into specific patterns.
<App action="A" id="1">
<BaseVehicle id="6689"/> <!-- 2000 Nissan Frontier -->
<DriveType id="8"/> <!-- 4WD -->
<Note>w/ 0" Front Raised Height</Note>
<Qty>2</Qty>
<PartType id="7556"/> <!-- Shock Absorber -->
<Position id="22"/> <!-- Front -->
<MfrLabel>Rancho RS9000XL Shock Absorber</MfrLabel>
<Part>RS999188</Part>
</App>
<App action="A" id="2">
<BaseVehicle id="6689"/> <!-- 2000 Nissan Frontier -->
<BodyType id="22"/> <!-- Standard Cab Pickup -->
<Note>w/ 0" Front Raised Height</Note>
<Qty>2</Qty>
<PartType id="7556"/> <!-- Shock Absorber -->
<Position id="22"/> <!-- Front -->
<MfrLabel>Rancho RS9000XL Shock Absorber</MfrLabel>
<Part>RS999190</Part>
</App>
<App action="A" id="3">
<BaseVehicle id="6689"/> <!-- 2000 Nissan Frontier -->
<BodyType id="18"/> <!-- Extended Cab Pickup -->
<Note>w/ 0" Front Raised Height</Note>
<Qty>2</Qty>
<PartType id="7556"/> <!-- Shock Absorber -->
<Position id="22"/> <!-- Front -->
<MfrLabel>Rancho RS9000XL Shock Absorber</MfrLabel>
<Part>RS999195</Part>
</App>
The Overlap validations are performed by considering the following hierarchy or patterns:
- The attributes are grouped into specific patterns or hierarchies as per the XSD:
(1) BaseVehicle, (8) BodyType, and (9) DriveType, so VCdb Attributes should be sorted accordingly. The XML is converted to tabular format as follows:
| Attribute Pattern | App ID | PartType | Position | Part | BaseVehicle | DriveType | BodyType | Mfr. Label | Note |
|---|---|---|---|---|---|---|---|---|---|
| BaseVehicle, DriveType | 1 | 7556 | 22 | RS999188 | 6689 | 8 | Rancho RS9000XL Shock Absorber | w/ 0" Front Raised Height | |
| BaseVehicle, BodyType | 2 | 7556 | 22 | RS999190 | 6689 | 22 | Rancho RS9000XL Shock Absorber | ||
| w/ 0" Front Raised Height | |||||||||
| BaseVehicle, BodyType | 3 | 7556 | 22 | RS999195 | 6689 | 18 | Rancho RS9000XL Shock Absorber | w/ 0" Front Raised Height |
-
The system generates a set of applications (hereinafter called root) containing suspect overlapped records by taking BaseVehicle + Notes as a pivot and computing the following fields:
- Count of distinct notes - Application record with different notes. In this example, the distinct notes count is 1.
- Count of distinct part numbers - Application record with different part numbers. In this example, the part numbers are distinct from all the 3 application records. The distinct Part number is 3.
- Count of distinct attribute patterns. The application records having different attribute values are grouped. In this example, the Distinct Attribute value is 2 (DriveType, and BodyType).
A suspect overlap record is found when at least one of the above-computed fields is greater than 1.
| BaseVehicle | PartType | Position | Mfr. Label | Note | Count of distinct Notes | Count of distinct PN | Count of distinct attributes |
|---|---|---|---|---|---|---|---|
| 6689 | 7556 | 22 | Rancho RS9000XL Shock Absorber | w/ 0" Front Raised Height | 1 | 3 | 2 |
- The system identifies common attributes within the root to find different pivots by counting the number of applications where vehicle attributes are included.
| BaseVehicle | PartType | Position | Count of BaseVehicle | Count of DriveType | Count of BodyType |
|---|---|---|---|---|---|
| 6689 | 7556 | 22 | 3 | 1 | 2 |
In this case, the only common attribute within the ACES file is BaseVehicle, so the pivot remains as BaseVehicle + Notes. However, if the count of BodyType would have been the same as BaseVehicle, the
pivot would be integrated by BaseVehicle + BodyType + Notes.
- For each pivot found in the previous step (2), repeat step (3) replacing BaseVehicle with pivots found. The Catalog applications with no differences in the "Notes" and "Position" are considered as “Overlapped".