This topic describes the extraction of applications for only the identified and operating regions.
For an organization that operates only in certain identified regions, the creation of vehicle applications based on YMM-submodel-region is supported only based on those identified regions.
Operating Regions Configuration:
The organization specific operating regions configuration must be configured for the regions that they are operating for. This will decide the creation of vehicle applications for the identified regions.
- This is a one-time configuration done by the organization and does not require any action from their vendors or other partners. The configuration is set up by our Customer Partner Success (CPS) team. For more information, reach out to our CPS team.
- The application supports vehicle data onboarding for both North America and Latin America regions.
- If region is not specified at individual application level, the application considers the Region For attribute mentioned in the ACES XML header.
- If region is not specified at individual application level and Region For attribute is also not specified in the ACES XML header, then the application considers the region specified in the App Config. It is recommended to mention the region in the XML at header level or at the app level. For more information on App configuration, see Configure Region for Explosion in App Config.
- You must specify either North America region or Latin America region in the header of ACES XML file. If specified for both the regions (Example: North America region as USA and Latin America region as Brazil), then the application displays an error message “Multiple AutoCare regional DBs (NA and LATAM) are not supported in a single file” (File Error). The same applies in the case of App Config.
- The region-specific application extraction is only based on the configuration file and not the ACES file
segments. That is, if any region is mentioned in the segment of ACES XML file which is not part of the configuration file, then the region found in ACES XML is not considered for extraction.
Example:
Let us consider an application with the Make Model - Nissan Sentra. If the application record is defined in Year Range, then the system will convert such application record to individual record keeping all other information same across applications.
Considering the extracted application Application 3 (Base Vehicle ID -118567),
The Vehicle IDs retrieved based on the Base Vehicle, Sub model (if provided) and Region (if provided) available in the application record, the system will explode the submitted application into individual Region/Sub-Model applications keeping all other information same across applications.
If the Region/SubModel is not provided, then the system will infer all possible values for that Base Vehicle Id from the VCdb Vehicle table.
As we observe, there are 16 Applications extracted for Nissan Sentra in the year 2012. Similarly, considering the applications extracted in the year 2010 and 2011 will depict the values as below:
| Base Vehicle ID | Year | Make | Model |
|---|---|---|---|
| 118567 | 2012 | Nissan | Sentra |
For the above Application record (from ACES), If the organization’s operating region is only United States, then as per the below table which represents all possible Applications with the Base Vehicle ID – 118567 (for United States); based on SubModel and Region - only the first 6 applications (representing the Region of United States) are created in the system.
Task Details
The regions identified for explosion (creation) is shown in the ACES Import task viewer as “Vehicle Regions considered for Application Extraction/Explosion: <<region names>>”.
Consider that you have identified (or configured) three regions (USA, Canada, and Mexico) for the creation of catalogs, application groups, and applications. The following figure displays an example notification message of the configured regions:
The following scenarios depicts the feature behavior considering various aspects.
Scenario 1
Scenario: Consider that an organization ORG is operating in region – USA. Applications will be created for USA region only.
Considering the region being operated by ORG is configured in the configuration file, the applications will be created for USA region.
To validate the entity creation for the organization - ORG that operates only in the USA region:
Importing ACES XML:
- Import the ACES XML file into the application. For more information on importing the ACES XML file, refer Quickstart for Uploading ACES Data.
Result: You can view the imported tasks in the Task Detail page.
- You can verify the creation of tasks in the Child Tasks tab.
Result: The created catalogs are displayed.
Validation:
-
Click Search and select Search Applications.
Result: The Automotive Domain Search page is displayed. -
Click on the created catalog.
Result: The Catalog Manage page is displayed. -
You can navigate to the applications via Entity Network tab > Entity Graph > Applications or Manage Catalog > Select Application Group > Manage Applications > Select Applications. Go to the required application.
Result: The Application Manage page is displayed.
The region of the created entity is displayed as USA. You have now successfully verified the creation of the entity for a specific region – USA.
Scenario 2
The application allows you to specify a region in the Region For attribute in the ACES XML header. If region is not specified at individual application level, the application considers the Region For attribute.
Consider that you are importing an ACES XML containing multiple applications - A1 and A2, and the Region For attribute in the XML header is set to Argentina. The application A1 has the region specified as Brazil, while application A2 does not have any region specified.
In the following sample XML snippet, application A1 has id “1” and application A2 has id “2”. Also, Argentina region has id “7” and Brazil region has id “6”:
<?xml version="1.0" encoding="UTF-8"?>
<ACES version="4.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Header>
<RegionFor>
<Region id="7"/>
</RegionFor>
</Header>
<App action="A" id="1">
<BaseVehicle id="31279"/>
<Region id="6"/>
</App>
<App action="A" id="2">
<BaseVehicle id="127805"/>
</App>
</ACES>
The following applies upon application extraction:
- A1 retains it individually specified region (Brazil).
- Since A2 does not have a region defined at the application level, it inherits the region specified in the XML header - Argentina.
A sample screenshot is as displayed:
