ACES Country Context Assignment for Unchanged Data

What is ACES Country Context Assignment for Unchanged Data?
For companies planning to rollout to new countries, it necessitates that the existing data reflects the new country. However, due to the prevailing logic of calculating net changes only when a change happens to a catalog, existing data could not be updated based on the context assignment logic. This feature removes that dependency; wherein even if there is no change to the catalog, the system will assign the country context to the existing data.

This feature handles all the following use-cases:

• Vendor loading a completely unchanged ACES file during the second load.
• Vendor loading an ACES file with some changes to header elements during the second load.
• Vendor loading an ACES file with new/changed/dropped Applications during the second load.

Context Assignment for Unchanged Data via XML Upload (Second Load)

The context-assignment for unchanged or changed catalog data is depicted in the following scenarios:

• Scenario 1: Assign country-context(s) to changed catalogs

• Scenario 2: Assign country-context(s) to unchanged catalogs

Scenario 1: Assign country-context(s) to changed catalogs

Let us consider the catalog 'Beckmann Technologies Windshield Washer Pump Repair Kit' existing in the system did not have the country-context assigned. Later the catalog has new application added and is uploaded again.
Existing Catalog without Context:

Updated ACES XML File with added applications and the country-contexts configured:

Result: After uploading XML file (second load), the system will override the Catalog and all its Applications (new or existing) with the derived country-contexts, based on the matched countries in the file (from the attributes Parts Approved For) and the information in the Authorized Catalog table for a given Vendor-Brand-Part Type combination:

The following table depicts the mapping of attribute values between ACES XML file and Authorized Catalog table:

• Considering the Context US, CA and MX were available in Authorized Catalog Table, the overriden catalog looks like:
  
• The attribute value for Is Part Type Authorized is updated with the value FALSE (indicates unauthorized part type) by the system. The Content Specialist can approve the part type as authorized (via workflow).
  

Scenario 2: Assign country-context(s) to unchanged Catalogs (nothing is modified in the catalog, but has the context updated as US)

Let us consider that the catalog 'JH Flask Drum Brake Shoe C Washer' was existing in the system, and the ACES XML file for the same was reloaded without any other changes in the file except the Parts Approved For now specified and the country-context US being configured:

Result: After uploading the XML file, the system performs the following actions:

• The system overrides the existing Catalog and assigns the country-context US if it is available in Authorized Catalog table for a specific Vendor-Brand-Part Type combination.

• The attribute value for Is Part Type Authorized is updated with the value FALSE (indicates unauthorized part type) by the system. The Content Specialist can approve the part type as authorized (via workflow).
  

  For more information on how to upload ACES XML file, see Quickstart for Uploading ACES Data.

Authorized Catalog Table

This table matches the details with the ACES XML file and decides to create a country-context. Based on the inputs available from ACES XML file, with the combinations Vendor ID, Brand ID and Part Teminology ID, the Authorized Catalog table helps you to identify the Catalog, Application groups and/or Applications, for which county-context must be assigned upon second load.

Generic Depiction: The following image depicts the Authorized Catalog table, where required country-context(s) are specified in the Authorized Countries column with particular Vendor-Brand-Part Type combination.