|
|
|
|
|
|
|
|
Hot Fix Downloads
| 21AML01 was replaced by 21AML02 |
| 21AML02 | |||
| Issue(s) Addressed : | Introduced: | ||
| SN-019541 | The REPLICATETRANSACTION macro in SASŪ Anti-Money Laundering fails when the transaction key is larger than 8. format | 21AML01 | |
| SN-034848 | A sort error might occur in the OWNER_REPORT macro when there is a blank USER_LONG_ID field | 21AML01 | |
| SN-034987 | The SEND_ALERT_REMINDER macro does not support e-mail addresses that contain special characters | 21AML01 | |
| SN-019367 | The WC_NORMALIZE_WATCH_LIST_DATA macro causes a read-access or segmentation violation for world-check processing | 21AML01 | |
| SN-019544 | The alert generation process might have problems handling numeric formats that are not set to the BEST32. format | 21AML01 | |
| SN-020671 | Risk factor scenarios SAS10023 and SAS10024 may produce incorrect results if the number of months parameter for the scenarios is greater than the number of months available in the profile data sets. | 21AML01 | |
| SN-018064 | ORA-00918 error messages surface in several places in the SASŪ Anti-Money Laundering user interface | 21AML01 | |
| SN-019397 | In SASŪ Anti-Money Laudering, INSTALL.SAS program copies !SASROOT/.../.../SASMACR.sas7bcat to !AMLROOT/custom/source | 21AML01 | |
| SN-039076 | Errors occur when you use the SASŪ Anti-Money Laundering macro FIND_ALERT_NEAR_NEIGHBORS | 21AML01 | |
| SN-019389 | A read access violation or segmentation violation occurs with WC_NORMALIZE_WATCH_LIST_DATA | 21AML01 | |
| SN-019228 | SASŪ Anti-Money Laundering dynamic URL queries might generate an error if they contain (<) or (>) symbols | 21AML01 | |
| SN-019229 | The SASŪ Anti-Money Laundering user interface provides the ability to launch external applications | 21AML01 | |
| SN-019590 | A missing sample program in SASŪ software might generate an error during execution of the install.sas program | 21AML01 | |
| SN-019591 | The sasaml.neighbor.sql query might generate an error message | 21AML01 | |
| SN-019304 | The calculation for scenario 91 in SASŪ Anti-Money Laundering is incorrect | 21AML01 | |
| SN-019306 | The DISTINCT clause in the riskranking SQL query might cause performance issues | 21AML01 | |
| SN-019341 | ALERT - An error occurs when the target FSC_PARTY_DIM record undergoes a type-2 change | 21AML01 | |
| SN-019343 | BL_TEMP=YES causes an SQLLDR error on the Microsoft Windows operating system | 21AML01 | |
| SN-020055 | The SASŪ Anti-Money Laundering client does not run on WebSphere or Weblogic servers if Java 2 security is enabled | 21AML01 | |
| SN-019361 | Single-column sorting on the Closed Alerts or the Suppressed Alerts pages removes multicolumn sorting on the Available Alerts page | 21AML01 | |
| SN-019364 | Alerts in the alert generation process are routed to logically deleted user IDs | 21AML01 | |
| SN-019366 | Records might disappear from the user interface after you upgrade to SASŪ Anti-Money Laundering 2.1 and purge the FSC_TRANSACTION_DIM table | 21AML01 | |
| SN-019368 | The SASŪ Anti-Money Laundering scenario, SAS10023, calculates the wrong average when the party profile has fewer months than requested | 21AML01 | |
| SN-019391 | Duplicate risk scores might occur in the Alert History window | 21AML01 | |
| SN-019395 | SEND_ALERT_REMINDER and NOTIFY_MANAGER modules in SASŪ Anti-Money Laundering do not support special characters in e-mail addresses | 21AML01 | |
| SN-019396 | Bypage help is added for two FINTRAC Investigation user interface windows | 21AML01 | |
| SN-019592 | The update of the Fsc_location_watch_list_dim program does not work when you delete countries | 21AML01 | |
| SN-019416 | Re-name STR bypage Help files to include name of country | 21AML01 | |
| SN-019421 | Add configuration property to enable conditional display of U.S. SAR links in SASŪ Anti-Money Laundering | 21AML01 | |
| SN-019534 | In SASŪ Anti-Money Laundering 2.1, data stored in Oracle 10G is not viewable via Apache Tomcat when you click the Near Neighbors link | 21AML01 | |
| SN-019599 | The install.sas program is missing unknown foreign key updates | 21AML01 | |
| SN-019535 | Incorrect post-processing macro name in the macro FIND_REPORT_NEAR_NEIGHBORS in SASŪ Anti-Money Laundering 2.1 | 21AML01 | |
| SN-019589 | PUT_AML_ERROR.SAS does not display hot fix information in error messages | 21AML01 | |
| SN-019600 | The version number in the SASŪ Anti-Money Laundering Help system and About page is not correct | 21AML01 | |
| SN-019537 | Image paths in the SASŪ Anti-Money Laundering 2.1 Help system should use forward slashes | 21AML01 | |
| SN-019603 | The bypage help for the SASŪ Anti-Money Laundering Custom tab uses an incorrect template | 21AML01 | |
| SN-019538 | The SASŪ Anti-Money Laundering 2.1 transaction query for the Norwegian system activity report should include trade transaction data | 21AML01 | |
| SN-019539 | .JSP program references need to be fixed for the modified Custom Tab application in the SASŪ Anti-Money Laundering Help system | 21AML01 | |
| SN-019545 | The SAVE_TRANSACTION_KEY macro might generate an error on large transaction key values | 21AML01 | |
| SN-019605 | You cannot set the number of report groups in the SASŪ Anti-Money Laundering report for Active Alerts distribution | 21AML01 | |
| SN-019552 | Hash tables for certain external-party scenarios might exceed the 2-gigabyte memory limit on the Windows operating system | 21AML01 | |
| SN-019553 | The COMBINE_ALERTS macro fails because the SQL Pass-Through code does not contain a SCHEMA parameter | 21AML01 | |
| SN-019555 | The Scenario Administrator in SASŪ Anti-Money Laundering 2.1 might fail to promote a large list of scenarios | 21AML01 | |
| SN-019662 | The Alert History window in SASŪ Anti-Money Laundering 2.1 displays an incorrect creation date | 21AML01 | |
| SN-019556 | Users need to be able to select a delimiter for exporting files in SASŪ Anti-Money Laundering 2.1 | 21AML01 | |
| SN-019557 | The CREATE_NEAR_NEIGHBOR_SETS macro in SASŪ Anti-Money Laundering 2.1 generates an error if an account number contains characters | 21AML01 | |
| SN-019663 | A transaction-details query from the All Available Transaction tab might generate an Oracle timeout error message | 21AML01 | |
| SN-019664 | Selecting the Interbank Application tab in SASŪ Anti-Money Laundering 2.1 might generate an error | 21AML01 | |
| SN-019667 | The Scenario Administrator does not allow SAS employees to use an employee SID for both SASŪ Anti-Money Laundering and SASŪ Money Laundering Detection | 21AML01 | |
| SN-019668 | An undefined catalog START_SHARE generates an error message in the Scenario Administrator when the calendar utility is invoked | 21AML01 | |
| SN-019669 | Code that extracts data and populates the Alert Regulatory Report window runs twice when it is invoked | 21AML01 | |
| SN-019848 | The GET_ENTITY_INFO macro in SASŪ Anti-Money Laundering fails on execution | 21AML01 | |
| SN-019670 | The program FIND_ALERT_NEAR_NEIGHBORS.SAS uses the incorrect schema to create the WORK.FSK_NN_PARTY table | 21AML01 | |
| SN-019672 | The SEND_ALERT_REMINDER macro generates an incorrect SYMBOLGEN message | 21AML01 | |
| SN-019673 | The BUILD_MATCH_CODES macro in SASŪ Anti-Money Laundering 2.1 is not building match codes for mailing addresses | 21AML01 | |
| SN-019674 | Column requirements (parts G and H) in SASŪ Anti-Money Laundering 2.1 are limited to 400 characters | 21AML01 | |
| SN-020025 | User interface advanced query generates a data type mismatch error | 21AML01 | |
| SN-019845 | Filtering occurs on an incorrect risk score in SASŪ Anti-Money Laundering 2.1 | 21AML01 | |
| SN-020057 | The APPEND procedure fails when you run the ADD_HISTORIC_TARGET module | 21AML01 | |
| SN-020077 | Incorrect transaction counts are returned for Account, Customer, and Household in the All Available Alerts tab | 21AML01 | |
| SN-020073 | FINTRAC SAR queries should include data from FSK_ACCOUNT_TRADE_ALERT table | 21AML01 | |
| SN-019849 | If the USER_FIELD_ID field is blank a sort order problem can occur in the OWNER_REPORT program | 21AML01 | |
| SN-019850 | The FIND_ALERT_NEAR_NEIGHBOR.SAS macro now supports multibank applications | 21AML01 | |
| SN-019880 | Put the correct SASŪ Anti-Money Laundering version number in SASML.WAR's manifest file | 21AML01 | |
| SN-020027 | FIND_ALERT_NEAR_NEIGHBOR module might generate an error if 0 rows or 0 unsupressed alerts are returned from the input data set | 21AML01 | |
| SN-019881 | Missing alert data causes errors in the owner_report module | 21AML01 | |
| SN-033587 | Scenario SAS10009 might fail if the TRANSACTION_LIST_SIZE variable is not defined as global | 21AML02 | |
| SN-033400 | The promote_scenarios macro might cause an integrity constraint violation | 21AML02 | |
| SN-033141 | The code fails when invoking the SCENARIOCODGEN macro without specifying the PRODUCT_TYPE parameter | 21AML02 | |
| SN-019665 | Numeric formats should be set to BEST32. to ensure that long surrogate keys are handled properly in SASŪ Anti-Money Laundering 2.1 | 21AML02 | |
| SN-033274 | The Bayes reports do not display the source of the metrics used to generate the report | 21AML02 | |
| 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 | 21AML02 | |
| SN-033532 | Using the replicateTransactions macro to specify which date key to use for table replication | 21AML02 | |
| SN-033280 | Scenarios SAS10023 and SAS10024 calculate the wrong risk factors when the number of months requested is greater than number of profile months | 21AML02 | |
| SN-033287 | Scenario SAS10009 is filling up the transaction save area with duplicate triggering transactions | 21AML02 | |
| SN-033522 | Scenarios might generate erroneous alerts due to duplicates in the alert list | 21AML02 | |
| SN-033540 | Scenario SAS10015 incorrectly compares debit count to credit threshold | 21AML02 | |
| SN-030805 | ALERT - Saving a manual alert with an account number that is zero or less generates an invalid number error message | 21AML02 | |
| SN-033586 | The daily aggregate total values for scenario SAS10020 are larger than expected | 21AML02 | |
| SN-034832 | OBSOLETE CODE USED FOR EVENT_CODE_VALUE IN ALERT_AGE_REPORT MACRO | 21AML02 | |
| SN-033308 | Scenarios SAS10005 and SAS10007 are testing for Currency Transation Reports that are greater than, or equal, to $10,000 | 21AML02 | |
| SN-034517 | Pages are still available for viewing after logging out of the SASŪ Anti-Money Laundering Investigation client | 21AML02 | |
| SN-033475 | The RISKRANKING module might produce unexpected results if the any character other than 'Y' is entered for the RISKONLY parameter | 21AML02 | |
| SN-034565 | The party_watchlist_header code in SASŪ Anti-Money Laundering and SASŪ Money Laundering Detection might generate a character length-exceeded error | 21AML02 | |
| SN-033480 | Missing CATNAME SOURCE.MNYUTIL (SASHELP.MNYUTIL) in START_SHARE.SAS program | 21AML02 | |
| SN-034454 | The SASŪ Anti-Money Laundering Investigation user interface might generate errors due to the missing SASAML.BROWSER.CACHE property | 21AML02 | |
| Windows | Released: Feb 2009 | ||
| Install Instructions: 21AML02wn.pdf | |||
| Download: 21AML02 for Windows (file size: 51.5M) | |||
| HPUX 64bit | Released: Feb 2009 | ||
| Install Instructions: 21AML02h6.pdf | |||
| Download: 21AML02 for HPUX 64bit (file size: 50.8M) | |||
| Solaris 64bit | Released: Feb 2009 | ||
| Install Instructions: 21AML02s6.pdf | |||
| Download: 21AML02 for Solaris 64bit (file size: 50.8M) | |||
| AIX 64bit | Released: Feb 2009 | ||
| Install Instructions: 21AML02r6.pdf | |||
| Download: 21AML02 for AIX 64bit (file size: 50.8M) | |||
| Linux | Released: Feb 2009 | ||
| Install Instructions: 21AML02lx.pdf | |||
| Download: 21AML02 for Linux (file size: 50.8M) | |||
 |
| 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