SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 20077: Incorrect transaction counts are returned for Account, Customer, and Household in the All Available Alerts tab

DetailsHotfixAboutRate It

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

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Anti-Money Laundering Alert Generation ServerMicrosoft Windows XP Professional2.12.29.1 TS1M3 SP4
Microsoft Windows NT Workstation2.12.29.1 TS1M3 SP4
Microsoft Windows 2000 Server2.12.29.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server2.12.29.1 TS1M3 SP4
Microsoft Windows 2000 Advanced Server2.12.29.1 TS1M3 SP4
Linux2.12.29.1 TS1M3 SP4
Solaris2.12.29.1 TS1M3 SP4
64-bit Enabled Solaris2.12.29.1 TS1M3 SP4
Microsoft Windows 2000 Professional2.12.29.1 TS1M3 SP4
64-bit Enabled AIX2.12.29.1 TS1M3 SP4
AIX2.12.29.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.