Inherit/link application data

Inherit/link application data

Details about inheriting application data

You can inherit application data among your products. This feature also works across all of your brands
  1. n-n relationships are possible (one parent product inherits to multiple children products / one children product can inherit from multiple parent products)
  2. You can combine application data that you manage individually on the child product level with application data that is inherited from a parent
  3. The ACES file includes all applications (regular and inherited)

Details about different data points:

Different data points have a different logic of how they are getting inherited

  1. PartType

    1. The Part Type is always assigned at least on the item level but can also be assigned in the "Applications" segment, specific to one application
      1. Part Type of parent product in "Items" segment: Will never be used. You need a part type in the "Items" segment of the child product or in the "Applications" segment of the parent product
      2. Part Type of parent product in "Applications" segment: The item-level part type of the child product will not overwrite the part type of the parent product
    2. (Note: If the parent product uses a position that is invalid for the part type of the child, that application will be excluded from an ACES file)

  1. Position

    1. The inheriting of the position depends on whether it is assigned on the parent level individually per SKU, as a default value or as a default value on the child level
    2. The position will be used in this order:
    3. 1. Default position on child level
    4. 2. Application specific position
    5. 3. Default position on parent level
    6. With this logic you are enabled to overwrite the parent position by assigning a default position on the child level
Position assigned on Parent Application Level
Position assigned on Parent Default Level
Position assigned on Child Default Level
Position that will be used
Child Default LevelChild Default LevelChild Default Level
Parent Application Level
The application record gets excluded from an ACES file if the selected position does not match the part type. Since you could have a position from the parent product getting inherited with a different part type on the child level, this may cause application records to get dropped.

  1. MfrLabel

    1. Default mfrLabel in the child product will overwrite parent product data
    2. The mfrLabel of the parent product will never be used

How to manage inherited application data

Inherited applications have a blue background and show at the top the part number they are inheriting from. You can there also unlink the connection.

It is not possible to have multiple layers of inheritance. Children products only inherit application records that are assigned to the parent directly.

    • Related Articles

    • Improving Application Data

      Partially Valid/Invalid Application Data PDM is constantly analyzing your product data for potential improvements. You can easily identify and fix the application data updates with the help of the color-coding feature.    Green indicates that the ...
    • Import/Export Parent/Child Application Data

      This article will focus on importing and exporting parent-child relationships in application data. For information on creating inheritance relationships for applications between products, see Inherit/Link application data. The parent/child ...
    • Import/Export Bundle Data

      Import/Export Bundle Data You can Import and Export data from the Bundle Feature right from the catalog. Export the Bundle Data In a Brand tab click All Products Select Application segment and select a parent product from the catalog Child ...
    • Application Segment - Add new Application

      Add new Application When adding a new application for a product, PDM will color code available Subconfigurations (i.e., sub-models) based on selected Make, Model, and Year / Year range. Select a Brand and click All Products. ...
    • Application Segment Overview

      Application Segment Overview In the Application segment, you provide information on vehicle fitments. Applications can be configured on multiple levels. Applications are defined in the following order : Year Make Model Sub configurations (Engine, ...