JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Master Index Data Manager User's Guide     Java CAPS Documentation
search filter icon
search icon

Document Information

Master Index Data Manager User's Guide

Related Topics

About the Master Index Data Manager

About Oracle Java CAPS Master Index

About Master Index Applications

Features of Master Index Applications

Functions of the Master Index Data Manager

Learning about MIDM Object Profiles

MIDM Object Profile Components

Source Records

Single Best Record

Survivor Calculator

Source Record and SBR Components in a Master Index

Identification Numbers for each Entity in the Master Index

EUID

Local ID

Auxiliary ID

Working with the Master Index Data Manager

Requirements

Logging in to the Master Index Data Manager

To Log in to the MIDM

Master Index Data Manager Security Permissions

Master Index Data Manager Navigation Tips

Navigating the MIDM Functions

Navigating the MIDM Detail Pages

Logging Out of the MIDM

Using the MIDM Dashboard

Viewing Summary Information From the Dashboard

To View Summary Information

Accessing Reports and Audit Logs From the Dashboard

To Access Reports and Audit Logs From the Dashboard

Performing a Quick Search (EUID Lookup)

To Perform Quick Search

Performing an EUID Comparison Lookup

To Perform an EUID Comparison Lookup

Learning About Object Queries on the MIDM

About the MIDM Search Function

Simple Lookup

Advanced Alphanumeric Lookup

Advanced Phonetic Lookup

EUID Comparison Lookup

The Search Results List

Searching by Ranges on the MIDM

Required Fields on the MIDM

Searching for Object Profiles on the MIDM

Performing an EUID Lookup

To Perform an EUID Lookup

Performing a Local ID Lookup

To Perform a Local ID Lookup

Performing an Alphanumeric Search

To Perform an Alphanumeric Search

Performing a Phonetic Search

To Perform a Phonetic Search

Performing an EUID Comparison Lookup

To Perform an EUID Comparison Lookup

Working with Search Results on the MIDM

Viewing the Results of a Search

Selecting a Profile from the Results List

Sorting the Results of Your Search

Learning About Object Profile Views on the MIDM

Object Profile Details on the MIDM

Source Record Details on the MIDM

Object Profile and Source Record Comparisons

Object Profile Transaction Histories

Object Profile Merge Histories on the MIDM

The Master Index Audit Log

Viewing Object Information on the MIDM

Viewing Object Profiles on the MIDM

To View an Object Profile

Viewing a Source Record on the MIDM

To View a Source Record

Comparing Object Information on the MIDM

Comparing Two or More Object Profiles

Comparing Source Records From Object Profile Views

Comparing Source Records From One Source System

Viewing Transaction Histories on the MIDM

To View a Complete Transaction History For an Object Profile

To View Transaction History Records from the Transactions Page

About Transaction History Search Fields on the MIDM

About Transaction History Results Fields on the MIDM

Transaction History Transaction Types on the MIDM

Viewing a Profile's Merge History on the MIDM

To View an Object's Merge History

Viewing Merged Profiles for an Object Profile

To View Merged Profiles for an Object Profile

Viewing the MIDM Audit Log

To View the Audit Log

About Audit Log Search Fields on the MIDM

About Audit Log Results Fields on the MIDM

Audit Log Functions on the MIDM

Adding an Object Profile on the MIDM

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 MIDM Maintenance Tasks

Matching Probability Weights

Merging Profiles on the MIDM

Surviving and Non-Surviving Profiles

Source Record Merges

Undoing a Merge

Assumed Matches

Potential Duplicates

Handling Potential Duplicates on the MIDM

Merge

Resolve

Survivor Calculator Overrides

Linking Source Record Fields to the SBR

Locking Field Values in the SBR

Concurrent Users on the MIDM

Modifying Profile Information on the MIDM

Modifying Information in an Object Profile

Modifying Parent Object Information in a Profile

Adding a Child Object to an Object Profile

Modifying a Child Object in a Profile

Deleting a Child Object From a Profile

Modifying Information Directly in a Source Record

Modifying the Parent Object in a Source Record

Adding a Child Object to a Source Record

Modifying a Child Object in a Source Record

Deleting a Child Object From a Source Record

Overwriting SBR Field Values

Locking an SBR Field

Unlocking an SBR Field

Overriding the Survivor Calculator's SBR

Linking an SBR Field to a Specific Source Record

Unlinking an SBR Field From a Source Record

Adding a Source Record to an Object Profile

To Add a Source Record to an Object Profile

Deactivating a Profile or Source Record

Deactivating an Object Profile

Deactivating a Source Record

Reactivating a Profile or Source Record

Reactivating an Object Profile

Reactivating a Source Record

Working with Potential Duplicate Profiles on the MIDM

Finding Potential Duplicate Profiles on the MIDM

To Find Potential Duplicates

About Duplicate Records Search Fields on the MIDM

Merging Potential Duplicate Profiles

To Combine Duplicate Profiles From the Comparison Page

Resolving Potential Duplicate Profiles on the MIDM

To Resolve Potential Duplicate Profiles From the Results List

To Resolve Potential Duplicate Profiles From the Comparison Page

Unresolving Potential Duplicate Profiles on the MIDM

To Unresolve Potential Duplicate Profiles From the Results List

To Unresolve Potential Duplicate Profiles From the Comparison Page

Working with Assumed Matches on the MIDM

Finding Assumed Matches on the MIDM

To Find Assumed Matches

About Assumed Matches Search Fields

About Assumed Match Results Fields on the MIDM

Reversing an Assumed Match on the MIDM

To Reverse an Assumed Match

Combining Object Information on the MIDM

Merging Object Profiles on the MIDM

To Merge Object Profiles

Merging Source Records on the MIDM

To Merge Source Records

Unmerging Object Information on the MIDM

Unmerging Object Profiles on the MIDM

To Unmerge Object Profiles

Unmerging Source Records on the MIDM

To Unmerge Two Merged Source Records

Learning About MIDM Reports

MIDM Production Reports

MIDM Activity Reports

Configuring MIDM Reports

Masked Data and MIDM Reports

Running MIDM Reports

To Run Reports From the MIDM

About Report Search Fields on the MIDM

Working with Assumed Matches on the MIDM

The Assumed Matches function of the MIDM 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. The following topics provide 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 MIDM

You can find object profiles that were updated by an assumed match using the Assumed Matches function of the MIDM. When you search for assumed matches, you can select an object profile to view from a results list to determine whether the assumed match was made correctly.

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. In the tabbed headings, select Assumed Matches.

    The Assumed Matches search page appears.


    Figure 56 Assumed Matches Search Page

    image:Figure shows the Assumed Match Search page.
  3. On the Assumed Matches search page, enter the search criteria (for more information, see About Assumed Matches Search Fields).
  4. Click Search.

    The Assumed Match Result page appears (for more information, see About Assumed Match Results Fields on the MIDM).


    Figure 57 Assumed Matches Search Results List

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

    The Assumed Matches page appears with the assumed match profile displayed.


    Figure 58 Assumed Matches Comparison Page

    image:Figure shows two profiles involved in an assumed match transaction.
  6. To view a transaction history of the profile, click View History at the bottom of the page.
  7. To undo the assumed match transaction, follow the instructions provided under Reversing an Assumed Match on the MIDM.

About Assumed Matches Search Fields

The fields located on the Assumed Matches search page allow you to specify information about the assumed match profiles you want to view.

Table 8 Assumed Matches Search Fields

In this field …
type or select ...
EUID
The enterprise-wide unique identification number of the profile you want to view.
System
The external system with which the object profile that caused the assumed match is associated.
Local ID
The local ID associated with the object profile in the specified system. The name of this field might be different for your implementation.
Create Date From
A beginning create date for the profiles you want to view. The query is performed for transactions that were created between the Create Date From (and Create Time From) and the To Create Date (and To Create Time).
To Create Date
The ending create date for the profiles you want to view.
Create Time From
The beginning create time for the profiles you want to view (using 24-hour notation). If no time is entered, the default value is 00:01 (12:01 A.M.).
To Create Time
The ending create time for the profiles you want to view (using 24-hour notation). If no time is entered, the default value is 24:00.

About Assumed Match Results Fields on the MIDM

The fields located in the assumed match results list help you to identify an assumed match transaction to display on the Assumed Matches comparison page. The fields described in the following table always appear in the results list, but the list can be configured to include additional fields.

Table 9 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 MIDM

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.

Figure 59 Assumed Matches Page – Reversing an Assumed Match

image:Figure shows an assumed match transaction ready to be reversed.

To Reverse an Assumed Match

  1. View the assumed match profile, as described in Finding Assumed Matches on the MIDM.
  2. At the bottom of the page, click Undo 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 source record that caused the assumed match. Any changes that were made after the assumed match but before reversing the assumed match are retained.

  4. On the information dialog box, click OK to view the newly created profile.