| A1I005 |
| SAS Compliance Solutions 6.3_M1 |
| Issue(s) Addressed: | Introduced: |
| 58669 | The Transactions tab of the Customer Details page might show transactions only for the Primary Owner in SAS® Anti-Money Laundering |
A1I001 |
| 58914 | The downloaded CSV data is inconsistent with the data displayed on the Alert Details page in SAS® Anti-Money Laundering |
A1I001 |
| 58929 | The current financial summary period is blank on the Customer Details page in SAS® Anti-Money Laundering |
A1I001 |
| 42491 | A WHERE clause containing the DATEPART() function might be incorrectly formed when passed to Teradata with SAS/ACCESS® Interface to Teradata |
A1I001 |
| 58715 | You see duplicate alerts in SAS® Anti-Money Laundering when you create a manual alert before running the Alert Generation Process |
A1I001 |
| 58716 | The %fcf_replicate_transactions macro in SAS® Anti-Money Laundering does not generate triggering transactions |
A1I001 |
| 58745 | You might encounter slow performance when you import scenarios using the Scenario Administrator in SAS® Anti-Money Laundering |
A1I001 |
| 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 |
A1I001 |
| 58749 | You might encounter slow performance when you import rules and rule groups using the Scenario Manager in SAS® Customer Due Diligence |
A1I001 |
| 58750 | All relationships associated with a party are deleted after you run the Integrated Event Management (IEM) process in SAS® Anti-Money Laundering |
A1I001 |
| 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 |
A1I001 |
| 58868 | ALERT - The party number for an external party alert is blank in the FSK_ALERT database table in SAS® Anti-Money Laundering |
A1I001 |
| 58869 | Aggregated transaction totals include amounts that are not from triggering transactions in SAS® Anti-Money Laundering |
A1I001 |
| 58870 | Importing scenarios in the SAS® Anti-Money Laundering web application takes a long time to complete |
A1I001 |
| 58883 | You encounter a "unique constraint (FCFKC.PK_RISK_ASMNT) violated" error when running the risk assessment process in SAS® Anti-Money Laundering |
A1I001 |
| 58898 | SAS® Anti-Money Laundering generates entity history code containing special characters that cause subsequent macros to fail |
A1I001 |
| 58905 | The fcf_rc_get_entity_score_info.sas macro in SAS® Anti-Money Laundering takes a long time to complete |
A1I001 |
| 58906 | The Integrated Event Management macros in SAS® Anti-Money Laundering perform slowly |
A1I001 |
| 58907 | Risk assessments that do not match any routing rules are not displayed in SAS® Anti-Money Laundering |
A1I001 |
| 58913 | The risk assessment process in SAS® Anti-Money Laundering fails with "variables are not properly sorted on data set WORK._TEMP_PARTY_DIM" error |
A1I001 |
| 58925 | Subjects and Incidents are incorrectly matched based on Type, Category, and Subcategory using Integrated Event Management |
A1I001 |
| 58927 | Risk-factor-only alerts are not generated when you run the alert generation process in SAS® Anti-Money Laundering |
A1I001 |
| 51185 | A macro exists in SAS Anti-Money Laundering that enables you to display the current release and the latest hot-fix that is applied |
A1I002 |
| 59446 | The %fcf_replicate_transaction macro fails while processing transaction type alerts during the alert generation process in SAS® Anti-Money Laundering |
A1I002 |
| 59453 | NATIONAL_ID field in PARTY_LIVE table is not populated after you run Integrated Event Management macros in SAS® Anti-Money Laundering |
A1I002 |
| 59454 | The alert generation process in SAS® Anti-Money Laundering might perform slowly when copying transactions for alerts entities |
A1I002 |
| 59455 | %fcf_agp_codegen incorrectly applies user-specified scenario overrides and causes the alert generation process to fail in SAS® Anti-Money Laundering |
A1I002 |
| 60617 | You see a "Subject identification type contains an invalid code" error in a FinCEN response file for a report generated by SAS® Anti-Money Laundering |
A1I003 |
| 60778 | Account currency information is not displayed on the Alert Details page and the Account Details tab in SAS® Anti-Money Laundering |
A1I003 |
| 60786 | Scenario information is not displayed on the Alert Details page when you do not have access to Scenario Administrator in SAS® Anti-Money Laundering |
A1I003 |
| 59069 | The alert generation process in SAS® Anti-Money Laundering fails with a "more positional parameters found than defined" error |
A1I003 |
| 60810 | The alert generation process in SAS® Anti-Money Laundering fails with the error "by variables are not properly sorted on data set WORK.SCENROUTE" |
A1I003 |
| 60812 | Transaction dimension data is not replicated during the alert generation process for external party alerts in SAS® Anti-Money Laundering |
A1I003 |
| 61929 | Improvements in regulatory reporting for SAS® Enterprise Case Management and SAS® Anti-Money Laundering |
A1I004 |
| 62042 | The SAS® Anti-Money Laundering case print preview does not show data on some tabs even though data shows on the same tabs within the web application |
A1I004 |
| 62040 | Scenarios within a routing group are not included in SAS® Anti-Money Laundering alert generation processing |
A1I004 |
| 62043 | The industry code field is blank in a SAS® Anti-Money Laundering Suspicious Activity Report (SAR) |
A1I004 |
| 62044 | An incorrect entity risk score is used for SAS® Anti-Money Laundering customer risk ranking (CRR) risk calculation |
A1I004 |
| 62707 | SAS® Anti-Money Laundering now supports FinCEN SAR data in an XML-based file, also known as the SARX format |
A1I005 |
| NOTE: If you install this hot fix and have SAS Enterprise Case Management 6.3_M1 installed, you must also install hot fix B1Y007. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes