Settings That Depend on Data Origins

The following Customizing settings can be defined dependent on data origins. If you do not specify a data origin, the default settings are used.

Assign Mapping Instructions to Data Origin

Mapping instructions define how attributes are imported, converted, and exported before and after harmonization.

If you want to differentiate between the related conversions, you can assign mapping instructions to specific data origins. For each data origin, you can use only one mapping instruction, but you can assign one mapping instruction to multiple data origins.

For more information, see Customizing under Cross-Application Components Demand Data Foundation Data Harmonization Technical Settings Define Object Types .

Set Up Data Harmonization per Object Type

For each data origin you can define how harmonization is performed using the following settings:

You define whether the system automatically harmonizes data provided by the selected data origin at all.
You define whether the system automatically creates new harmonized objects for all objects that cannot be mapped to an existing harmonized object.
You define whether all automatic assignments of source objects to harmonized objects need manual approval.
You define in which sequence the harmonization functions are performed.

For the harmonization of attribute values you make the following settings dependent on data origins:

You prioritize data origins (general).

For example, you can prioritize data origins depending on the data quality. If attribute values are provided by multiple data origins, the value with the highest priority is copied to the harmonized object during automatic harmonization. If at a later point in time a value is provided by a data origin with the same or an even higher priority, the attribute value of the harmonized object is overwritten.
You prioritize data origins for specific attributes.

You can define various data origin priorities for each attribute. If you do not define a priority for a data origin of an attribute, the system uses the general priority of the data origin or the default priority respectively.
You define in which cases the system creates a work item for manual approval of attribute changes whenever the value of a specified attribute of a harmonized object is changed.

For more information, see Customizing under Cross-Application Components Demand Data Foundation Data Harmonization Set Up Data Harmonization per Object Type .

Make Attribute-Specific Settings: Attribute Sets

An attribute set defines which attributes are displayed on the user interface. For example, you can use different attribute sets for different product categories. For each object type you select one attribute that is used to select the relevant attribute set and assign the attribute sets to specific values.

If a data origin uses specific attribute values that are not covered with the standard values or if the same value means different things for different data origins, you can make this assignment dependent on the data origin.

Example Example

The attribute Product Category is defined as selecting attribute. You are working with product categories Food and Beverages.

You define different attribute sets FOOD and BEVERAGE with the relevant attributes and assign these attribute set to the product categories.

Data origin 1 uses the attribute value Liquids for the product category Beverages. You assign the attribute set BEVERAGE to the attribute value Liquids.

End of the example.

For more information, see Customizing under Cross-Application Components Demand Data Foundation Data Harmonization Technical Settings Make Attribute-Specific Settings Assign Sets to Attribute Values .

Make Attribute-Specific Settings: Descriptions for Attributes

In Customizing you can define for each data origin, how attributes are named in this area. If you choose a specific data origin in the user-specific parameters, all field labels are displayed using the description defined for this data origin (see User-Specific Parameters).