Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Oracle Customer Hub (UCM) to Resolve Duplicate Records > Configuring Duplicate-Resolution Functionality > About Suspect MatchingPreviously when an incoming account or contact record was flagged for manual review by the UCM data management workflow, the record was placed in Review status, and a new record was not created. This action disrupted the overall business process workflow involving Oracle Customer Hub (UCM) and other connected applications. What Happens When an Incoming Record Has a Status of Review?With the latest release of Oracle Customer Hub (UCM), when an incoming record is flagged for manual review a new best version record is also created, with the appropriate UUID and cross-reference. The best version record is given a status of Suspect to be differentiated from the previously reviewed records. A response message is returned to the requesting external application. The suspect record and any identified potential duplicates that are flagged by the UCM data management workflow are stored in a duplicate results table and made available for the data steward to review in the Duplicate Account or Duplicate Contact views. The suspect record can be approved or merged in these views. The update and delete actions can be performed in the Account and Contact views. While the record has a Suspect status, it cannot be published to any other subscribing systems. If the suspect record already exists in the external application, the Update and Delete operations on the suspect record will keep the external application informed. The Unmerge operation restores the merged record to its previous state. If the data steward deems that the record is not a match for any of the existing records, the Suspect status is removed, and an upsert message is sent to the external applications that do not yet have the suspect record. When the suspect record is merged into another record, a message is sent to all external applications to preserve the synchronization. When the Suspect status is removed from the record, the result is sent to those applications that do not yet have the record. What Happens When a Record Has a Status of Pending?While this record still has the Pending status, it can be updated, deleted or merged in the UI or through an incoming message. If the update is sent from a different system and not from the originating system (through auto match), then a cross-reference must be created for the additional system. Before the Pending status is resolved, any changes to this best version record must be published to all the systems that have an associated cross-reference associated. When the pending record is identified as a potential duplicate with another nonpending best version record, it is recommended that the pending record be merged into the nonpending best version record. When the Suspect status is removed from the record, the result is sent to those applications that do not yet have the record. By default two system preferences allow you to use suspect match: |
![]() ![]() |
Oracle Customer Hub (UCM) Master Data Management Reference | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |