support.sas.com
 
 
support.sas.com


SAS Money Laundering Detection 1.4

Hot Fix Downloads

 
14MLD01 was replaced by 14MLD02

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