Skip Navigation Links | |
Exit Print View | |
Master Index Data Manager User's Guide Java CAPS Documentation |
Master Index Data Manager User's Guide
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 Record and SBR Components in a Master Index
Identification Numbers for each Entity in the Master Index
Working with the Master Index Data Manager
Logging in to the Master Index Data Manager
Master Index Data Manager Security Permissions
Master Index Data Manager Navigation Tips
Navigating the MIDM Detail Pages
Viewing Summary Information From the Dashboard
Accessing Reports and Audit Logs From the Dashboard
To Access Reports and Audit Logs From the Dashboard
Performing a Quick Search (EUID Lookup)
Performing an EUID Comparison Lookup
To Perform an EUID Comparison Lookup
Learning About Object Queries on the MIDM
About the MIDM Search Function
Searching by Ranges on the MIDM
Searching for Object Profiles on the MIDM
Performing an Alphanumeric Search
To Perform an Alphanumeric 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
Viewing Object Information on the MIDM
Viewing Object Profiles on the MIDM
Viewing a Source Record on the MIDM
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
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
Learning About MIDM Maintenance Tasks
Surviving and Non-Surviving Profiles
Handling Potential Duplicates on the MIDM
Linking Source Record Fields to the SBR
Locking Field Values in the SBR
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
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
Reactivating a Profile or Source Record
Reactivating an Object Profile
Working with Potential Duplicate Profiles on the MIDM
Finding Potential Duplicate Profiles on the MIDM
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
About Assumed Matches Search Fields
About Assumed Match Results Fields on the MIDM
Reversing an Assumed Match on the MIDM
Combining Object Information on the MIDM
Merging Object Profiles on the MIDM
Merging Source Records on the MIDM
Unmerging Object Information on the MIDM
Unmerging Object Profiles on the MIDM
Unmerging Source Records on the MIDM
To Unmerge Two Merged Source Records
Oracle Java CAPS Master Index provides a set of production and activity reports that can be generated from the MIDM. The production reports provide information about the current state of the data in the master index application, helping you monitor stored data and determine how that data needs to be updated. This information also helps verify that the matching logic and weight thresholds are defined correctly. Activity reports provide statistical information for transactions over specific periods of time.
The following topics provide additional information to help you understand and work with the default reports:
Production reports provide information about the transactions that are processed through the master index database. These reports provide lists of potential duplicate profiles, merge transactions, unmerge transactions, assumed matches, updates, and deactivated profiles for a specified time period. These reports provide valuable information about how data is being processed with the current configuration. In addition to running the production reports daily, you should run them against any data that has been loaded from existing systems into the master index database in batch format. Production reports are run based on a date range you specify.
Assumed Match Report - This report displays information about any profiles that were automatically updated by incoming data during the specified time period. The information in this report, in combination with data from the potential duplicate report, helps you determine whether the matching threshold for assumed matches is accurate. You should review this report daily to ensure that no assumed matches were made in error.
Deactivated Record Report - This report displays a list of all profiles that were deactivated during the specified time period. Review this report daily to ensure that no profiles were deactivated in error. Master Index applications provide the ability to reactivate any deactivated profile.
Potential Duplicate Report - This report displays information about object profiles that were marked as potential duplicates of one another during the specified time period. The information provided in this report can help you determine whether the matching threshold and the duplicate threshold are configured accurately. Review this report daily to ensure potential duplicates are managed in a timely manner, and use this report as a work list when processing potential duplicates.
Merge Transaction Report - This report displays a list of all object profiles that were merged during the specified time period. Review this report daily to ensure that no profiles were merged in error. Master Index applications provide the ability to unmerge any merged profiles.
UnMerge Transaction Report - This report displays a list of all object profiles that were unmerged during the specified time period.
Update Report - This report displays object profiles whose information was updated during the specified time period. Review this report daily to verify the updates made in a given day. This report can help explain why a resolved potential duplicate listing was reinstated to the potential duplicate list.
Activity reports should be run weekly, monthly, and yearly to obtain statistical data about the transactions that are processed through the master index database. These reports give the number of each type of transaction performed for the specified week, month, or year. They also provide cumulative information for the week, month, or year to date. The information you find in these reports helps analyze the condition of the data by giving you the number of potential duplicates created, the number of assumed matches, and so on.
Weekly Activity Report - This report displays a summary of transactions that occurred against the database on each day for the specified calendar week (always Sunday through Saturday). The information provided in this summary includes the number of each of the following transactions performed each day.
Add
EUID Deactivate
EUID Merge
EUID Unmerge
LID Merge
LID Unmerge
Unresolved Potential Duplicates
Resolved Duplicates
Monthly Activity Report - This report displays a summary of transactions that occurred against the database during the specified month. You can run this report for any calendar month. The information provided in this report includes a summary of each transaction listed for the weekly activity report above.
Yearly Activity Report - This report displays a summary of transactions that occurred against the database for the specified calendar year. You can run this report for any calendar year. The information provided in this report includes a summary of each transaction listed for the weekly activity report above.
The report files are configured in midm.xml in the master index project. For detailed information and instructions on configuring the reports, see Configuring the Master Index MIDM Pages in Oracle Java CAPS Master Index Configuration Guide and Master Index Data Manager Configuration in Oracle Java CAPS Master Index Configuration Reference .
Though the MIDM can be configured to hide certain fields from users who do not have the appropriate security permissions, reports generated from the MIDM will display the hidden data if those fields are configured to appear on the reports. Be sure to only give access to users who should be able to view this information, or do not include hidden fields in the reports.