In SAS Money Laundering Detection, there are several 'events' that can be performed in the Investigation UI component. These events include adding comments, notes, closing an alert etc. All event features require use of FSK_SEQUENCE.

Currently two features, 'Closing an Alert', and 'Filing a SAR' are using FSK_SEQUENCE differently from the other events. This is causing the UNIQUE index on FSK_ALERT_EVENT to fail as well as preventing the event from being documented in the metadata. The loss of the metadata invalidates the system and prevents multiple events from occuring.

Removing the UNIQUE constraint on the INDEX is not an option as this will allow the population of invalid sequence numbers (surrogate keys) into the system and will result in multiple events having the same id.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Money Laundering Detection 1.4 is available at: