About Oracle Java CAPS Master Index (Repository)

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 Enterprise Data Manager (EDM).

• About Master Index Applications (Repository)

• Features of Master Index Applications (Repository)

• Functions of the Enterprise Data Manager

About Master Index Applications (Repository)

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 a 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 identifying 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.

Features of Master Index Applications (Repository)

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 system 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

  • EDM appearance

  • Searches available to the EDM

  • 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 EDM. Messages received from external systems and the EDM are checked for potential duplicates during processing.

• Updates to External Systems – The Oracle Java CAPS Enterprise Service Bus provides a master index application with the ability to 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.

• Integration – Relying on the Oracle Java CAPS Enterprise Service Bus, a master index application provides the power and flexibility to identify, route, and transform data to and from any system or application throughout your business enterprise. It can accept incoming transactions and distribute updates to any external system, providing seamless integration with the systems in your enterprise.

• Matching Algorithm – A master index application is designed to use the Oracle Java CAPS 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.

Functions of the Enterprise Data Manager

While a master index application cleanses data automatically as it is entered through external system messages or through the EDM, there are instances where it cannot be determined automatically whether two object profiles truly match one another. In these cases, manual review through the EDM 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 EDM provides additional functions to help you maintain the data you store. Using the EDM, 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 system records and the SBR.

• Search for Object Profiles – Using the EDM, you can search for specific objects or sets of objects. The EDM 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 EDM 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 system record associated with an SBR.

• Compare Object Data – The EDM allows you to compare two 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; or 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 EDM 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 EDM also allows you to merge system records between object profiles and to specify which information from each system record to preserve in the resulting profile. If two object profiles or system 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 EDM. 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. From the audit log, you can also view a transaction history for each transaction that caused an audit log entry.

• 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.