Problem Note 39076: Errors occur when you use the SASĀ® Anti-Money Laundering macro FIND_ALERT_NEAR_NEIGHBORS
Errors similar to the following can occur when you use the FIND_ALERT_NEAR_NEIGHBORS macro:
ERROR: Invalid dimension specification for array acct_number. The upper bound of an array dimension is smaller than its corresponding lower bound.
ERROR: Invalid dimension specification for array ori00. The upper bound of an array dimension is smaller than its corresponding lower bound.
ERROR: Invalid dimension specification for array ori0. The upper bound of an array dimension is smaller than its corresponding lower bound.
ERROR: Invalid dimension specification for array ori1. The upper bound of an array dimension is smaller than its corresponding lower bound.
ERROR: Invalid dimension specification for array ori2. The upper bound of an array dimension is smaller than its corresponding lower bound.
. . .more error messages. . .
The macro generates these errors when the parameter input data set (inLIb.inDS) does not contain any observations or any unsuppressed alerts (where ALERT_SUPPRESSED_IND='N'.) The code in SAS Anti-Money Laundering 2.1 and 2.1.1 does not check for these conditions.
If the input data set does not contain any observations or unsuppressed alerts, the macro process is halted and the following message is displayed in the SAS log:
NOTE: AML: <Input Dataset> has 0 records or 0 active records. FIND_ALERT_NEAR_NEIGHBOR is being skipped.
Note: This problem is fixed in SAS Anti-Money Laundering 2.1.1 and later.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Linux | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled HP-UX | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled Solaris | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled AIX | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows XP Professional | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Windows Vista | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Standard Edition | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Enterprise Edition | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows NT Workstation | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Datacenter Edition | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Professional | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Server | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Advanced Server | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Datacenter Server | 2.1 | 2.1.1 | 9.1 TS1M3 SP4 | 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.
The FIND_ALERT_NEAR_NEIGHBORS macro generates errors when the passed input data set (inDS) does not contain any observations or unsuppressed alerts.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2010-04-12 10:23:01 |
Date Created: | 2010-03-18 14:08:48 |