addSuspect
- Description
- This transaction adds a new suspect relationship between two given parties.
- Web Services
- Operation name: addSuspect
- Example
Add a suspect relationship between the parties Christine Jones and Chris Jones and provide a suspect status of
Parties Suspected to be Duplicates – Collapse Not Permitted.- Usage information
- The purpose of this transaction is to establish a suspect relationship
between two parties.
New suspect relationships are initially determined by an external application, which then submits a request using this transaction to InfoSphere® MDM to establish the relationship. The integration point between InfoSphere MDM and the external application determines the values for the relationship parameters.
- Preconditions
- Both parties must exist and be active.
- Mandatory input
- PartyId
- SuspectPartyId
- SuspectStatusType
- SourceType
- MatchEngineType
- CurrentSuspectCategoryType
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
- If the value of SuspectPartyId is greater than the value of PartyId, then this transaction swaps the two parties, and will consider the party with the lower ID value to be the Suspect Party.
- Request message
- <TCRMTxType> addSuspect
<TCRMTxObject> TCRMSuspectBObj
<TCRMObject> TCRMSuspectBObj
- Response objects
- TCRMSuspectBObj Note: If not specified in the request, the CurrentMatchEngineType attribute uses the value of MatchEngineType by default.
- Special note
- The following attributes cannot be specified by this transaction: