Data Validation

PIES database version validation

Once the PIES XML file is uploaded via UI, the system initiates the batch processing for the uploaded data. Once the launcher job verifies that the uploaded file adheres the PIES XML file standards, then the system checks whether the database version of the PIES XML file belongs to the latest PIES database version (supported versions).

If the version date of the PIES XML file lies within the past six months, then the launcher job collects the appropriate PCAdb database based on the identified version date and provides the same as the resource file to the PIES file processing job for further processing of the PIES XML file.

<?xml version="1.0" encoding="UTF-8"?>
<PIES xmlns="http://www.autocare.org">
    <Header>
        <PIESVersion>7.2</PIESVersion>
        <SubmissionType>FULL</SubmissionType>
        <BlanketEffectiveDate>2018-07-13</BlanketEffectiveDate>
        <ChangesSinceDate>2018-07-13</ChangesSinceDate>
        <ParentDUNSNumber>887254927341</ParentDUNSNumber>
        <ParentGLN>7324343587651</ParentGLN>
        <ParentVMRSID>GIANT</ParentVMRSID>
        <ParentAAIAID>BBCD</ParentAAIAID>
        <BrandOwnerDUNS>8343236745388</BrandOwnerDUNS>
        <BrandOwnerGLN>7757154423525</BrandOwnerGLN>
        <BrandOwnerVMRSID>WONDR</BrandOwnerVMRSID>
        <BuyerDuns>8885234356676</BuyerDuns>
        <CurrencyCode>USD</CurrencyCode>
        <LanguageCode>EN</LanguageCode>
        <TechnicalContact>Noe</TechnicalContact>
        <ContactEmail>noe.aguirre@AA.com</ContactEmail>
        <PCdbVersionDate>2017-12-18</PCdbVersionDate>
        <PAdbVersionDate>2017-12-18</PAdbVersionDate>--->PCdb version error
    </Header>
      <PriceSheets>...</PriceSheets>
    <Items>...</Items>
     <Trailer> 
     <ItemCount>1</ItemCount> 
     <TransactionDate>2007-04-25</TransactionDate> 
     </Trailer> 
</PIES> 

XSD validation

Once the PIES XML file is uploaded via UI, the system initiates the batch processing for the uploaded data. The system validates elements of Price sheet and Vendor Item entity in PIES XML file against the elements of XSD schema to validate each attribute elements defined in PIES XML file matches with the attributes of XSD schema.

Once the XSD schema validation is done, the dynamic attributes of Item entity such as Product attributes and Parts classification attributes, and the attributes of Price sheet entity defined in the PIES XML file entity gets automatically mapped to RDP DMD (Taxonomy Model) and populated in the UI.

Validate duplicate entities

When the vendors upload bulk entities such as Price Sheet, and Vendor Item via UI, the system validates the incoming records with the matching attribute of the respective entity. If any of the matching attributes are updated, new entities are created, else the system marks the entity as "Update" or "No Change" to improve the system performance.

Currently, when vendors or suppliers re-imports the same Price Sheet records by updating Matching attribute, the system validates the incoming Price Sheet attributes with matching attributes. If any of the matching attributes are updated, then the system create new entity.

Scenario

Consider that vendor has previously imported PIES XML file into the system. The vendor re-imports the same Price Sheet records by updating the matching attribute (Price Sheet Number).

<?xml version="1.0" encoding="UTF-8"?>
<PIES
		xmlns="http://www.autocare.org">
 <Header>
  <PIESVersion>7.2</PIESVersion>
 </Header>
    <PriceSheets>
        <PriceSheet MaintenanceType="A">
            <PriceSheetNumber>RSLLDR-2000</PriceSheetNumber> --------> Matching attribute
            <PriceSheetName>RSLLDR-2000</PriceSheetName> 
            <SupersededPriceSheetNumber>RSLLDR-1999</SupersededPriceSheetNumber>
            <CurrencyCode>EUR</CurrencyCode>
            <PriceZone>Western</PriceZone>
            <EffectiveDate>2020-08-14</EffectiveDate>
            <ExpirationDate>2020-08-14</ExpirationDate>
        </PriceSheet>
    </PriceSheets>

Result: The system creates new Price Sheet entity.

Similarly, when vendor re-imports Item records by updating matching attribute values (BrandId, SubBrandId, Vendorship Id, Part Number and Part Type), the system validates the incoming Item attributes with matching attributes. If the any of the matching attributes are updated, then the system create new Vendor Item entity.

<Items>
        <Item MaintenanceType="A">
            <HazardousMaterialCode>N</HazardousMaterialCode>
            <BaseItemID>RSLLDR-1912</BaseItemID>
            <ItemLevelGTIN GTINQualifier="UP">00842700103199</ItemLevelGTIN>
            <PartNumber>RSLLDR-1912</PartNumber> --------> Matching attribute
            <BrandAAIAID>JCTO</BrandAAIAID>  --------> Matching attribute
            <BrandLabel>CV4</BrandLabel>
            <SubBrandAAIAID>HJNO</SubBrandAAIAID> --------> Matching attribute
            <SubBrandLabel>Super Series</SubBrandLabel>
            <VMRSBrandID>FELPR</VMRSBrandID>
            <ACESApplications>Y</ACESApplications>
            <ItemQuantitySize UOM="EA">2</ItemQuantitySize>
            <ContainerType>PR</ContainerType>
            <QuantityPerApplication Qualifier="MAX" UOM="EA">8</QuantityPerApplication>
            <ItemEffectiveDate>2020-08-28</ItemEffectiveDate>
            <AvailableDate>2020-08-28</AvailableDate>
            <MinimumOrderQuantity UOM="EA">8</MinimumOrderQuantity>
            <ManufacturerProductCodes>
                <Group>W12</Group>
                <SubGroup>W123</SubGroup>
            </ManufacturerProductCodes>
            <AAIAProductCategoryCode>330102</AAIAProductCategoryCode>
            <UNSPSC>1176833429</UNSPSC>
            <PartTerminologyID>2476</PartTerminologyID> --------> Matching attribute
            <VMRSCode>129995789</VMRSCode>
    </Items>

Kits Entity Validation

To validate matching attributes in the kits entity type, include Brand AAIAID or Part Number in the kit segment of the PIES XML file.

- <Item MaintenanceType="C">
	<PartNumber>New050422</PartNumber>
	<BrandAAIAID>CLGS</BrandAAIAID>
	<SubBrandAAIAID>HTVZ</SubBrandAAIAID>
	<SubBrandLabel>Gold Class</SubBrandLabel>
	<PartTerminologyID>1684</PartTerminologyID>
- <Kits>
- <KitComponent MaintenanceType="A">
			<ComponentPartNumber>MT_kits05</ComponentPartNumber> ---------> Matching Attribute
			<ComponentBrand>CLGS</ComponentBrand>
			<ComponentBrandLabel>Acme -------> Matching Attribute Parts</ComponentBrandLabel>
			<ComponentSubBrand>HTVZ</ComponentSubBrand>
			<ComponentSubBrandLabel>Premium</ComponentSubBrandLabel>
			<Description LanguageCode="EN" DescriptionCode="DES">Oil Filter</Description>
			<QuantityInKit UOM="EA">2</QuantityInKit>
			<SequenceCode>2</SequenceCode>
			<SoldSeparately>Y</SoldSeparately>
		</KitComponent>
	</Kits>


- <PartInterchangeInfo>
- <PartInterchange MaintenanceType="A" QualityGradeLevel="O" BrandLabel="Chrysler" BrandAAIAID="CLGS">
<PartNumber>MT_partinterchange05</PartNumber>
		</PartInterchange>
	</PartInterchangeInfo>
</Item>

When a vendor imports kit Item records by updating matching attribute values such as Brand AAIAID or Part Number, the system validates the incoming item attributes with the matching attributes. If XSD validations are satisfied and any of the matching attributes are updated, then the system creates new kits entity.

Example of New kits entity created by the system.

• File Details: