Problem Note 46310: SAS® Anti-Money Laundering Riskranking macro might generate data integrity errors for risk-factor-only alerts.
The Riskranking macro might generate a data integrity error for risk-factor-only alerts. The error is due to a missing segment_id in one of the tables that is merged to Knowledge Center table FSK_ALERT_RISK_FACTOR. The FSK_ALERT_RISK_FACTOR table has a foreign key constraint (AML_CTR.FSK_ALERT_RISK_FACTOR.R_51)
on alert_id and segment_id from the FSK_ALERT table.
This constraint generates the following error in the SAS log if the segment_ids are missing in FSK_ALERT_RISK_FACTOR:
WARNING: Variable ENTITY_NUMBER has different lengths on BASE and DATA files (BASE 50 DATA 75).
NOTE: FORCE is specified, so dropping/truncating will occur.
NOTE: There were 5 observations read from the data set MST_ALER.RANKED_RISK_FACTOR_ALERTS.
NOTE: 5 observations added.
NOTE: The data set DB_KC.FSK_ALERT_RISK_FACTOR has . observations and 6 variables.
ERROR: During insert: [IBM][CLI Driver][DB2/AIX64] SQL0530N The insert or update value of the FOREIGN KEY "AML_CTR.FSK_ALERT_RISK_FACTOR.R_51" is not equal to any value of the parent key of the parent table. SQLSTATE=23503
Segment_id has been added to the temporary table in the Riskranking macro to resolve the error above.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Standard Edition | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows XP Professional | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate 32 bit | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled AIX | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled HP-UX | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
64-bit Enabled Solaris | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
HP-UX IPF | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Linux | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Linux for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
Solaris for x64 | 4.2 | 5.1 | 9.2 TS2M3 | 9.3 TS1M2 |
*
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.
The Riskranking macro might generate a data integrity error for risk-factor-only alerts. The error is due to a missing segment_id in one of the tables that is merged to Knowledge Center table FSK_ALERT_RISK_FACTOR.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2012-04-27 14:34:06 |
Date Created: | 2012-04-16 08:39:24 |