Problem Note 20077: Incorrect transaction counts are returned for Account, Customer, and
Household in the All Available Alerts tab
Incorrect transaction counts are displayed in the All Available Alerts
tab. This is due to a problem with the queries that are defined in
SASAML.DB2 and SASAML.ORACLE. There is a UNION ALL join statement that
is double counting transactions in these queries:
sasaml.alerttrans.allcore.foracct.count.sql
sasaml.alerttrans.allcore.forhousehold.count.sql
sasaml.alerttrans.allcore.forparty.count.sql
The UNION ALL statement should be changed to a UNION join.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering Alert Generation Server | Microsoft Windows XP Professional | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Microsoft Windows NT Workstation | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Server | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Datacenter Server | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Advanced Server | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Linux | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Solaris | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
64-bit Enabled Solaris | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Professional | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
64-bit Enabled AIX | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
AIX | 2.1 | 2.2 | | 9.1 TS1M3 SP4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2007-05-28 00:38:56 |
Date Created: | 2007-04-30 09:27:45 |