A new update is available for SAS Compliance Solutions , version 6.3_M1 :
SAS Note 42491 | A WHERE clause containing the DATEPART() function might be incorrectly formed when passed to Teradata with SAS/ACCESS® Interface to Teradata |
SAS Note 58715 | You see duplicate alerts in SAS® Anti-Money Laundering when you create a manual alert before running the Alert Generation Process |
SAS Note 58716 | The %fcf_replicate_transactions macro in SAS® Anti-Money Laundering does not generate triggering transactions |
SAS Note 58745 | You might encounter slow performance when you import scenarios using the Scenario Administrator in SAS® Anti-Money Laundering |
SAS Note 58746 | A \"Column new_file_nm could not be found\" error occurs when you import a scenario using the Scenario Administrator in SAS® Anti-Money Laundering |
SAS Note 58749 | You might encounter slow performance when you import rules and rule groups using the Scenario Manager in SAS® Customer Due Diligence |
SAS Note 58750 | All relationships associated with a party are deleted after you run the Integrated Event Management (IEM) process in SAS® Anti-Money Laundering |
SAS Note 58843 | On the Alert Details page in SAS® Anti-Money Laundering, the Triggering Values column value is truncated when it contains more than 255 characters |
SAS Note 58868 | ALERT: The party number for an external party alert is blank in the FSK_ALERT database table in SAS® Anti-Money Laundering |
SAS Note 58869 | Aggregated transaction totals include amounts that are not from triggering transactions in SAS® Anti-Money Laundering |
This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for A1I001 |
Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes.