 |
||
|
||
|
||
|
Return to Additional Products and Solutions | |
|
||
Hot Fix Downloads
| 211AML01 was replaced by 211AML04 |
| 211AML02 was replaced by 211AML04 |
| 211AML03 was replaced by 211AML04 |
| 211AML04 | |||
| Issue(s) Addressed : | Introduced: | ||
| SN-020657 | Russian translation updates are available for SASŪ Anti-Money Laundering | 211AML01 | |
| SN-030809 | The FIND_ALERT_NEAR_NEIGHBOR macro fails when BLTEMP=NO and an attempt is made to delete observations from the table, FSK_NN_PARTY | 211AML01 | |
| SN-020659 | Simplified Chinese translations are available for SASŪ Anti-Money Laundering 2.1.1 | 211AML02 | |
| SN-020658 | Japanese translations are available for SASŪ Anti-Money Laundering 2.1.1 | 211AML02 | |
| SN-030805 | ALERT - Saving a manual alert with an account number that is zero or less generates an invalid number error message | 211AML02 | |
| SN-033587 | Scenario SAS10009 might fail if the TRANSACTION_LIST_SIZE variable is not defined as global | 211AML03 | |
| SN-019850 | The FIND_ALERT_NEAR_NEIGHBOR.SAS macro now supports multibankapplications | 211AML03 | |
| SN-019544 | The alert generation process might have problems handling numeric formats that are not set to the BEST32. format | 211AML03 | |
| SN-019541 | The code that triggers transactions in SAS® Anti-Money Laundering failswhen the transaction key is larger than 8. format | 211AML03 | |
| SN-033400 | The promote_scenarios macro might cause an integrity constraint violation | 211AML03 | |
| SN-019589 | PUT_AML_ERROR.SAS does not display hot fix information in error messages | 211AML03 | |
| SN-019600 | The version number in the SASŪ Anti-Money Laundering Help system and About page is not correct | 211AML03 | |
| SN-019555 | The Scenario Administrator in SASŪ Anti-Money Laundering 2.1 might fail to promote a large list of scenarios | 211AML03 | |
| SN-019848 | The GET_ENTITY_INFO macro in SASŪ Anti-Money Laundering fails on execution | 211AML03 | |
| SN-019670 | The program FIND_ALERT_NEAR_NEIGHBORS.SAS uses the incorrect schema tocreate the WORK.FSK_NN_PARTY table | 211AML03 | |
| SN-019672 | The SEND_ALERT_REMINDER macro generates an incorrect SYMBOLGEN message | 211AML03 | |
| SN-019673 | The BUILD_MATCH_CODES macro in SASŪ Anti-Money Laundering 2.1 is not building match codes for mailing addresses | 211AML03 | |
| SN-020025 | User interface advanced query generates a data type mismatch error | 211AML03 | |
| SN-019845 | Filtering occurs on an incorrect risk score in SASŪ Anti-Money Laundering 2.1 | 211AML03 | |
| SN-020057 | The APPEND procedure fails when you run the ADD_HISTORIC_TARGET module | 211AML03 | |
| SN-034848 | A sort error might occur in the OWNER_REPORT macro when there is a blank USER_LONG_ID field | 211AML03 | |
| SN-019880 | Put the correct SASŪ Anti-Money Laundering version number in SASML.WAR's manifest file | 211AML03 | |
| SN-020027 | FIND_ALERT_NEAR_NEIGHBOR module might generate an error if 0 rows or 0unsupressed alerts are returned from the input data set | 211AML03 | |
| SN-033274 | The Bayes reports do not display the source of the metrics used to generate the report | 211AML03 | |
| SN-034851 | ALERT - Invalid results might occur due to the GETRUNDATE macro not checking for negative values in the business_day_count field of the job calendar table | 211AML03 | |
| SN-033278 | Some scenarios might truncate party, account, or branch numbers when the sourced data contains blanks | 211AML03 | |
| SN-033532 | Using the replicateTransactions macro to specify which date key to use for table replication | 211AML03 | |
| SN-020671 | Risk factor scenarios SAS10023 and SAS10024 may produce incorrectresults if the number of months parameter for the scenarios is greaterthan the number of months available in the profile data sets. | 211AML03 | |
| SN-033280 | Scenarios SAS10023 and SAS10024 calculate the wrong risk factors when the number of months requested is greater than number of profile months | 211AML03 | |
| SN-033287 | Scenario SAS10009 is filling up the transaction save area with duplicate triggering transactions | 211AML03 | |
| SN-033522 | Scenarios might generate erroneous alerts due to duplicates in the alert list | 211AML03 | |
| SN-033540 | Scenario SAS10015 incorrectly compares debit count to credit threshold | 211AML03 | |
| SN-033299 | Overlay of the axis labels might occur in the monthly and weekly trend reports | 211AML03 | |
| SN-033586 | The daily aggregate total values for scenario SAS10020 are larger than expected | 211AML03 | |
| SN-034855 | Localization problems with the Anti-Money Laundering Active Alert Ownership and Activity report. | 211AML03 | |
| SN-034832 | OBSOLETE CODE USED FOR EVENT_CODE_VALUE IN ALERT_AGE_REPORT MACRO | 211AML03 | |
| SN-033308 | Scenarios SAS10005 and SAS10007 are testing for Currency Transation Reports that are greater than, or equal, to $10,000 | 211AML03 | |
| SN-034517 | Pages are still available for viewing after logging out of the SASŪ Anti-Money Laundering Investigation client | 211AML03 | |
| SN-033475 | The RISKRANKING module might produce unexpected results if the any character other than 'Y' is entered for the RISKONLY parameter | 211AML03 | |
| SN-034565 | The party_watchlist_header code in SASŪ Anti-Money Laundering and SASŪ Money Laundering Detection might generate a character length-exceeded error | 211AML03 | |
| SN-035316 | DBCS characters in the SAS® Anti-Money Laundering Investigation UI are not translating correctly | 211AML04 | |
| SN-035317 | A NullPointerException error occurs in the SASŪ Anti-Money Laundering query output window when Rows per Page is modified | 211AML04 | |
| SN-034454 | The SASŪ Anti-Money Laundering Investigation user interface might generate errors due to the missing SASAML.BROWSER.CACHE property | 211AML04 | |
| SN-035319 | In SASŪ Anti-Money Laundering, the Customer Names Query generates a duplicate window when the query is empty | 211AML04 | |
| SN-035321 | In SASŪ Anti-Money Laundering, the "more information about this alert" link on the Transaction Details page returns an empty result set | 211AML04 | |
| Windows (English) | Released: Apr 2009 | ||
| Install Instructions: 211AML04wn.pdf | |||
| Download: 211AML04 for Windows (file size: 53.1M) | |||
|
ATTENTION: 211AML04 is also available for the following languages: Arabic, Simplified Chinese, Japanese, Korean, Russian, Spanish |
|||
| HPUX 64bit (English) | Released: Apr 2009 | ||
| Install Instructions: 211AML04h6.pdf | |||
| Download: 211AML04 for HPUX 64bit (file size: 52.4M) | |||
|
ATTENTION: 211AML04 is also available for the following languages: Arabic, Simplified Chinese, Japanese, Korean, Russian, Spanish |
|||
| Solaris 64bit (English) | Released: Apr 2009 | ||
| Install Instructions: 211AML04s6.pdf | |||
| Download: 211AML04 for Solaris 64bit (file size: 52.4M) | |||
|
ATTENTION: 211AML04 is also available for the following languages: Arabic, Simplified Chinese, Japanese, Korean, Russian, Spanish |
|||
| AIX 64bit (English) | Released: Apr 2009 | ||
| Install Instructions: 211AML04r6.pdf | |||
| Download: 211AML04 for AIX 64bit (file size: 52.4M) | |||
|
ATTENTION: 211AML04 is also available for the following languages: Arabic, Simplified Chinese, Japanese, Korean, Russian, Spanish |
|||
| Linux (English) | Released: Apr 2009 | ||
| Install Instructions: 211AML04lx.pdf | |||
| Download: 211AML04 for Linux (file size: 52.3M) | |||
|
ATTENTION: 211AML04 is also available for the following languages: Arabic, Simplified Chinese, Japanese, Korean, Russian, Spanish |
|||
|
| Top ^ |
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 tradema rks or trademarks of their respective companies.