Learning About MIDM Reports

Sun 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:

• MIDM Production Reports

• MIDM Activity Reports

• Configuring MIDM Reports

• Masked Data and MIDM Reports

MIDM Production 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.

MIDM Activity Reports

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.

Configuring MIDM Reports

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 Configuring Sun Master Indexes and Master Index Data Manager Configuration in Understanding Sun Master Index Configuration Options .

Masked Data and MIDM Reports

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.