updateSuspectStatus

Description
The purpose of this transaction is to allow the suspect status for two given suspects to be updated once the suspect situation has been investigated or adjusted due to suspect matching augmentation.
Web Services
Operation name: updateServiceProduct
Service name: PartyService
Example
Update the suspect status to show that the two parties are not the same person.
Usage information
If the application identified two parties as possible suspects and the investigation has determined that they are in fact not suspects, this transaction would be used to change the status to not duplicates.

If the investigation reveals that the two parties are in fact the same individual or organization, the suspect status could be changed to duplicate to reflect the results of the investigation prior to a collapse.

You can define suspect status values using a code table.

Preconditions
Suspect object must exist.
Mandatory input
  • LastUpdateDate
Inquiry levels
Not applicable
Filter values
Not applicable
Transaction behavior

If the ACXIOM Integration feature is used and both source Party and suspect Party have AbiliTec Maintained Links a suspect augmentation matching record is created in SUSPECTAUGMENT table.

If the IBM® InfoSphere® QualityStage Matching feature is used for match adjustment, this transaction will create a suspect augmentation matching record in SUSPECTAUGMENT table for the suspect object.

This transaction uses the CurrentSuspectCateogryRule externalized rule to set the current suspect category and current match engine value in the suspect object. The default behavior of this rule is to choose the current suspect type based on the suspect augmentation type of the match engine with the highest priority. The priority, from highest to lowest:
  1. AbiliTEC match adjustment
  2. InfoSphere QualityStage match adjustment
  3. InfoSphere MDM deterministic
The default implementation of the externalized rule for setting current suspect category will return the following, in order of preference, from an A1 AbiliTEC match to a no suspect error:
  1. Only one AbiliTEC adjusted A1 match found.
  2. Best AbiliTEC adjustment A1 match found (based on highest match relevancy score and lowest non-match relevancy score).
  3. Only one InfoSphere QualityStage adjusted A1 match found.
  4. Best InfoSphere QualityStage adjustment A1 match found (based on weight).
  5. Only one InfoSphere MDM deterministic A1 match found.
  6. Best InfoSphere MDM deterministic A1 match found (based on highest match relevancy score and lowest non-match relevancy score).
  7. Only one AbiliTEC adjusted A2 match found.
  8. Best AbiliTEC adjustment A2 match found (based on highest match relevancy score and lowest non-match relevancy score).
  9. Only one InfoSphere QualityStage adjusted A2 match found.
  10. Best InfoSphere QualityStage adjustment A2 match found.
  11. Only one InfoSphere MDM deterministic A2 match found.
  12. Best InfoSphere MDM deterministic A2 match found (based on highest match relevancy score and lowest non-match relevancy score).
  13. Error if neither A1 or A2 match found (No suspect found for collapse).
Request message
<TCRMTxType> updateSuspectStatus

<TCRMTxObject> TCRMSuspectBObj

<TCRMObject> TCRMSuspectBObj with no associations

Response objects
TCRMSuspectBObj
Special note
Not applicable