InfoSphere® MDM enables the enterprise to create a single, trusted record for
To achieve this capability, the suspect processing feature has
a set of externalized, customizable business rules that prevent the
persistence of duplicate parties in the system. For example, while
adding a new party, if an existing party is found to have an exact
match, the new party information may be used to update the existing
party instead of adding a new record for that party.
However, some businesses may require the persistence of these duplicate
parties. In these cases, it is expected that the business maintains
multiple profiles of the same party, for example: by line of business.
Further, these party profiles should not be subject to the party
merging functionality, such as the automatic merge on the addition
of a new party information or collapse functionality. Also, the business
may want to view an aggregate of this data across these duplicate
profiles. The exact matches across lines of business, for example,
would have a suspect status of 6 - “Parties are Duplicates - Collapse
Not Permitted”. This view could be a collection of the data across
all duplicates, allowing any conflicting party information to be resolved
based on rules of survivorship. This is the purpose of the aggregated
party view feature (getAggregatedPartyView service).
Important: To use the aggregated party view feature, you must
enable the system to persist duplicates.