|
|
|
|
|
|
|
|
Hot Fix Downloads
| 221AML01 was replaced by 221AML02 |
| 221AML02 | |||
| Issue(s) Addressed : | Introduced: | ||
| SN-019589 | PUT_AML_ERROR.SAS does not display hot fix information in error messages | 221AML01 | |
| SN-019600 | The version number in the SASŪ Anti-Money Laundering Help system and About page is not correct | 221AML01 | |
| SN-019880 | Put the correct SASŪ Anti-Money Laundering version number in SASML.WAR's manifest file | 221AML01 | |
| SN-035523 | Performance might be poor when issuing queries that use the Fsc_Transaction_View table in SASŪ Anti-Money Laundering | 221AML01 | |
| SN-035770 | The NOTIFY_MANAGER macro in SASŪ Anti-Money Laundering now accepts semi-colons as a delimiter type for the attachment files | 221AML01 | |
| SN-035317 | A NullPointerException error occurs in SASŪ Anti-Money Laundering query output windows when the number of rows per page is modified | 221AML01 | |
| SN-035272 | A Java exception error message might occur when selecting the link versionHistory in the Customer Account window | 221AML01 | |
| SN-035271 | The SASŪ Anti-Money Laundering alert count is displayed instead of the label "Total" in the Total Alerts By Month Report | 221AML01 | |
| SN-035339 | Duplicate scenario categories might appear in the SASŪ Anti-Money Laundering Advanced Query screen of the Investigation user interface | 221AML01 | |
| SN-035319 | In SASŪ Anti-Money Laundering, the Customer Names Query generates a duplicate window when the query is empty | 221AML01 | |
| SN-035276 | The scenario_id field in the investigation user interface of a SASŪ Anti-Money Laundering macro might be truncated | 221AML01 | |
| SN-035321 | In SASŪ Anti-Money Laundering, the "more information about this alert" link on the Transaction Details page returns an empty result set | 221AML01 | |
| SN-035279 | Tomcat is not passing national language support (NLS) characters to the SASŪ Anti-Money Laundering database | 221AML01 | |
| SN-035284 | Warning messages might appear in the log when running the FIND_ALERT_NEAR_NEIGHBOR macro in SASŪ Anti-Money Laundering | 221AML01 | |
| SN-035327 | The columns remitter_account_number and beneficiary_account_number might be truncated if their values contain two account numbers | 221AML01 | |
| SN-035772 | The PROMOTE_SCENARIOS macro in SASŪ Anti-Money Laundering might generate a constraint error when the macro is invoked twice | 221AML01 | |
| SN-036299 | A SASŪ Anti-Money Laundering risk classification macro might fail when multiple accounts have the same primary owner | 221AML01 | |
| SN-036298 | The SASŪ Anti-Money Laundering ROUTE macro might fail when running with Teradata and the macro AUTOROUTE2CURRENTINVESTIGATOR is set to 'Y' | 221AML01 | |
| SN-036297 | The SASŪ Anti-Money Laundering SENDMAIL macro truncates attachments to 256 bytes | 221AML01 | |
| SN-036296 | Profile_Analysis.sas stores the last day of the month in the LAST_ACTIVITY_DATE in the Fsc_Account_Profile_Fact table | 221AML01 | |
| SN-036293 | The SAR report fails with an error when running SASŪ Anti-Money Laundering with DB2 | 221AML01 | |
| SN-036265 | The SASŪ Anti-Money Laundering risk assessment process returns an error in the user interface when the risk_classification field contains a null value | 221AML01 | |
| SN-042931 | The ALERT_ID field is set to a scientific notation value when running the SEND_ALERT_REMINDER macro | 221AML02 | |
| SN-039077 | The SASŪ Anti-Money Laundering macro FIND_ALERTS_NEAR_NEIGHBORS generates an error if the NN_ work tables do not contain any observations | 221AML02 | |
| SN-041881 | A Java null-format exception error might occur when you delete alert comments in SASŪ Anti-Money Laundering | 221AML02 | |
| SN-041885 | An SQL exception error occurs when selecting the "All Available" tab on the Alert Details page of SASŪ Anti-Money Laundering and MySQL is the database | 221AML02 | |
| SN-041886 | The drop-down list in the SASŪ Anti-Money Laundering Scenario Administrator Advanced Routing window is not populating with column names | 221AML02 | |
| SN-041889 | SASŪ Anti-Money Laundering scenario categories are truncated in the Alert Status Category report | 221AML02 | |
| SN-041077 | A conditional statement in scenario SAS10008 might process an extra transaction day | 221AML02 | |
| SN-041101 | The promote_scenarios macro fails when you use MySQL | 221AML02 | |
| SN-041891 | With SASŪ Anti-Money Laundering, an Oracle error occurs when clicking the Alert ID link of a transaction that is listed on the All Available tab | 221AML02 | |
| Windows | Released: Feb 2011 | ||
| Install Instructions: 221AML02wn.pdf | |||
| Download: 221AML02 for Windows (file size: 81.4M) | |||
| Windows for IPF (64 bit) | Released: Feb 2011 | ||
| Install Instructions: 221AML02w6.pdf | |||
| Download: 221AML02 for Windows for IPF (64 bit) (file size: 81.4M) | |||
| HPUX 64bit | Released: Feb 2011 | ||
| Install Instructions: 221AML02h6.pdf | |||
| Download: 221AML02 for HPUX 64bit (file size: 81.4M) | |||
| Solaris 64bit | Released: Feb 2011 | ||
| Install Instructions: 221AML02s6.pdf | |||
| Download: 221AML02 for Solaris 64bit (file size: 81.4M) | |||
| AIX 64bit | Released: Feb 2011 | ||
| Install Instructions: 221AML02r6.pdf | |||
| Download: 221AML02 for AIX 64bit (file size: 81.4M) | |||
| Linux | Released: Feb 2011 | ||
| Install Instructions: 221AML02lx.pdf | |||
| Download: 221AML02 for Linux (file size: 81.4M) | |||
| HPUX for Itanium | Released: Feb 2011 | ||
| Install Instructions: 221AML02hx.pdf | |||
| Download: 221AML02 for HPUX for Itanium (file size: 81.4M) | |||
| Solaris for x64 | Released: Feb 2011 | ||
| Install Instructions: 221AML02sx.pdf | |||
| Download: 221AML02 for Solaris for x64 (file size: 81.4M) | |||
 |
| Top ^ |
PLEASE CAREFULLY READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING MATERIALS FROM THIS SITE. BY DOWNLOADING ANY MATERIALS FROM THIS SITE, YOU ARE AGREEING TO THESE TERMS.
|
You are downloading software code ("Code") which will become part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries ("the Institute"). This Code is designed to either correct an error in the Software
or to add functionality to the Software. The code is governed by the same agreement which governs the Software. If you do not have an existing agreement with the Institute governing the Software, you may not download the Code.
|
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered
trademarks or trademarks of their respective companies.
|
Copyright © 2014 SAS Institute Inc. All Rights Reserved.
|
Return to Additional Products and Solutions