| P31002 for HP-UX IPF |
| SAS Anti-Money Laundering 6.1_M1 |
| Issue(s) Addressed: | Introduced: |
| 51185 | Two macros are available that enable you to display the current release and the latest applied hot fix for SAS® Anti-Money Laundering |
P31001 |
| 51955 | The error "Statement is not valid or it is used out of proper order" is generated when you run macros that load data for SAS® Anti-Money Laundering |
P31001 |
| 51230 | The "About SAS Anti-Money Laundering" button now returns the current release and latest applied hot fix or maintenance release |
P31001 |
| 54120 | When you view deleted scenario details in SAS® Anti-Money Laundering, the Test Scenario tab is displayed even though it should not be |
P31001 |
| 54121 | The Risk Classifier Threshold value is not displayed on the Risk Assessment Details page in SAS® Anti-Money Laundering |
P31001 |
| 54123 | ALERT - SQL queries against a DB2 database fail in SAS® Anti-Money Laundering |
P31001 |
| 54124 | ALERT - SQL queries against an Oracle database fail in SAS® Anti-Money Laundering |
P31001 |
| 54125 | ALERT - SQL queries against a SQL Server database fail in SAS® Anti-Money Laundering |
P31001 |
| 54126 | ALERT - SQL queries against a Teradata database fail in SAS® Anti-Money Laundering |
P31001 |
| 54357 | The error "Cannot request data from" occurs when you save or open a case in SAS® Customer Due Diligence |
P31001 |
| 55162 | An error occurs when you run the risk assessment (FCF_RAP) process with Microsoft SQL Server in SAS® Anti-Money Laundering |
P31002 |
| 55664 | The fcf_iem_update_subject macro in SAS® Anti-Money Laundering does not update event information in the SAS® Enterprise Case Management database |
P31002 |
| 55746 | The risk assessment process fails with an execute error when you update an assessment date in SAS® Anti-Money Laundering |
P31002 |
| 55747 | The risk assessment process fails when you update an assessment date in SAS® Anti-Money Laundering |
P31002 |
| 54858 | The SAS® Anti-Money Laundering FCF_ROUTE.SAS macro might generate duplicate alert records when AUTOROUTE2CURRENTINVESTIGATOR is set to "true" |
P31002 |
| 54861 | The SAS® Anti-Money Laundering columns SUPPRESSION_END_DATE and OWNER_USER_ID are not updated by macro fcf_iem_post.sas |
P31002 |
| 54876 | Performance has been improved for rendering lists on the Alerts, Risk Assessments, and Case pages in the SAS Anti-Money Laundering investigation UI |
P31002 |
| 55168 | The macro %fcf_iem_fb_man_alerts_risks() does not correctly assign an entity dimension to manually created alerts in SAS® Anti-Money Laundering |
P31002 |
| 55169 | SAS® Anti-Money Laundering might not immediately close an alert in the database when you close the alert on the same day on which you created it |
P31002 |
| 55663 | The fcm_iem_update_party macro in SAS® Anti-Money Laundering does not update the PARTY_FULL_NM column in the SAS® Enterprise Case Management database |
P31002 |
| 54844 | Slow performance might occur when you display details pages in the SAS® Anti-Money Laundering investigation user interface |
P31002 |
| 55170 | SAS® Anti-Money Laundering displays the error "Failed to request data from" on the Customer Alert Details window |
P31002 |
| 55297 | The error "Failed to request data from" occurs when you view the alert details for a scenario that contains an ID greater than 2,147,483,647 |
P31002 |
| 55301 | All of the alerts are duplicated on the All Available Alerts tab in SAS® Anti-Money Laundering |
P31002 |
| 55302 | SAS® Anti-Money Laundering displays a "Tried to register widget" error in the JavaScript console when you edit a case |
P31002 |
| NOTE: If you install this hot fix, you must install hot fix R66004 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes