Skip Navigation Links | |
Exit Print View | |
Working With the EDM for Oracle Java CAPS Master Index Java CAPS Documentation |
Working With the EDM for Oracle Java CAPS Master Index
About the Enterprise Data Manager
About Oracle Java CAPS Master Index (Repository)
About Master Index Applications (Repository)
Features of Master Index Applications (Repository)
Functions of the Enterprise Data Manager
Learning about EDM Object Profiles
Object Profile Indicators on the EDM
System Record and SBR Components in a Master Index (Repository)
Identification Numbers for each Entity in the Master Index (Repository)
Working with the Enterprise Data Manager
Logging in to the Enterprise Data Manager
Enterprise Data Manager Security Permissions
Enterprise Data Manager Navigation Tips
Navigating the EDM Search Pages
Navigating the EDM Detail Pages
Learning About Object Queries on the EDM
Searching by Ranges on the EDM
Searching for Object Profiles on the EDM
Performing an EUID Lookup on the EDM
Performing a Local ID Lookup on the EDM
Performing an Alphanumeric Search on the EDM
To Perform an Alphanumeric Search
Performing a Phonetic Search on the EDM
Performing a Blocker Search on the EDM
Performing an EUID Comparison Lookup on the EDM
To Perform an EUID Comparison Lookup
Working with Search Results on the EDM
Viewing the Results of a Search
Sorting the Results of Your Search
Selecting a Profile from the Results List
Creating and Printing a Search Result Report
Learning About Object Profile Views on the EDM
Object Profile Details on the EDM
Object Profile Comparisons on the EDM
Object Profile Transaction Histories on the EDM
Object Profile Merge Histories on the EDM
Viewing Object Profile Information on the EDM
Viewing Object Profiles on the EDM
Comparing Object Information on the EDM
Comparing Records in one Object Profile
Viewing a Profile's Transaction History on the EDM
About Transaction History Search Fields on the EDM
About Transaction History Results Fields on the EDM
Transaction History Transaction Types on the EDM
Viewing a Profile's Merge History on the EDM
Viewing an Object Profile From a Merge History Tree
About Audit Log Search Fields on the EDM
About Audit Log Results Fields on the EDM
Audit Log Functions on the EDM
Adding an Object Profile on the EDM
Step 1: Obtain Information about the Object
Step 2: Specify a System and Local ID
To Specify a System and Local ID
Step 3: Specify Parent Object Information
To Specify Parent Object Information
Step 4: Specify Child Object Information
To Specify Child Object Information
Step 5: Save the Object Profile
Learning About EDM Maintenance Tasks
Surviving and Non-surviving Profiles
Handling Potential Duplicates on the EDM
Updating the SBR versus System Records
Modifying Profile Information on the EDM
Modifying Parent Object Information
To Modify Parent Object Information
Adding a Child Object on the EDM
Modifying a Child Object on the EDM
Deleting a Child Object on the EDM
Updating the Single Best Record Directly on the EDM
Adding a System Record to an Object Profile on the EDM
To Add a System Record to an Object Profile
Deactivating a Profile or System Record on the EDM
Deactivating an Object Profile
Reactivating a Profile or System Record on the EDM
Reactivating an Object Profile
Working with Potential Duplicate Profiles on the EDM
Finding Potential Duplicate Profiles on the EDM
About Matching Review Search Fields on the EDM
About Potential Duplicate Results Fields on the EDM
Merging Potential Duplicate Profiles on the EDM
Working with Assumed Matches on the EDM
Finding Assumed Matches on the EDM
About Assumed Match Results Fields on the EDM
Reversing an Assumed Match on the EDM
Combining Object Information on the EDM
Merging Object Profiles on the EDM
Merging System Records on the EDM
Unmerging Object Information on the EDM
Unmerging Object Profiles on the EDM
To Unmerge two Merged Object Profiles
Unmerging System Records on the EDM
The Matching Review function of the EDM allows you to view any object profiles that are marked as potential duplicates of each other by the master index application. You can search for and view potential duplicate profiles on the EDM, and then fix the potential duplication by either merging or resolving the two profiles. You can view potential duplicates that are resolved, but not those that are merged.
Perform any of the following tasks to monitor and fix potential duplicate profiles.
Potential duplicate profiles are determined based on the matching probability weight that indicates how closely two profiles match. You can easily find and compare potential duplicate profiles using the EDM.
Figure 42 Potential Duplicate Comparison Page
Figure 43 Matching Review Search Page
If more than one potential duplicate pair matches the search, the Potential Duplicate Result page appears (for more information, see About Potential Duplicate Results Fields on the EDM).
Figure 44 Potential Duplicate Search Results List
If only one potential duplicate pair matches the search, the Comparison page appears.
Figure 45 Associated Records List
Tip - If there is more than one page of results on the Associated Records, click Next to view the next page.
Note - If you select different types of data for each side, the differences between the two profiles are no longer highlighted (for example, if you choose SBR address data on one side and system record address data on the other, or if you choose SBR address data on one side and SBR phone data on the other).
The fields located on the Matching Review Search page allow you to specify information about the potential duplicate or assumed match profiles you want to view.
Table 9 Matching Review Search Fields
|
The fields located in the potential duplicate results list help you to identify a potential duplicate pair to display on the Comparison page.
Table 10 Potential Duplicate Results Fields
|
When you compare two potential duplicate profiles, you might find that the object profiles represent the same entity, or that a system record from one profile actually belongs in the other profile. You can perform either an object profile merge or a system record merge to correct this. When you merge two profiles, the SBR of the surviving profile(s) is automatically recalculated based on the system records involved in the merge.
For more information about merging object profiles, see Combining Object Information on the EDM.
The merge result profile appears, allowing you to view the profile that will be saved after the merge.
The merge result record appears, allowing you to view the information that will be saved in the SBR after the merge.
When you compare two potential duplicate profiles and determine that they do not represent the same object, you can resolve the two profiles to flag the profiles as not being potential duplicates. There are two types of resolution. Resolve removes a potential duplicate flag, but if one of the resolved profiles is updated the records might be listed as potential duplicates again. Resolve Permanently flags the two profiles as being permanently resolved.
The status of the potential duplicate entry is changed to Resolved and the profiles are no longer regarded as possible duplicates of one another.