Configuring Exact Match Functionality in Oracle Customer Hub (UCM)

You configure Oracle Customer Hub (UCM) exact match functionality by configuring user properties in the UCM Data Quality Manager business service. For information on configuring business service user properties using Siebel Tools, see Integration Platform Technologies: Siebel Enterprise Application Integration. Use the following task to configure exact match functionality.

To configure exact match functionality in Oracle Customer Hub (UCM)

  • Configure the following user properties for the UCM Data Quality Manager business service.

    User Property Value

    ExactMatch Object

    Name + “:" + IntObjName + “;"

    Name ExactMatch Field

    ICFieldName + “:" + BCFieldName + “;"

    where:

    • Name must be unique. It might be an integration object name, root component name, or supported objects, for example, account, contact.

    • IntObjName is the integration object name. Use it for querying by user key.

    • ICFieldName is the integration component field name.

    • BCFieldName is the business component field name. Use it for querying by example.

If a single field can uniquely identify a record, then it is recommended that you use only that field as the exact match field. However, you can specify multiple exact match fields, separated by a semicolon (;). The exact match functionality combines the exact match fields using the AND operator, and performs a single query for a matching record.

An object can appear in only one ExactMatch Object property. You can create one ExactMatch Object property that includes all supported objects, or you can create one ExactMatch Object property for each object. Append a number to each ExactMatch Object property, even if you create only one.

The following table shows an example of configuring the exact match functionality for the UCM Data Quality Manager business service. In this example, the first ExactMatch Object user property is for the contact object, and the exact match fields are First Name, Last Name, Email Address, and Home Phone #. The exact match functionality returns a matching record if the values in these fields in a single record in the database match the values in the same fields in an incoming record. The second ExactMatch Object user property is for the account object, and the exact match fields are Name and Location.

User Property Value

ExactMatch Object 1

Contact:CIFContactInsert;

Contact ExactMatch Field 1

First Name:First Name;Last Name:Last Name;Email Address:Email Address;Home Phone #:Home Phone #;

ExactMatch Object 2

Account:CIFAccountInsert;

Account ExactMatch Field 1

Name:Name;Location:Location;

You can create multiple Name ExactMatch Field properties for an object, and you can optionally append a number at the end of the user property names to distinguish them, for example, Contact ExactMatch Field 1, Contact ExactMatch Field 2, and so on. Each Name ExactMatch Field user property can contain a maximum of 250 characters. The exact match functionality concatenates all of the fields specified in all of the Name ExactMatch Field user properties for the object using the AND operator, and performs a single query for a matching record.

As an example, you might create two Name ExactMatch Field user properties for the contact object, as shown in the following table.

User Property Value

ExactMatch Object 1

Contact:CIFContactInsert;

Contact ExactMatch Field 1

Social Security Number:Social Security Number;

Contact ExactMatch Field 2

Birth Date:Birth Date;

The exact match functionality concatenates the fields specified in these two user properties, and returns a matching record if the values in the Social Security Number and Birth Date fields in a single record in the database match the values in the same fields in an incoming record.

Note: You cannot use Name ExactMatch Field user properties to specify alternative queries for an object. For example, you cannot configure the exact match functionality to search first for a matching record using the fields specified in Contact ExactMatch Field 1, and if no matching record is found, then perform a second search for a matching record using the fields specified in Contact ExactMatch Field 2.