Providing software solutions since 1976


SAS Compliance Solutions 7.1

Hot Fix Downloads for 64-bit Enabled AIX

* Important changes to Hot Fixes!

A5T001 was replaced by A5T007

A5T002 was replaced by A5T007

A5T003 was replaced by A5T007

A5T004 was replaced by A5T007

A5T005 was replaced by A5T007

A5T006 was replaced by A5T007

A5T007 for 64-bit Enabled AIX
SAS Compliance Solutions 7.1
Issue(s) Addressed:Introduced:
58914 The downloaded CSV data is inconsistent with the data displayed on the Alert Details page in SASŪ Anti-Money Laundering A5T001
60039 A hot fix for SASŪ Anti-Money Laundering and SASŪ Customer Due Diligence is available A5T001
60786 Scenario information is not displayed on the Alert Details page when you do not have access to Scenario Administrator in SASŪ Anti-Money Laundering A5T001
42491 A WHERE clause containing the DATEPART() function might be incorrectly formed when passed to Teradata with SAS/ACCESSŪ Interface to Teradata A5T001
58905 The fcf_rc_get_entity_score_info.sas macro in SASŪ Anti-Money Laundering takes a long time to complete A5T001
58927 Risk-factor-only alerts are not generated when you run the alert generation process in SASŪ Anti-Money Laundering A5T001
59455 %fcf_agp_codegen incorrectly applies user-specified scenario overrides and causes the alert generation process to fail in SASŪ Anti-Money Laundering A5T001
61033 The Customer Risk Ranking score in SASŪ Anti-Money Laundering is incorrect after you rescore an updated party A5T001
51230 The "About SAS Anti-Money Laundering" button now returns the current release and latest applied hot fix or maintenance release A5T002
60219 Deploying SASŪ Compliance Solutions 7.1 with non-distributed and stand-alone SASŪ LASR Analytic Server fails in the configuration process A5T002
60245 Case status change is not reflected in audit events for cases in SASŪ Anti-Money Laundering 7.1 and SASŪ Customer Due Diligence 7.1 A5T002
60952 You can still close an alert in SASŪ Anti-Money Laundering even if you do not have that capability specified in SASŪ Management Console A5T002
60954 The alert-generation process fails and an error occurs after you create or update scenarios using the Scenario window in SASŪ Anti-Money Laundering A5T002
60957 SASŪ Anti-Money Laundering Query Service REST API does not return a JSON response according to the order specified in the query column position A5T002
60958 Graphics in the Analysis section of the customer Details window do not display the expected colors in SASŪ Anti-Money Laundering 7.1 A5T002
60967 A copied rule in the SASŪ Anti-Money Laundering Customer Due Diligence Rule Administrator is not displayed in the rule list A5T002
60974 The Suspicious Activity Report (SAR) in SASŪ Anti-Money Laundering does not display the "Type of gaming institution" and "Other (specify)" fields A5T002
61008 The CDD Review page incorrectly shows duplicate records for a rule after you edit the rule in SASŪ Customer Due Diligence A5T002
61024 Scenario Administrator in SASŪ Anti-Money Laundering limits the number of replication days to 366 A5T002
61025 Microsoft Internet Explorer renders only one half of the scoring graph in the Customer Due Diligence component of SASŪ Anti-Money Laundering A5T002
61028 External party details are not displayed on the SASŪ Anti-Money Laundering transaction details page A5T002
61029 The "Risk Factors" tab is missing from the SASŪ Anti-Money Laundering "Alert Details" page A5T002
61031 Users can route alerts, cases, and risk assessments in SASŪ Anti-Money Laundering even though they are not configured to have the capability A5T002
61032 Users can close alerts in SASŪ Anti-Money Laundering even though the software is not configured for them to have that capability A5T002
61040 The codes that you receive when you close an alert do not have a meaningful description in SASŪ Anti-Money Laundering 7.1 A5T002
61041 The account number on the SASŪ Anti-Money Laundering transaction details page is an account key value instead of an account number value A5T002
61044 The value for "Alert Age" in the list of entities on the SASŪ Anti-Money Laundering alert triage page is incorrect A5T002
61045 You can route cases that you do not own in SASŪ Anti-Money Laundering A5T002
61046 Users can access the "Risk Assessment" tab even though the software is not configured for them to have that capability A5T002
61050 Disposition values are blank when you open a closed Customer Due Diligence (CDD) review A5T002
61082 The labels that display account information of nodes in the Funds Tracker graph are not displayed correctly in SASŪ Anti-Money Laundering A5T002
61090 You cannot create a Suspicious Activity Report from a case when the subject does not have an associated account in SASŪ Anti-Money Laundering A5T002
61092 SASŪ Anti-Money Laundering does not validate the user name that you enter in the "Route to user" field if that name is defined in SASŪ metadata A5T002
61103 Adding an entity to a case in SASŪ Anti-Money Laundering results in a "Conflict when creating an object" message A5T002
61104 When you click the Reports menu in the Anti-Money Laundering Regulatory Reports folder, you see "User is not authorized to access this page" A5T002
61106 Users with "Route My Regulatory Reports for Anti-Money Laundering" capability in SASŪ Management Console can route any regulatory report A5T002
61113 A Customer Due Diligence Review cannot be saved or edited in SASŪ Anti-Money Laundering A5T002
61114 The SASŪ Anti-Money Laundering Customer Due Diligence Reviews list contains duplicate information and the total count is incorrect A5T002
61122 In SASŪ Anti Money Laundering, you can route cases from the All Available Cases list even when you are not the owner of the case A5T002
61136 The risk-classifier code value does not match the expected value in SASŪ Anti-Money Laundering A5T002
61140 Transaction names are not displayed in SASŪ Anti-Money Laundering when they contain a dot character A5T002
61141 An error occurs if you manually create a Customer Due Diligence (CDD) review that does not contain scoring data A5T002
61177 The creation time for a report is truncated (missing) in the creation date in SASŪ Anti-Money Laundering A5T002
61102 Some entities with active alerts are not listed in the Entity Triage listing after you run the alert generation process in SASŪ Anti-Money Laundering A5T002
59454 The alert generation process in SASŪ Anti-Money Laundering might perform slowly when copying transactions for alerts entities A5T002
60959 The Suspicious Activity Report (SAR) form fails to validate in SASŪ Anti-Money Laundering, even though the data is correct A5T002
60965 The Suspicious Activity Report form fails to validate when the Taxpayer Identification Number type is unknown in SASŪ Anti-Money Laundering A5T002
61085 The value for "Form of Identification for Subject Unknown" in a Suspicious Activity Report is blank in the e-file report in SASŪ Anti-Money Laundering A5T002
61097 The customer risk ranking (CRR) program fails when SASŪ Customer Due Diligence uses Microsoft SQL Server A5T002
62693 The SASŪ Compliance Solution alert-generation process fails in the FCF_REPLICATE_EXT_TRANSACTIONS.SAS macro after you apply Hot Fix A5T002 A5T003
61123 All transactions are exported to a CSV file instead of only the transactions in the SASŪ Anti-Money Laundering entity transactions list A5T004
61530 ALERT - "The maximum length of this input field has been exceeded" occurs when you enter text in "Step 5 - Narrative" in Suspicious Activity Reports A5T004
61532 The transaction summary associated with an External Party alert shows an incorrect value on the Entity Details page in SASŪ Anti-Money Laundering A5T004
61548 Search by Case results are not sorted alphabetically in SASŪ Anti-Money Laundering A5T004
61550 In SASŪ Anti-Money Laundering, when you validate a Suspicious Activity Report, an S419 error might occur A5T004
61552 The "User is not authorized to perform this action" error occurs when you attempt to view an alert in SASŪ Anti-Money Laundering A5T004
61556 The "Route" action might be incorrectly disabled or enabled in SASŪ Anti-Money Laundering 7.1 A5T004
61557 Saving a scenario in SASŪ Anti-Money Laundering results in "Scenario XXXXXX update failed" or "Other user may have changed this scenario..." errors A5T004
61569 Users without permission to view cases can still see case information when using the Search by Cases functionality in SASŪ Anti-Money Laundering A5T004
61571 In SASŪ Anti-Money Laundering, the contact information displayed in regulatory reports might be different from the information in the e-file A5T004
61574 Saving a scenario in SASŪ Anti-Money Laundering results in "Form Errors. Please correct..." or "Name must be populated and unique" errors A5T004
61575 In the SASŪ Anti-Money Laundering FinCEN Suspicious Activity Report user interface, the date range fields are populated with incorrect values A5T004
61579 You cannot edit any reviews for Customer Due Diligence even if the correct capability is enabled in the SASŪ Anti-Money Laundering metadata A5T004
61580 The Money Laundering Risk Score column shows in the Search results even if you do not select the preference in SASŪ Anti-Money Laundering A5T004
61581 "ERROR: CLI describe error...SQLSTATE=42501" occurs when you add a new business unit in SASŪ Anti-Money Laundering A5T004
61582 SASŪ Anti-Money Laundering contains security vulnerabilities A5T004
61583 SASŪ Anti-Money Laundering does not support multiple institutions in the Suspicious Activity Report A5T004
61584 Attempting to modify manual parties that are added to a SASŪ Anti-Money Laundering report fails and returns "An unexpected server error has occurred" A5T004
61585 You can edit some fields in a Suspicious Activity Report (SAR) that you do not own in SASŪ Anti-Money Laundering A5T004
61586 "Retail foreign exchange dealer" and "SRO Futures" in Suspicious Activity Reports are incorrectly mapped in SASŪ Anti-Money Laundering A5T004
61591 The alert run date in SASŪ Anti-Money Laundering always shows that the time is midnight (00:00:00) A5T004
61108 The "Could not open a connection to SQL Server..." error occurs during the compute tier post-configuration step in SASŪ Anti-Money Laundering A5T005
61660 In SASŪ Anti-Money Laundering, when you route an unsaved case, you lose either the changes that you made or the new case owner A5T005
61661 In SASŪ Anti-Money Laundering, when you set the case status to "Case Review," all the fields in the Case Details window are no longer editable A5T005
61937 The Visual Funds Tracker adds original Netflow values to entities each time you click Filter Transactions in SASŪ Anti-Money Laundering A5T005
62029 "ERROR: Variable EXECUTING_EXT_PARTY_KEY is not on file MST_PREP.CTR_EXECUTING_PTY_TRANS" occurs if you test a scenario in SASŪ Anti-Money Laundering A5T005
62043 The industry code field is blank in a SASŪ Anti-Money Laundering Suspicious Activity Report (SAR) A5T005
62044 An incorrect entity risk score is used for SASŪ Anti-Money Laundering customer risk ranking (CRR) risk calculation A5T005
62145 "ERROR: The macro CDD_MAIN_PROCESS will stop executing" occurs in SASŪ Customer Due Diligence A5T005
62159 The Add Entity to Case dialog box might not list all alerts to promote to a case in SASŪ Anti-Money Laundering A5T005
62162 Attribute scores might not be displayed in the Customer Risk Rating panel in SASŪ Customer Due Diligence A5T005
62164 The Solr index for Alert Status is not updated when a case is closed in SASŪ Anti-Money Laundering A5T005
62165 You can incorrectly create two CDD Reviews for the same customer if the CDD Review has a custom status A5T005
62166 Branch data might be incorrect when you select a branch in SASŪ Anti-Money Laundering A5T005
62168 All notes do not appear when one note has a large number of attachments in SASŪ Anti-Money Laundering A5T005
62180 SASŪ Enterprise Case Management displays an "unable to load" error when you set the value of the ECM.Policy.FinancialItemMigration property to false A5T005
62217 The "Error checking in CDD Reviews" pop-up message is displayed in SASŪ Customer Due Diligence A5T005
62219 You receive the "User name is invalid" message when you try to route an entity to a user in SASŪ Anti-Money Laundering A5T005
62220 Graphics do not appear in the Analysis section of account pages in SASŪ Anti-Money Laundering A5T005
62221 You cannot claim an entity in SASŪ Anti-Money Laundering A5T005
62227 Entities on the Entity Triage page might show inconsistent information in SASŪ Anti-Money Laundering A5T005
62228 The "One and only one prep data set variable must be selected as 'By Variable'" message might occur when you attempt to synchronize a prep data set A5T005
62229 An option to filter by a status of Closed is available on the CDD Reviews page, even though you cannot view a closed CDD Review A5T005
62230 The "FCF_REPLICATE_TRANSACTIONS is being skipped" note might occur with newly generated alerts A5T005
62231 You might see "WARNING: Apparent symbolic reference DT_AGP_ROUTE_ENTITY not resolved" in the alert generation process log A5T005
62233 The Transaction Details page might display the wrong date for a transaction A5T005
62833 The transactions_prep.sas source code does not consider scenario duration parameters in the SAS10206, SAS10220, SAS10225, and SAS10230 scenarios A5T005
51185 A macro exists in SAS Anti-Money Laundering that enables you to display the current release and the latest hot-fix that is applied A5T006
62712 The "SAR Data Validation Error Report" in SASŪ Anti-Money Laundering might not include data for the subject that is responsible for an error A5T006
62808 A filter applied on the Alert Age column on the Entity Triage page in SASŪ Anti-Money Laundering might not work A5T006
62901 Text that is entered in the "Reason" field for suppressing an alert might truncate without warning if the text is more than 255 characters in length A5T006
62919 Error messages are seen in SASŪ Anti-Money Laundering after you open either a case or an entity that has 10 or more related cases A5T006
62920 SASŪ Visual Analytics Hub does not show an access link for SASŪ Anti-Money Laundering even when the "View AML Hub Link" option is enabled A5T006
62936 Transactions that are associated with alerts generated from Watch List Entities scenarios are not displayed in SASŪ Anti-Money Laundering A5T006
62938 The Apache Ant script that is called in SASŪ Anti-Money Laundering Hot Fix A5T005 fails when it attempts to load the metadata package A5T006
62939 The SASŪ Customer Due Diligence customer risk ranking (CRR) process takes a long time to complete A5T006
62941 The preference to hide the Money Laundering Score (MLS) in SASŪ Anti-Money Laundering is not functioning properly A5T006
62954 Your selected entries on the Entity Triage page in SASŪ Anti-Money Laundering are deselected after you scroll up or down in a table A5T006
62961 The "Netflow" value in the Visual Funds Tracker in SASŪ Anti-Money Laundering is incorrect after double-clicking the "Refresh Transactions" button A5T006
62966 An External Party page does not open in SASŪ Anti-Money Laundering and you see a "Requested object not found" notice A5T006
63032 Characters from various languages might not display as expected in the SASŪ Anti-Money Laundering user interface A5T006
63034 The party name is not displayed for parent entities on the left-hand side of the "Associated Entities" section in SASŪ Anti-Money Laundering A5T006
63035 "No localised resource strings . . ." or "Rest error for resources . . . " errors occur in the SASŪ Anti-Money Laundering UI A5T006
63063 Report data is corrupted if two reports are edited in SASŪ Anti-Money Laundering in the same browser window A5T006
63066 You might see unexpected date values on the Account Details or Customer Details pages in SASŪ Anti-Money Laundering A5T006
63171 Numeric values in data-grid columns align to the left when you use the Hebrew-language setting in a browser for SASŪ Anti-Money Laundering A5T006
63173 Data in list boxes and text boxes in SASŪ Anti-Money Laundering can contain extra spaces when you use the Hebrew-language setting in a browser A5T006
63175 The "Save as grid defaults" selection does not retain filters and sort orders that you apply to data-grid columns for lists related to reports A5T006
63176 Owner assignments for alerted entities are incorrect after you apply Hot Fix A5T005 for SASŪ Anti-Money Laundering A5T006
63223 An incorrect value is in the "Entity Type" field in the "Summary" section on the CDD Reviews page of SASŪ Anti-Money Laundering A5T006
63228 The %fcf_add_to_sar90_cases compiled macro generates a warning message although there are no scenarios to activate SAR-90 cases A5T006
61077 The Apache Solr delta-import command fails and generates errors in SASŪ Anti-Money Laundering 7.1 A5T007
63080 The "Validate Report" button does not validate a postal code as expected in SASŪ Anti-Money Laundering A5T007
63081 Clicking "Validate Report" results in an unexpected "HTTP Status 500" pop-up error message when the < or > characters are used in a SARX report A5T007
63082 You receive an unexpected C10 Fatal error when you validate a SARX report in SASŪ Anti-Money Laundering A5T007
63097 You receive a transcoding error while restoring a table after you apply Hot Fix A5T006 in SASŪ Anti-Money Laundering A5T007
63099 You see a "CLI execute error . . ." regarding the FSK_RC_REPORT_ENTITY_BRIDGE table in SASŪ Anti-Money Laundering after you apply Hot Fix A5T006 A5T007
63266 You cannot route entities in SASŪ Anti-Money Laundering when you have only the Route Any Entity capability A5T007
63267 A blank value in field 94 "Filing institution contact phone number. . ." in a Suspicious Activity Report (SARX) causes an A4 Fatal FinCEN e-file error A5T007
63268 You see a warning when you append a REPLICATION_DATES table to DB_KC.fsk_REPLICATION_DATES in a relational database management system (RDBMS) A5T007
63269 The "Employee Indicator" field does not set to the default value for an entity when you want to add the entity to a case in SASŪ Anti-Money Laundering A5T007
63270 The "Date Closed" field does not update after a case is closed in SASŪ Anti-Money Laundering A5T007
63271 You click the "Activate" or "Deactivate" button for a scenario in SASŪ Anti-Money Laundering, but the "LSTUPDATE_DATE" field does not update A5T007
63272 The %FCF_RISK_RANKING macro routine might generate "WARNING: The variable acc_number in the DROP, KEEP, or RENAME list has never been referenced" A5T007
63273 The extract, transform, load (ETL) code to process the OFAC watch list might not preserve information about the place of birth A5T007
63274 A transaction reference number displays outside of the Transaction Type Information box in SASŪ Anti-Money Laundering A5T007
63346 SASŪ Anti-Money Laundering is unresponsive when you try to remove or activate an alert in a case A5T007
63347 You can create a case or add alerts to cases of an entity that you do not own in SASŪ Anti-Money Laundering A5T007
63359 You see warnings about differing field lengths for ACTUAL_VALUES_TEXT and PRIMARY_ENTITY_NUMBER variables after you run the alert generation process A5T007
63361 The Edge Type Code column always contains an "Outbound Transaction" value on the Visual Funds Tracker page in SASŪ Anti-Money Laundering A5T007
63364 The SASŪ Anti-Money Laundering alert generation process fails after the ctr_cico_ctc_header scenario header is used A5T007
63366 SAS_Server81 does not start successfully after you deploy SASŪ Anti-Money Laundering on multiple business units A5T007
63367 Duplicate transactions appear in the SASŪ Anti-Money Laundering Funds Tracker graph A5T007
63368 Transaction times in the SASŪ Anti-Money Laundering Funds Tracker transactions list are incorrect A5T007
63369 Older transactions for the same account are missing from the Funds Tracker in SASŪ Anti-Money Laundering A5T007
63393 An "Unexpected next character . . ." error occurs when an "Additional details" data grid contains column names in Hebrew in SASŪ Anti-Money Laundering A5T007
63456 Some scenarios fail to run in SASŪ Anti-Money Laundering 7.1.5 when segmentation is enabled A5T007
63528 ALERT - The web application does not display anything other than errors or blank web pages in SASŪ Anti-Money Laundering when Hot Fix A5T007 is not installed A5T007
Released: January 22, 2019     Documentation: A5T007r6.pdf D       Download: A5T007pt.zip  
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment.
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 © 2019 SAS Institute Inc. All Rights Reserved.