Problem Note 60954: The alert-generation process fails and an error occurs after you create or update scenarios using the Scenario window in SAS® Anti-Money Laundering
 |  |  |  |  |
In SAS Anti-Money Laundering, the alert-generation process might fail and you might encounter an error similar to the one below when you create a new scenario or update an existing scenario using the Scenario window:
ERROR: FCF: There may be a problem in the seg_kc.FSC_PARTY_ACCOUNT_BRIDGE
ERROR: FCF: Compare STG_ALER.suppressed_alerts to MST_ALER.entity_alerts to determine which primary entity number(s) were dropped
ERROR: FCF: Also make sure there are not multiple rows in the dimension table (fsc_party_dim) with the same number (party_number)
that have change_current_ind = 'Y'
FCF_GET_ENTITY_INFO VERSION 7.1
ERROR: FCF: A problem has occurred in FCF_GET_ENTITY_INFO while processing alerts. Please see the SAS log for details.
The error occurs when you use Microsoft SQL Server as the database management system for SAS Anti-Money Laundering. When you create or update a scenario using the Scenario window, the fields in the FSK_SCENARIO table (particularly, the entity_level_code field) are updated with a blank value instead of a null value. Because Microsoft SQL Server handles blank and null values differently, the underlying query in the FCF_GET_ENTITY_INFO macro that is called in the alert-generation process fails.
To work around this issue in the alert-generation process, change the value from a blank value to a null value in your FSK_SCENARIO table.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 7.1 | |||
| 64-bit Enabled AIX | 7.1 | |||||
| 64-bit Enabled Solaris | 7.1 | |||||
| Linux for x64 | 7.1 | |||||