JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Working With the EDM for Oracle Java CAPS Master Index     Java CAPS Documentation
search filter icon
search icon

Document Information

Working With the EDM for Oracle Java CAPS Master Index

Related Topics

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

EDM Object Profile Components

System Records

Single Best Record

Survivor Calculator

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)

EUID

Local ID

Working with the Enterprise Data Manager

Logging in to the Enterprise Data Manager

To Log in to the EDM

Enterprise Data Manager Security Permissions

Enterprise Data Manager Navigation Tips

Navigating the EDM Functions

Navigating the EDM Search Pages

Navigating the EDM Detail Pages

Logging Out of the EDM

Learning About Object Queries on the EDM

About the EDM Search Function

The Lookup Page

The Search Page

The Comparison Lookup Page

The Search Result Page

Types of EDM Searches

EUID Lookup

Local ID Lookup

Advanced Search

Comparison Lookup

Searching by Ranges on the EDM

Required Fields on the EDM

Searching for Object Profiles on the EDM

Performing an EUID Lookup on the EDM

To Perform an EUID Lookup

Performing a Local ID Lookup on the EDM

To Perform a Local ID Lookup

Performing an Alphanumeric Search on the EDM

To Perform an Alphanumeric Search

Performing a Phonetic Search on the EDM

To Perform a Phonetic Search

Performing a Blocker Search on the EDM

To Perform a Blocker Search

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

The Tree View

Information Fields

Object Profile Comparisons on the EDM

Object Profile Transaction Histories on the EDM

Object Profile Merge Histories on the EDM

The EDM Audit Log

Viewing Object Profile Information on the EDM

Viewing Object Profiles on the EDM

To View Object Information

Comparing Object Information on the EDM

Comparing two Object Profiles

Comparing Records in one Object Profile

Viewing a Profile's Transaction History on the EDM

To View a Transaction History

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 a Merge History Tree

Viewing an Object Profile From a Merge History Tree

Viewing the EDM Audit Log

To View the Audit Log

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

To Save the Object Profile

Learning About EDM Maintenance Tasks

Matching Probability Weights

Merging Profiles on the EDM

Surviving and Non-surviving Profiles

System Record Merges

Undoing a Merge

Assumed Matches

Potential Duplicates

Handling Potential Duplicates on the EDM

Merge

Resolve

Update Tips for the EDM

Concurrent Users

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

To Add a Child Object

Modifying a Child Object on the EDM

To Modify a Child Object

Deleting a Child Object on the EDM

To Delete a Child Object

Updating the Single Best Record Directly on the EDM

Locking an SBR Field

Unlocking an SBR Field

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

Deactivating a System Record

Reactivating a Profile or System Record on the EDM

Reactivating an Object Profile

Reactivating a System Record

Working with Potential Duplicate Profiles on the EDM

Finding Potential Duplicate Profiles on the EDM

To Find Potential Duplicates

About Matching Review Search Fields on the EDM

About Potential Duplicate Results Fields on the EDM

Merging Potential Duplicate Profiles on the EDM

To Combine Object Profiles

To Combine System Records

Resolving Potential Duplicate Profiles on the EDM

To Resolve two Potential Duplicate Profiles

Working with Assumed Matches on the EDM

Finding Assumed Matches on the EDM

To Find Assumed Matches

About Assumed Match Results Fields on the EDM

Reversing an Assumed Match on the EDM

To Reverse an Assumed Match

Combining Object Information on the EDM

Merging Object Profiles on the EDM

To Merge Object Profiles

Merging System Records on the EDM

To Merge System Records

Unmerging Object Information on the EDM

Unmerging Object Profiles on the EDM

To Unmerge two Merged Object Profiles

Unmerging System Records on the EDM

To Unmerge two Merged System Records

Learning About EDM Reports

EDM Production Reports

EDM Activity Reports

EDM Search Result Reports

Configuring EDM Reports

Masked Data and EDM Reports

Running EDM Reports

To Run Reports From the EDM

About Report Search Fields on the EDM

Working with Assumed Matches on the EDM

The Matching Review function of the EDM allows you to view any object profiles that were automatically updated by the master index application as a result of an assumed match. You can reverse the assumed match if necessary. This section provides instructions for finding profiles updated by an assumed match and then reversing the update if necessary. Perform the following tasks to work with profiles that were automatically matched.

Finding Assumed Matches on the EDM

You can find object profiles that were updated by an assumed match using the Matching Review function of the EDM. When you search for assumed matches, you can select an object profile to view from a results list.

Figure 46 Assumed Match Page

image:Figure shows a comparison of one profile before and after an assumed match was made against it.

To Find Assumed Matches

  1. Obtain information about the object profile you want to view, such as their EUID, a system in which they are registered, or the login ID of the user who added the record that caused the update.
  2. On the EDM, select Matching Review. The Matching Review Search page appears.

    Figure 47 Matching Review Search Page

    image:Figure shows the Assumed Match Search page.
  3. On the Matching Review Search page, enter the search criteria (for more information, see About Matching Review Search Fields on the EDM).
  4. In the upper portion of the page, click Search for Assumed Match.

    One of the following occurs:

    • If more than one profile matches the search criteria, the Assumed Match Result page appears (for more information, see About Assumed Match Results Fields on the EDM). Continue to step 5.

    • If only one profile matches the search criteria, the Assumed Match page appears with a comparison of the two profiles that were combined with the differences between the two profiles highlighted in blue. Skip to step 6.


    Figure 48 Assumed Match Results List

    image:Figure shows the results of an assumed match search.
  5. In the Results list, click the ID of the assumed match profile you want to view.

    The Assumed Match page appears with the parent object of the SBR displayed.

  6. To view additional information about the object, review the instructions provided under Viewing Object Profiles on the EDM.
  7. To view the next entry in the assumed match results list, click Next>.
  8. To view the previous entry in the assumed match results list, click <Previous.
  9. To return to the assumed match results list, click Result.

About Assumed Match Results Fields on the EDM

The fields located in the assumed match results list help you to identify an assumed match transaction to display on the Comparison page.

Table 11 Assumed Match Results Fields

This field …
displays this information …
ID
The assumed match ID of the transaction that caused the assumed match.
EUID
The enterprise-wide unique identification number of the object profile that was updated by the assumed match.
Weight
The matching probability weight between the updated profile and the record that caused the assumed match.
System
The system with which the record that caused the assumed match is associated.
Local ID
The local ID in the above system for the record that caused the assumed match. The name of this field might be different for your implementation.
Create User
The login ID of the user who added the profile that created the assumed match.
Create Date
The date and time the transaction that caused the assumed match occurred.

Reversing an Assumed Match on the EDM

If you find that an assumed match was made in error, you can reverse the assumed match. This process returns the updated object profile to its status just prior to the assumed match update, creates a new object profile for the record that caused the assumed match, and recalculates the SBR for the existing profile.

To Reverse an Assumed Match

  1. View the assumed match profile, as described in Finding Assumed Matches on the EDM.
  2. In the upper portion of the page, click Undo Assumed Match.

    A confirmation dialog box appears, providing the EUID number of the new profile that will be created as a result of reversing the match.

  3. On the confirmation dialog box, click OK.

    The assumed match is reversed, the updated profile is returned to its state prior to the assumed match, and a new object profile is created for the system record that caused the assumed match. Any changes that were made after the assumed match but before reversing the assumed match are retained.