|
|
|
|
|
|
|
|
Hot Fix Downloads
| 14MLD01 was replaced by 14MLD02 |
| 14MLD02 | |||
| Issue(s) Addressed : | Introduced: | ||
| SN-017631 | Possible 'ERROR: Read Access Violation' in watch list processing withSAS Money Laundering Detection | 14MLD01 | |
| SN-016736 | Unable to print a hard copy of a SAR form from SAS� Money LaunderingDetection | 14MLD01 | |
| SN-016752 | FSK_ALERT_EVENT.ALERT_ID incorrectly populated with the SAR_ID in SAS�Money Laundering Detection | 14MLD01 | |
| SN-016753 | A corrected SAR in SAS� Money Laundering Detection does not have the"corrected SAR" checkbox automatically filled in | 14MLD01 | |
| SN-016733 | autoclt.sas not included in the media for SAS� Money Laundering Detection | 14MLD01 | |
| SN-016734 | Scenario Administrator online help location for SAS� Money LaunderingDetection is incorrect | 14MLD01 | |
| SN-016754 | Details frame counters are not disabled during "View All Rows" withinSAS� Money Laundering Detection | 14MLD01 | |
| SN-016731 | SAS� Money Laundering Detection fsmsolution_check returns incorrectresults causing scenario and risk factor reports to fail | 14MLD01 | |
| SN-016735 | ALERT - Unable to add new scenarios to SAS Money Laundering Detection | 14MLD01 | |
| SN-016755 | ALERT - Unable to add events to SAS� Money Laundering Detection investigationuser interface | 14MLD01 | |
| SN-016723 | SAS Money Laundering Detection watch list processing scenarios requiremore than 2 GB of memory and produce out of memory errors | 14MLD01 | |
| SN-016756 | ALERT - Problems in SAS� Money Laundering Detection Advanced Query security | 14MLD01 | |
| SN-016732 | Performance issues within SAS� Money Laundering Detection due toincorrect indexes | 14MLD01 | |
| SN-016757 | SAS� Money Laundering Detection User Administrator is not correctlyrecreating the FSK_USER and FSK_USER_ADMIN tables | 14MLD01 | |
| SN-016758 | Use caution when adding a user and then updating privileges within SAS�Money Laundering Detection | 14MLD01 | |
| SN-017110 | Memory restrictions of 2 GB prevent processing more than 2.7 millionaccounts or customers within SAS� Money Laundering Detection | 14MLD01 | |
| SN-018676 | SAS� Money Laundering Detection Risk_Factor_Details macro missingtriggering values text | 14MLD01 | |
| SN-018670 | SAS� program party_watchlist_header.sas incorrectly named in twolocations within SAS� Money Laundering Detection | 14MLD01 | |
| SN-018675 | SAS� Money Laundering Detection install updates for detection.js andreport_tree.htm documentation | 14MLD01 | |
| SN-018680 | SAS� Money Laundering Detection Transaction_View posted date andsecondary account name logic are both incorrect | 14MLD01 | |
| SN-018684 | Display problems in the SAS� Money Laundering Detection Customers DetailsScreen | 14MLD01 | |
| SN-018681 | The SAS� Money Laundering Detection Investigation UI is unable to createa manual alert | 14MLD01 | |
| SN-018672 | Household information not supported in SAS� Money Laundering Detection1.4 | 14MLD01 | |
| SN-018683 | The module party_account_bridge.sas may produce duplicate records withinSAS� Money Laundering Detection | 14MLD01 | |
| SN-018664 | ALERT - Party transactions prep file is missing columns within SAS� MoneyLaundering Detection | 14MLD01 | |
| SN-018685 | Message "ERROR: Format $sarstat. is incorrect for variable SAR_STATUS"occurs within SAS� Money Laundering Detection | 14MLD01 | |
| SN-034986 | The LOAD_ADDRESS_BOOK.SAS macro generates error messages in the log when executed if the SASMAIL.CSV file is missing | 14MLD02 | |
| SN-034798 | The Export function to a CSV file does not replace or append to an existing CSV file | 14MLD02 | |
| SN-034799 | Suspicious Actvity Report suspect work and phone numbers are swapped when displayed in the SAS� Money Laundering Detection investigation client | 14MLD02 | |
| SN-034182 | ALERT - The load_core macro fails when trying to invoke the data quality server routine when the data quality server is not licensed | 14MLD02 | |
| SN-034446 | Custom user-interface parameters, SYSADMIN and NUMALERTCOLUMNS, are missing in AUTOCLT.SAS | 14MLD02 | |
| SN-035036 | The UPDATE_REPORT_OUTPUT_STYLES macro generates an error when it is called | 14MLD02 | |
| SN-035037 | A "No Transactions" message might be displayed when drilling down ona party transaction alert | 14MLD02 | |
| SN-034800 | When closing alerts, performance decreases as the FSK_ALERT table increases in size | 14MLD02 | |
| SN-035084 | The POST macro stub call incorrectly invokes the PRE macro stub code | 14MLD02 | |
| SN-035085 | The LAST_SUSP_ACTV_RPT_DATE column is being dropped from the MST_DIM.FSC_PARTY_DIM table | 14MLD02 | |
| SN-034852 | Truncation of phone numbers occurs in the SAR data model | 14MLD02 | |
| SN-034565 | The party_watchlist_header code in SAS� Anti-Money Laundering and SAS� Money Laundering Detection might generate a character length-exceeded error | 14MLD02 | |
| SN-035087 | Numeric data within scenario messages in SAS� Money Laundering Detection is truncated | 14MLD02 | |
| SN-035091 | Erroneous results can occur when large values exist in numeric fields within SAS� Money Laundering Detection scenarios | 14MLD02 | |
| SN-035105 | False alerts occur when a scenario is executed | 14MLD02 | |
| SN-035106 | Rounding errors appear in the SAS log during execution of scenarios | 14MLD02 | |
| SN-035170 | SAS� Money Laundering Detection does not support large surrogate key values | 14MLD02 | |
| SN-035193 | Scenario SAS10004 only counts inquiries for parameters Q10004_LIMIT_1 - Q10004_LIMIT_3 for 29 days | 14MLD02 | |
| SN-035195 | Scenario SAS10025 calculates missing or zero values when the field currency_amount is zero or missing | 14MLD02 | |
| SN-035289 | SAS® Money Laundering Detection account_transaction_prep program might truncate columns within the account transaction prep table | 14MLD02 | |
| SN-034448 | Alert Generation macros do not support large surrogate keys | 14MLD02 | |
| SN-035222 | Build_party_match_codes module attempts to build name match codes for both organizations and individuals | 14MLD02 | |
| SN-035223 | The BUILD_PARTY_MATCH_CODES macro returns an error if the length of the input value exceeds 255 characters | 14MLD02 | |
| SN-035224 | The BUILD_PARTY_MATCH_CODES macro does not give you the option to suppress the building of street and mailing address match codes | 14MLD02 | |
| SN-035226 | Scenarios SAS10023 and SAS10024 will now ignore customer accounts that have less than the required months of data | 14MLD02 | |
| SN-034452 | SAS� Money Laundering Detection code uses ROLE_DESC, which degrades performance | 14MLD02 | |
| SN-035249 | The SAS� Money Laundering Detection macro DIST_ACTIVE_ALERTS_REPORT fails when there are no active alerts | 14MLD02 | |
| SN-034456 | Risk factors are not associated to alerts with a different PRIMARY_ENTITY_LEVEL_CODE | 14MLD02 | |
| SN-035260 | The account, customer, and party number fields might be truncated to 25 characters in a SAS� Money Laundering Detection advanced query | 14MLD02 | |
| SN-035261 | SAS® Money Laundering Detection truncates dollar amounts in the suspicious activity reports | 14MLD02 | |
| SN-035266 | Large surrogate keys in SAS� Money Laundering Detection scenario administrator headers might generate unexpected results and errors | 14MLD02 | |
| SN-035267 | The SAS� Money Laundering Detection investigation user interface is slow to open when there are large numbers of closed alerts | 14MLD02 | |
| SN-035329 | When sending e-mail alerts, the alert IDs might appear twice and truncated in the SAS� Money Laundering Detection popup window | 14MLD02 | |
| Windows | Released: Apr 2009 | ||
| Install Instructions: 14MLD02wn.txt | |||
| Download: 14MLD02 for Windows (file size: 2.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