Show TOC

Setting Up Data Harmonization Locate this document in the navigation structure

 

You as an administrator for data harmonization review and adapt the relevant Customizing settings.

You find the Customizing activities for Data Harmonization under   Cross-Application Components   Demand Data Foundation   Data Harmonization  .

Caution Caution

If you change these settings in a running system that already contains harmonized data, this can lead to severe data inconsistencies!

End of the caution.

Process

The Customizing includes the following main activities:

  1. Define Object Types

    In this Customizing activity you make the following settings:

    • You define object types used in data harmonization and the relationships between these object types.

      Note Note

      If you want to use an additional object type besides Product and Location, create the object types with the dependent settings in Customizing and create the relevant Web user interfaces. To create your own object types, you require advanced knowledge in creating and using classes and interfaces.

      End of the note.
    • For each object type used in harmonization you define mapping instructions that specify how the object type is handled in data harmonization.

    For more information, see Customizing for Data Harmonization under   Technical Settings   Define Object Types  .

  2. Make Attribute-Specific Settings

    • You make settings regarding the appearance of attributes on the user interfaces:

      • For each object type, you can define attribute sets and groups that control which attributes are displayed on the user interfaces with which properties.

        Example Example

        You define different attribute sets for different product categories. For example, you hide attributes like Height or Length for liquid products. You use attribute groups, for example, to hide sensitive data for specific users.

        End of the example.
      • You can define attribute bundles for forms that collect related attributes under a heading. For example, you define an attribute bundle for administrative data.

    • You define which attributes are relevant for attribute value harmonization.

      You select the attributes that are considered during attribute value harmonization. You can define hierarchies of attributes that depend on each other.

      Values of attributes that have superordinate attributes are processed in accordance with the superordinate value in attribute value harmonization.

      Example Example

      The attribute BRAND depends on the superordinate attribute MANUFACTURER.

      End of the example.

    For more information, see Customizing for Data Harmonization under   Technical Settings   Make Attribute-Specific Settings  .

  3. Set Up Data Harmonization per Object Type

    The data provided by the data origins are of differing quality and contain varying levels of detail. Dependent on data origins you choose whether the following functions are processed during automatic data harmonization:

    • Automatic data harmonization

      Example Example

      For example, the data provided by a specific data origin contains objects that are not relevant for your purposes. For this data origin, you can disable automatic harmonization.

      End of the example.
    • Automatic creation of harmonized objects for unmapped source objects

    • Automatic assignment of source objects to harmonized objects only with approval

    • Harmonization of attribute values

    For more information, see Customizing for Data Harmonization under   Set Up Data Harmonization per Object Type  .