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
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
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
To Unmerge two Merged System Records
Oracle Java CAPS Master Index provides a set of production, activity, and search result reports that can be generated from the EDM. 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. Search result reports allow you to print a list of profiles in a search result set.
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. The information you find in these reports provides 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 can be run for the current day, the previous day, or for a date range you specify. If you run your daily reports in the evening, you should run the current day’s reports. If you run your daily reports in the morning, you should run the previous day’s reports.
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. Oracle Java CAPS 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 enterprise records that were merged during the specified time period. Review this report daily to ensure that no profiles were merged in error. Oracle Java CAPS master index applications provide the ability to unmerge any merged profiles.
UnMerge Transaction Report - This report displays a list of all enterprise records 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
Update
EUID Deactivate
EUID Merge
EUID Unmerge
LID Merge
LID Unmerge
LID Transfer
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 summary includes the number of each of the following transactions that were performed for the month:
Add
EUID Deactivate
EUID Merge
EUID Unmerge
LID Merge
LID Unmerge
Unresolved Potential Duplicates
Resolved Potential Duplicates
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 monthly activity report above.
In addition to viewing a search result list on an EDM window, you can create and print a search result report. This allows you to view a complete list of all profiles in a result set rather than viewing them one page at a time. You can generate search result reports for general, transaction history, assumed match, potential duplicate, and audit log search results. These reports are accessed from the Search Results page for the search you performed. Search result reports can be viewed online or sent to a printer of your choice. The fields that appear on the reports depend on the fields that appear on the Results page for the type of search you performed. For instructions on running a search result report, see Creating and Printing a Search Result Report.
The report files are configured by the Enterprise Data Manager file (edm.xml) in the master index project. For detailed information and instructions on configuring the reports, see Configuring Oracle Java CAPS Master Indexes (Repository) and Understanding Oracle Java CAPS Master Index Configuration Options (Repository).
Though the EDM can be configured to hide certain fields from users who do not have the appropriate security permissions, reports generated from the EDM 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.