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
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
Oracle Java CAPS Master Index provides a flexible framework to allow you to create matching and indexing applications called master index applications. It is an application building tool to help you design, configure, and create a master index application that will uniquely identify and cross-reference the business objects stored in your system databases. Business objects can be any type of entity for which you store information, such as customers, patients, vendors, businesses, hardware parts, and so on. Oracle Java CAPS Master Index allows you to define the data structure of the business objects to be stored and cross-referenced. In addition, you define the logic that determines how data is updated, standardized, weighted, and matched in the master index database.
The following topics provide additional information about Oracle Java CAPS Master Index, the master index applications created by Oracle Java CAPS Master Index, and the Master Index Data Manager (MIDM).
The applications created by Oracle Java CAPS Master Index are enterprise-wide master index applications that maintain the most current information about the objects in your business enterprise. A master index application creates a single, consistent view of all object data by providing an automatic, common identification process regardless of the location or system from which the data originates. Object profiles from various locations are cross-referenced using an enterprise-wide unique identifier (EUID) assigned to each profile by the master index application. By creating EUIDs, a master index application can identify many types of participants, such as customers, employees, contacts, and so on.
The identification and general information for all objects is centralized in one shared index. A master index application is designed specifically to support scattered business locations and disparate information systems across an enterprise, as well as various applications from multiple vendors. Maintaining a centralized database for multiple systems enables a master index application to integrate data throughout the enterprise while allowing local systems to continue operating independently. A master index application makes it easy to find information that was previously scattered among multiple systems.
The components of the master index applications you create are highly configurable, allowing each master index application to be customized for your specific data processing needs. Primary features of a master index application include the following:
Centralized Information – A master index application maintains a centralized database, enabling the integration of data records throughout the enterprise while allowing local systems to continue operating independently. The index stores copies of local source records and the single best record (SBR), which represents the most accurate and complete data for each object. This database is the central location of all object information and identifiers, and is accessible throughout the enterprise. Records from various systems are cross-referenced using the EUID assigned by a master index application to each object profile.
Configurability – Before deploying a master index application, you can customize the components and processing capabilities of the system. The configurable components include:
The types of objects to index
The types of data stored
The standardization and match engines to use
Matching, standardization, and phonetic conversion rules
Survivorship and weighting rules for determining the SBR
The types of queries available
How queries are blocked, or grouped, for match processing
MIDM appearance
Searches available to the MIDM
Local ID validation rules
Cross-referencing – A master index application serves as a global cross-reference, matching profiles across disparate source systems and simplifying the process of sharing data between systems. A master index application uses the local identifiers assigned by your existing systems as a reference, allowing you to maintain your current systems and practices.
Data Cleansing – A master index application uses configurable matching algorithm logic to uniquely identify object profiles and to identify duplicate and potential duplicate profiles. A master index application provides the ability to easily merge or resolve duplicates, and can be configured to automatically match profiles that are found to be duplicates of one another.
Data Updates – A master index application provides the ability to add, update, deactivate, merge, and delete data in the database tables through messages received from external systems or the MIDM. Messages received from external systems and the MIDM are checked for potential duplicates during processing.
Updates to External Systems – The master index application can publish updated information to external systems, provided the external systems can accept incoming messages. This is handled through a JMS Topic to which a master index application publishes XML messages that contain the updates.
Identification – A master index application employs configurable probabilistic matching technology. This technology uses a matching algorithm to formulate an effective statistical measure of how closely profiles match. Using a state-of-the-art algorithm in real-time mode and establishing a common method of locating profiles, a master index application consistently and precisely identifies objects within an enterprise.
Matching Algorithm – A master index application is designed to use the Master Index Match Engine or a custom matching algorithm to provide a matching probability weight between object profiles. You define matching thresholds, which control how potential duplicates and automatic merges are determined.
Unique Identifier – A master index application assigns an enterprise-wide unique identifier (EUID) to each object added to the database. The index uses the EUID to cross-reference the local IDs assigned to each object by the various computer systems throughout the enterprise.
While a master index application cleanses data automatically as it is entered through external system messages or through the MIDM, there are instances where it cannot be determined automatically whether two object profiles truly match one another. In these cases, manual review through the MIDM is needed to verify the status of the two profiles and then to possibly join two potential duplicate profiles or separate two profiles that were automatically joined. The MIDM provides additional functions to help you maintain the data you store.
Using the MIDM, you can perform the following activities.
View an Object’s History – The system provides a complete transaction history of each object profile by recording all changes to each object’s data. This allows you to view before and after images of a profile for each change made. The table also records the user ID of the person who made the changes. This history is maintained for both the local source records and the SBR.
Search for Object Profiles – Using the MIDM, you can search for specific objects or sets of objects. The MIDM allows you to perform different types of searches using different combinations of data elements and returns a list of potential matches to your search criteria. For certain searches, the results are assigned a matching weight that indicates the probability of a match.
Maintain Object Data – The MIDM supports all the necessary features for maintaining object profiles. It allows you to add new profiles; view, update, deactivate, or reactivate existing profiles; and compare profiles for similarities and differences. You can also view each local source record associated with an SBR.
Compare Object Data – The MIDM allows you to compare two or more object profiles in a side-by-side comparison so you can evaluate their differences or similarities. You can also compare different objects within one object profile in the same comparison view. For example, you can compare the profile’s SBR with a record from System A and you can compare a profile’s record from System A with its record from System B.
View and Resolve Potential Duplicates – Using algorithm matching logic, a master index application has the ability to identify potential duplicate profiles, and the MIDM provides the ability to manually correct the duplicate profiles. Profiles that are potential duplicates can be viewed online in a side-by-side comparison. Potential duplication is resolved by either merging the profiles in question or removing their potential duplicate flags.
Merge and Unmerge Profiles – You can compare potential duplicate profiles and then merge the profiles if you find them to be actual duplicates of one another. Using the merge feature, you can determine which profile to retain as the active profile. The MIDM also allows you to merge source records between object profiles and to specify which information from each source record to preserve in the resulting profile. If two object profiles or source records are merged in error, you can unmerge them, returning the information to the original records. You can also view a history of merges for a profile by viewing its merge tree.
Audit Log – The system administrator can specify that a log be maintained of each instance that object data is accessed from the MIDM. This log provides information such as the user ID of the user who accessed the data, the type of action that was performed against the data, and the date and time of access.
Security – Security is provided through the application server and includes basic access to the database through user login IDs and passwords, as well as access to specific functions and actions of a master index application. Access can be restricted by functions, actions within functions, data element, and user ID.