Problem Note 36298: The SAS® Anti-Money Laundering ROUTE macro might fail when running with Teradata and the macro AUTOROUTE2CURRENTINVESTIGATOR is set to 'Y'
When it is run with Teradata, the ROUTE macro in SAS Anti-Money Laundering might fail and the following error message might appear in the log:
ERROR: Teradata prepare: Syntax error: expected something between the word
'FSK_USER' and the 'user' keyword. SQL statement was:
select alert."scenario_name", alert."alert_id", alert."primary_entity_number",
alert."primary_entity_level_code",
alert."user_id" from "BANK1KCTR"."FSK_ALERT" alert,
"BANK1KCTR"."FSK_USER" user
where (user."user_id" = alert."user_id") and
((alert."user_id" < > -1) and (UPPER(alert."alert_status_code") =
'ACT'))
and (UPPER(user."logical_delete_ind") = 'N') order
by alert."primary_entity_level_code" asc, alert."scenario_name" asc,
alert."primary_entity_number" asc, alert."alert_id" asc.
ERROR: Teradata prepare: Syntax error: expected something between the word
'FSK_USER' and the 'user' keyword. SQL statement was: select
alert."scenario_name", alert."alert_id", alert."primary_entity_number",
alert."primary_entity_level_code",
alert."user_id" from "BANK1KCTR"."FSK_ALERT" alert,
"BANK1KCTR"."FSK_USER" user where (user."user_id" = alert."user_id") and
((alert."user_id" < > -1) and (UPPER(alert."alert_status_code") = 'ACT')) and
(UPPER(user."logical_delete_ind") = 'N').
NOTE: Table WORK.INVESTIGATOR created, with 0 rows and 5 columns.
Select the Hot Fix tab in this note to access the hot fix for this issue.
The problem is due to the query above using the Teradata reserved word "USER" as a table alias. This alias has been replaced with the word "AMLUSER*" to resolve the error.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for 64-Bit Itanium-based Systems | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows XP 64-bit Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Advanced Server | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Datacenter Server | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Server | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Professional | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows NT Workstation | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Datacenter Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Enterprise Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Standard Edition | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows XP Professional | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Windows Vista | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled AIX | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled HP-UX | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
64-bit Enabled Solaris | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
HP-UX IPF | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Linux | 2.2.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Solaris for x64 | 2.2.1 | 2.2.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.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2009-08-11 13:33:45 |
Date Created: | 2009-06-19 16:18:46 |