|
Data Quality Guide for Oracle Customer Hub > Administering Data Quality > Calling Data Matching and Data Cleansing from Scripts or Workflows >
Deduplication Business Service Methods
This topic describes the following Deduplication business service method: Value Match Method. Scenario for Data Matching Using the Value Match Method gives one example of how you can call the Deduplication business service Value Match method. NOTE: For information about other deduplication business service methods that are available, see Siebel Tools Online Help.
Value Match Method
You can use the Value Match method of the Deduplication business service to find potential matching records in the Siebel application or when you want to prevent duplicate data from getting into the Siebel application through non-UI data streams. For more information about business services and methods, see Siebel Developer's Reference. Arguments
The Value Match method consists of input and output arguments, some of which are property sets. Table 80 describes the input arguments, and Table 81 describes the output arguments. CAUTION: The Value Match method arguments are specialized. Do not configure these components.
Table 80. Value Match Method Input Arguments
|
|
|
|
|
Adapter Settings |
Property Set |
Threshold |
The threshold score for a duplicate record. A match is considered only if the score exceeds this value. |
Optional. The value Override can be specified to override the corresponding setting information obtained by the service from the administration screens, vendor properties, and so on. |
Match Values |
Property Set |
Business component field names, and value pairs: <Name1><Value1>, <Name2><Value2>, <Name3><Value3>, ... |
The matched business component's field name and the corresponding field value: (Last Name, 'Smith')
(First Name, 'John'),
and so on ...
NOTE: Each pair must be a child property set of Match Values.
|
These name-value pairs are used as the matched value rather than the current row ID of the matched business component. The vendor field mappings for the matched business component are used to map the business component field names to vendor field names. |
BC Name |
Property |
BC Name |
The name of the matched business component. |
Required. |
Update Modification Date |
Property |
Update Modification Date |
If set to N, the match modification date is not updated. |
Optional.
The default is Y. |
Use Result Table |
Property |
Use Result Table |
If set to N, matches are not added to the result table. Instead, matches are determined by the business service. |
Optional.
The default is Y. |
MultipleChild
EntitiesDedup |
Property |
Support Multiple Child Entities Dedup |
If the input argument is True, the data in the Match Values input argument is in a new data format. NOTE: To support the Multiple Child Entities Dedup feature, vendors must support hierarchical data format.
|
Required. |
NOTE: Adapter Settings and Match Values are child property sets of the input property set.
Return Value
For each match, a separate child property set called Match Info is returned in the output with properties specific to the match (such as Matchee Row ID and Score), as well as some general output parameters as shown in Table 81. CAUTION: The Value Match method arguments are specialized. Do not configure these components.
Table 81. Value Match Method Output Arguments
|
|
|
|
|
End Time |
Property |
End Time |
The run end time. |
None |
Match Info NOTE: Match Info is a child property set of the output property set.
|
Property Set |
Matchee Row ID |
The row ID of a matching record. |
If you match against existing records, the record ROW_IDs are found and returned in the Match Info property set. |
Score |
The score of a matching record. |
Num Results |
Property |
Num Results |
The number of actual matches. |
None |
Start Time |
Property |
Start Time |
The run start time. |
None |
Called From
Any means by which you can call business service methods, such as with Siebel eScript or from a workflow process. Example
The following is an example of using Siebel eScript to call the Value Match method. This script calls the Value Match method to look for duplicates of John Smith from the Contact business component and then returns matches, if any. After the script finishes, determine what you want to do with the duplicate records, that is, either merge or remove them. function Script_Open ()
{
TheApplication().TraceOff();
TheApplication().TraceOn("sdq.log", "Allocation", "All");
TheApplication().Trace("Start of Trace");
// Create the Input property set and a placeholder for the Output property set
var svcs;
var sInput, sOutput, sAdapter, sMatchValues;
var buscomp;
svcs = TheApplication().GetService("DeDuplication");
sInput = TheApplication().NewPropertySet();
sOutput = TheApplication().NewPropertySet();
sAdapter = TheApplication().NewPropertySet();
sMatchValues = TheApplication().NewPropertySet();
// Set Generic Settings input property parameters
sInput.SetProperty("BC Name", "Contact");
sInput.SetProperty("Use Result Table", "N");
sInput.SetType("Generic Settings");
// Set Match Values child input property parameters
sMatchValues.SetProperty("Last Name", "Smith");
sMatchValues.SetProperty("First Name", "John");
sMatchValues.SetType("Match Values");
sInput.AddChild(sMatchValues);
// Set Adapter Settings child input property parameters
sAdapter.SetProperty("Search Level", "Narrow");
sAdapter.SetProperty("Population", "Default");
sAdapter.SetType("Adapter Settings");
sInput.AddChild(sAdapter);
// Invoke the "Value Match" business service
TheApplication().Trace("Property set created, ready to call Match method");
svcs.InvokeMethod("Value Match", sInput, sOutput);
// Get the Output property set and its values
TheApplication().Trace("Value Match method invoked");
var propName = "";
var propVal = "";
propName = sOutput.GetFirstProperty();
while (propName != "")
{
propVal = sOutput.GetProperty(propName);
TheApplication().Trace(propName);
TheApplication().Trace(propVal);
propName = sOutput.GetNextProperty()
}
TheApplication().Trace("End Of Trace");
TheApplication().TraceOff();
}
| 
