| 211AML04 for Spanish |
| Issue(s) Addressed: |
| SN-020657 | Russian translation updates are available for SASŪ Anti-Money Laundering | 211AML01 |
| SN-030809 | The FIND_ALERT_NEAR_NEIGHBOR macro fails when BLTEMP=NO and an attempt is made to delete observations from the table, FSK_NN_PARTY | 211AML01 |
| SN-020659 | Simplified Chinese translations are available for SASŪ Anti-Money Laundering 2.1.1 | 211AML02 |
| SN-020658 | Japanese translations are available for SASŪ Anti-Money Laundering 2.1.1 | 211AML02 |
| SN-030805 | ALERT - Saving a manual alert with an account number that is zero or less generates an invalid number error message | 211AML02 |
| SN-033587 | Scenario SAS10009 might fail if the TRANSACTION_LIST_SIZE variable is not defined as global | 211AML03 |
| SN-019850 | The FIND_ALERT_NEAR_NEIGHBOR.SAS macro now supports multibankapplications | 211AML03 |
| SN-019544 | The alert generation process might have problems handling numeric formats that are not set to the BEST32. format | 211AML03 |
| SN-019541 | The code that triggers transactions in SAS® Anti-Money Laundering failswhen the transaction key is larger than 8. format | 211AML03 |
| SN-033400 | The promote_scenarios macro might cause an integrity constraint violation | 211AML03 |
| SN-019589 | PUT_AML_ERROR.SAS does not display hot fix information in error messages | 211AML03 |
| SN-019600 | The version number in the SASŪ Anti-Money Laundering Help system and About page is not correct | 211AML03 |
| SN-019555 | The Scenario Administrator in SASŪ Anti-Money Laundering 2.1 might fail to promote a large list of scenarios | 211AML03 |
| SN-019848 | The GET_ENTITY_INFO macro in SASŪ Anti-Money Laundering fails on execution | 211AML03 |
| SN-019670 | The program FIND_ALERT_NEAR_NEIGHBORS.SAS uses the incorrect schema tocreate the WORK.FSK_NN_PARTY table | 211AML03 |
| SN-019672 | The SEND_ALERT_REMINDER macro generates an incorrect SYMBOLGEN message | 211AML03 |
| SN-019673 | The BUILD_MATCH_CODES macro in SASŪ Anti-Money Laundering 2.1 is not building match codes for mailing addresses | 211AML03 |
| SN-020025 | User interface advanced query generates a data type mismatch error | 211AML03 |
| SN-019845 | Filtering occurs on an incorrect risk score in SASŪ Anti-Money Laundering 2.1 | 211AML03 |
| SN-020057 | The APPEND procedure fails when you run the ADD_HISTORIC_TARGET module | 211AML03 |
| SN-034848 | A sort error might occur in the OWNER_REPORT macro when there is a blank USER_LONG_ID field | 211AML03 |
| SN-019880 | Put the correct SASŪ Anti-Money Laundering version number in SASML.WAR's manifest file | 211AML03 |
| SN-020027 | FIND_ALERT_NEAR_NEIGHBOR module might generate an error if 0 rows or 0unsupressed alerts are returned from the input data set | 211AML03 |
| SN-033274 | The Bayes reports do not display the source of the metrics used to generate the report | 211AML03 |
| 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 | 211AML03 |
| SN-033278 | Some scenarios might truncate party, account, or branch numbers when the sourced data contains blanks | 211AML03 |
| SN-033532 | Using the replicateTransactions macro to specify which date key to use for table replication | 211AML03 |
| SN-020671 | Risk factor scenarios SAS10023 and SAS10024 may produce incorrectresults if the number of months parameter for the scenarios is greaterthan the number of months available in the profile data sets. | 211AML03 |
| SN-033280 | Scenarios SAS10023 and SAS10024 calculate the wrong risk factors when the number of months requested is greater than number of profile months | 211AML03 |
| SN-033287 | Scenario SAS10009 is filling up the transaction save area with duplicate triggering transactions | 211AML03 |
| SN-033522 | Scenarios might generate erroneous alerts due to duplicates in the alert list | 211AML03 |
| SN-033540 | Scenario SAS10015 incorrectly compares debit count to credit threshold | 211AML03 |
| SN-033299 | Overlay of the axis labels might occur in the monthly and weekly trend reports | 211AML03 |
| SN-033586 | The daily aggregate total values for scenario SAS10020 are larger than expected | 211AML03 |
| SN-034855 | Localization problems with the Anti-Money Laundering Active Alert Ownership and Activity report. | 211AML03 |
| SN-034832 | OBSOLETE CODE USED FOR EVENT_CODE_VALUE IN ALERT_AGE_REPORT MACRO | 211AML03 |
| SN-033308 | Scenarios SAS10005 and SAS10007 are testing for Currency Transation Reports that are greater than, or equal, to $10,000 | 211AML03 |
| SN-034517 | Pages are still available for viewing after logging out of the SASŪ Anti-Money Laundering Investigation client | 211AML03 |
| SN-033475 | The RISKRANKING module might produce unexpected results if the any character other than 'Y' is entered for the RISKONLY parameter | 211AML03 |
| SN-034565 | The party_watchlist_header code in SASŪ Anti-Money Laundering and SASŪ Money Laundering Detection might generate a character length-exceeded error | 211AML03 |
| SN-035316 | DBCS characters in the SAS® Anti-Money Laundering Investigation UI are not translating correctly | 211AML04 |
| SN-035317 | A NullPointerException error occurs in the SASŪ Anti-Money Laundering query output window when Rows per Page is modified | 211AML04 |
| SN-034454 | The SASŪ Anti-Money Laundering Investigation user interface might generate errors due to the missing SASAML.BROWSER.CACHE property | 211AML04 |
| SN-035319 | In SASŪ Anti-Money Laundering, the Customer Names Query generates a duplicate window when the query is empty | 211AML04 |
| SN-035321 | In SASŪ Anti-Money Laundering, the "more information about this alert" link on the Transaction Details page returns an empty result set | 211AML04 |
| |
| Windows | Released: Apr 2009 |
| Install Instructions: 211AML04wn.pdf |
| Download: 211AML04 for Windows   (file size: 51.0M) |
| |
| HPUX 64bit | Released: Apr 2009 |
| Install Instructions: 211AML04h6.pdf |
| Download: 211AML04 for HPUX 64bit   (file size: 50.0M) |
| |
| Solaris 64bit | Released: Apr 2009 |
| Install Instructions: 211AML04s6.pdf |
| Download: 211AML04 for Solaris 64bit   (file size: 50.0M) |
| |
| AIX 64bit | Released: Apr 2009 |
| Install Instructions: 211AML04r6.pdf |
| Download: 211AML04 for AIX 64bit   (file size: 50.0M) |
| |
| Linux | Released: Apr 2009 |
| Install Instructions: 211AML04lx.pdf |
| Download: 211AML04 for Linux   (file size: 50.0M) |
| 41FI05 for Spanish |
| Issue(s) Addressed: |
| SN-015893 | Locale preference read from GLOBAL profile instead of USER profile | 41FI02 |
| SN-015933 | Problems adding additional notification templates | 41FI02 |
| SN-015934 | Validation of Facts Table fails if it is loaded via ETL Studio | 41FI02 |
| SN-015942 | Exporting 2 or more user defined dimensions will generate exception and fail | 41FI02 |
| SN-015913 | Alert notifications not sent when sender email address has no domain name | 41FI02 |
| SN-015965 | SAS Financial Management 4.1 support for additional languages | 41FI03 |
| SN-015404 | SAS Foundation EventViewer does not synchronize threads properly | 41FI03 |
| SN-016431 | Process administrator users are not displayed on certain form detail panels | 41FI04 |
| SN-016432 | Simultaneous query and budget form update will lock SAS Managed Server | 41FI04 |
| SN-016433 | Simultaneous access and refresh of a report causes it to hang | 41FI04 |
| SN-016434 | Formula may result in zeros | 41FI04 |
| SN-016435 | Poor performance with rendering formulas | 41FI04 |
| SN-016437 | Double byte characters displayed as garbage characters when exported to Excel | 41FI04 |
| SN-016436 | Double Byte Character Sets characters cannot be used in formulas | 41FI04 |
| SN-016438 | Formula processing produces exception and red cells in Excel | 41FI04 |
| SN-016479 | Poor performance with formulas using certain function | 41FI04 |
| SN-016480 | Formulas with incorrect syntax are validated and compiled incorrectly. | 41FI04 |
| SN-016481 | PRATE function may produce erroneous results | 41FI04 |
| SN-016484 | Cycle history detail report displays garbage | 41FI04 |
| SN-016487 | Contributing data records report is incomplete in some situations | 41FI04 |
| SN-016490 | Formula calculation sequence is in reverse order | 41FI04 |
| SN-016492 | Spread action on data entry form does not work from the menu | 41FI04 |
| SN-016494 | Enhancements needed for member labels dialogue | 41FI04 |
| SN-016495 | Solutions Add-In for Excel is utilizing too much CPU | 41FI04 |
| SN-016496 | Excel form may not open when launched from the Portal | 41FI04 |
| SN-016497 | Performance issues due to automatic table refreshing | 41FI04 |
| SN-016498 | Poor report performance when there are a large number of linked dimensions | 41FI04 |
| SN-016464 | SAS Financial Management customers may have problems deleting KPI projects | 41FI04 |
| SN-016465 | Product not licensed message when adding a Performance Dashboard Portlet to Portal | 41FI04 |
| SN-016470 | SSL Support for SAS 9.1.3 Solutions improved | 41FI04 |
| SN-017215 | Performance issues in forms when cells contain formulas | 41FI05 |
| SN-017216 | Delay when opening SelectSlicerMember dialog | 41FI05 |
| SN-017217 | Invalid cast exception may be generated when opening forms | 41FI05 |
| SN-017218 | Excel add-in saves temporary files in last folder opened | 41FI05 |
| SN-017219 | Reports shared as static take longer to complete | 41FI05 |
| SN-017220 | Performance improvements made to closing of Excel Add-In | 41FI05 |
| SN-017221 | Settings for copied tables are not maintained | 41FI05 |
| SN-017222 | CDA table with Account on the slicer does not render | 41FI05 |
| SN-017223 | Account dimension subset collapses when modified | 41FI05 |
| SN-017224 | Unable to open reports from the portal when running Windows 2003 | 41FI05 |
| SN-017244 | Inserting a project view into Microsoft Word or Micrsoft Excel may cause problems with DBCS characters | 41FI05 |
| SN-017272 | Updating slicer values does not work when only one value is used | 41FI05 |
| SN-017273 | Right mouse clicking on Time dimension value increases CPU usage to 100% | 41FI05 |
| SN-017274 | Default value for "Apply linked dimensions filter" flag is set to ON | 41FI05 |
| SN-017275 | Linked dimensions checkbox does not exclude all crossings | 41FI05 |
| SN-017268 | Out of memory condition may occur when opening a series of forms from a formset | 41FI05 |
| SN-017277 | Balancing rules may treat foreign currency amounts as zero | 41FI05 |
| SN-017278 | Balance account roll-ups may be double counted | 41FI05 |
| SN-017279 | Java exception when sending system status report from the Administration Portlet | 41FI05 |
| SN-017280 | WARNING: ADJUSTMENTS SHOULD BE POSTED is issued erroneously | 41FI05 |
| SN-017281 | Java exception when copying an ownership rule between models | 41FI05 |
| SN-017244 | Inserting a project view into Microsoft Word or Micrsoft Excel may cause problems with DBCS characters | 41FI05 |
| SN-017276 | Problems with un-available members | 41FI05 |
| |
| This hot fix can be downloaded from the SAS Financial Management Solutions 4.1 Hot Fix Download Page. |
| 21SP05 for Spanish |
| Issue(s) Addressed: |
| SN-015780 | Strategic Performance Management 2.1 security prevents batch processes from executing a calculate process | 21SP01 |
| SN-015781 | Deleting a diagram in Strategic Performance Managment 2.1 causes non-element based items to be removed from other diagrams | 21SP01 |
| SN-015782 | Problems with hyperlinks between diagrams in Strategic Performance Management 2.1 | 21SP01 |
| SN-015893 | Locale preference read from GLOBAL profile instead of USER profile | 21SP02 |
| SN-015913 | Alert notifications not sent when sender email address has no domain name | 21SP02 |
| SN-015933 | Problems adding additional notification templates | 21SP02 |
| SN-015934 | Validation of Facts Table fails if it is loaded via ETL Studio | 21SP02 |
| SN-015931 | Alerts not showing up in Strategic Performance Management | 21SP02 |
| SN-015964 | SAS Strategic Performance Management 2.1 support for additional languages | 21SP03 |
| SN-015404 | SAS Foundation EventViewer does not synchronize threads properly | 21SP03 |
| SN-016366 | Copying a scorecard includes all properties | 21SP04 |
| SN-016439 | NullPointerException when selecting a measure in Strategic Performance Management | 21SP04 |
| SN-016441 | Strategic Performance Management project options 'Current Date' selection reset | 21SP04 |
| SN-016444 | Scorecards/Reorder may not correctly reorder the scorecards | 21SP04 |
| SN-016448 | Changing a date and hitting enter may cause a 404 Error in Aggregate View | 21SP04 |
| SN-016462 | Setting the default diagram in project options will always display the first diagram | 21SP04 |
| SN-016463 | Changing a date and hitting enter may not correctly set the date in diagrams | 21SP04 |
| SN-016464 | SAS Financial Management customers may have problems deleting KPI projects | 21SP04 |
| SN-016465 | Product not licensed message when adding a Performance Dashboard Portlet to Portal | 21SP04 |
| SN-016470 | SSL Support for SAS 9.1.3 Solutions improved | 21SP04 |
| SN-016365 | Importing a Strategic Performance Management Project may generate errors | 21SP04 |
| SN-017009 | Problem exporting Strategic Performance Management project with non-ASCII language characters | 21SP05 |
| SN-017086 | "ERROR: [Formula] Fail to execute formula id=XXXX ..." returned importing project | 21SP05 |
| SN-017090 | Elements with different time period definitions may cause selection lists to be empty | 21SP05 |
| SN-017091 | Thai language characters may not be correctly aligned in diagrams | 21SP05 |
| SN-017092 | Korean characters do not display correctly on "Comment Edit" page | 21SP05 |
| SN-017093 | Strategic Performance Management may not display negative percentages as desired on non-United States Regional Settings | 21SP05 |
| SN-017094 | Small numbers may display in scientific notation on data entry forms | 21SP05 |
| SN-017095 | SAS Strategic Performance Management 2.1 does not have Print Preview functionality | 21SP05 |
| SN-017096 | Unselecting "Show Values" may cause diagram to be unusable | 21SP05 |
| |
| This hot fix can be downloaded from the SAS Strategic Performance Management 2.1 Hot Fix Download Page. |