Specify the attributes to use for matching, and assign transformations to each attribute. Only active attribute and transformation combinations that you define in the Define Attributes and Transformations page can be used in the staged schema and in match rules.

You define attributes and transformations for each entity used in DQM: Party, Address, Contact, Contact Point. Attributes are transformed by their assigned transformations in the staged schema.

For address, contact, and contact point attributes, you can optionally denormalize the attribute to the party level. The transformed value would be stored in the HZ_STAGED_PARTIES table instead of the staging table for the entity. You should denormalize only attributes that have a limited number of possible values, such as the Country attribute. Denormalization improve performance, but you cannot denormalize all attributes.

Procedure

This table describes some terms in the pages used for this procedure.

Selected Terminology

1. Select an attribute name and enter a user-defined name. Search interfaces that use DQM generally display the user-defined names, not the attribute names, as the search criteria.

   If you are defining one of the 30 custom attributes, enter the name of the custom PL/SQL procedure that DQM uses to obtain the custom attribute. See: Creating Custom Attributes.

2. Indicate the uniqueness of the attribute with respect to other attributes for the entity.

3. To view or update the transformations assigned to an attribute, click Transformation Details for the appropriate attribute to display the transformations below.

   Note: You cannot remove attributes that are seeded for the entity or used in seeded match rules.

4. To assign a seeded transformation, just enter the transformation name. For custom transformations, you must also enter a description as well as the PL/SQL function that is called to transform the attribute values and to return a formatted result. See: Creating Custom Transformations.

5. Default: Specify if the transformation is also selected by default when the corresponding attribute is selected to be used in a new match rule. See: Assigning Scores, Transformations, and Thresholds.

6. Bulk Acquisition: Specify if the attribute and transformation combination can be used in acquisition for match rules with the Bulk Duplicate Identification purpose.

   Note: For performance reasons, select this option only when necessary.

   You cannot deselect Bulk Acquisition for transformations that are used, for acquisition, in seeded match rules of Bulk Duplicate Identification purpose.

7. Active: To use the transformation, you must activate the transformation for the selected attribute.

   You cannot inactivate seeded transformations if they are used in seeded match rules. You can, however, activate inactive transformations to use in custom match rules.

   Note: You cannot remove transformations that are seeded for the attribute or used in seeded match rules.

8. Use Up and Down to order the transformations. For example, the CLEANSE transformation alters the original attribute value more than EXACT does. You would order EXACT before CLEANSE because the transformed value is closer to the original and provides a more precise match.

   If multiple transactions have Default selected, then this order is reflected when the corresponding attribute is selected for new match rules with the Search purpose.

9. Before you can use new or updated attributes and transformations, you must generate or update your staged schema. See: DQM Staging Program.