|Skip Navigation Links|
|Exit Print View|
|Working With the EDM for Oracle Java CAPS Master Index Java CAPS Documentation|
When you determine that two profiles represent the same object, you can merge the profiles to form one profile that contains the object’s most current information. You can also merge system records within one profile or from one profile to another. The resulting profile is called the Merge Result Record. The SBR for the surviving profile(s) is automatically recalculated based on the system records involved in the merge.
You can display the object profiles to merge using the Search function or the Matching Review function. This section describes how to merge records using the Search function. For information about merging records using the Matching Review function, see Merging Potential Duplicate Profiles on the EDM.
The following topics provide instructions for merging profiles or system records.
When you merge object profiles, all of the system records associated with the non-surviving object profile are transferred to the surviving object profile. The non-surviving profile is given a status of merged and is no longer active. The SBR of the surviving profile is recalculated based on the new system records that were added to the profile due to the merge. After merging two profiles, review the system records in the active profile to determine whether any of them should be deactivated.
Figure 49 Comparison Page - Merging Object Profiles
The Comparison page appears.
The merge result profile appears, allowing you to view the profile that will be saved after the merge.
You can merge a system record from one object profile into a system record from another object profile or you can merge two system records in one profile, as long as both system records originated from the same system. You can also specify which, if any, information to save from the non-surviving system record. When you merge system records, the non-surviving system record is transferred into the object profile of the surviving system record, and is given a status of merged. The SBR of the surviving profile is automatically recalculated.
Note - If you do not specify which child objects to retain during a system record merge, the master index application chooses for you; however, the EDM can be configured such that you must select which child objects to retain for certain object types (see your system administrator for more information about how your EDM is configured). If specifying child objects to retain is optional and you do not manually select the child objects, the default is to retain all child objects of a unique type from both system records. If there are any child objects of the same type, the default is to retain only the child object of the surviving system record. For example, if one system record has an office address and the other has a home address, both addresses are retained; but if both system records have a home address, the address of the surviving system record is retained.
Figure 50 Merging System Records
The Comparison page appears with the differences between the two records highlighted in blue.
Two LID Merge arrow buttons appear at the top of the page.
The merge result record appears, allowing you to view the information that will be saved in the SBR after the merge.
After you merge two system records, the surviving system record is updated, and the non-surviving system record is transferred to the “merge to” profile and is marked as merged. The SBRs for both object profiles involved in the merge are recalculated. If the “merge from” profile no longer has any system records, it is deactivated.