Problem Note 63456: Some scenarios fail to run in SAS® Anti-Money Laundering 7.1.5 when segmentation is enabled
 |  |  |  |  |
Hot Fix 5 (A5T006 for SAS® Compliance Solutions 7.1) provides the new scenario-segmentation functionality in SAS Anti-Money Laundering 7.1.5. The new functionality enables you to apply specific scenario parameters for each segment (customer or accounts) to every scenario.
Some scenarios fail to run successfully after segmentation is enabled with at least two segments. Here is the list of impacted scenarios:
- SAS10009—Transactions in Similar Amounts
- SAS10026—ATM Deposits at Multiple Locations
- SAS10027—ATM Withdrawals and Inquiries at Multiple Locations
- SAS10028—Multiple Branch Usage
- SAS10085A—Transactions with Either Corresponding Party on Watch List
- SAS10085B—Money Service Business (MSB) Account Transaction with External Party on Watch List
- SAS10085C—Customer Transaction with External Party on Watch List
The following errors occur in two circumstances:
- Those scenarios are tested through the SAS Anti-Money Laundering user interface (errors are in the stored process log).
- Those scenarios are run during the alert generation process (errors are in the AGP log).
Consequently, no alert is generated.
- SAS10009:
ERROR 124-185: The variable p10009_curr_trig_trans_key has already been defined.
ERROR 124-185: The variable p10009_save_trig_trans_key has already been defined.
ERROR 124-185: The variable p10009_save_trig_trans_key has already been defined.
- SAS10026:
ERROR 124-185: The variable p10026_branch_list has already been defined.
ERROR 124-185: The variable p10026_transaction_list has already been defined.
ERROR 124-185: The variable p10026_transaction_list has already been defined.
- SAS10027:
ERROR 124-185: The variable p10027_branch_list has already been defined.
ERROR 124-185: The variable p10027_transaction_list has already been defined.
ERROR 124-185: The variable p10027_transaction_list has already been defined.
- SAS10028:
ERROR 124-185: The variable p10028_branch_list has already been defined.
ERROR 124-185: The variable p10028_transaction_list has already been defined.
ERROR 124-185: The variable p10028_transaction_list has already been defined.
- SAS10085A:
ERROR 124-185: The variable p10085a_trig_trans_key has already been defined.
- SAS10085B:
ERROR 124-185: The variable p10085b_trig_trans_key has already been defined.
- SAS10085C:
ERROR 124-185: The variable p10085c_trig_trans_key has already been defined.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 7.1 | |||
| 64-bit Enabled AIX | 7.1 | |||||
| 64-bit Enabled Solaris | 7.1 | |||||
| Linux for x64 | 7.1 | |||||
A fix for this issue for SAS Compliance Solutions 7.1 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/A5T.html#63456
A new segmentation feature added in Hot Fix 5 is not supported by certain scenarios. If the scenarios SAS10009, SAS10026, SAS10027, SAS10028, SAS10085A, SAS10085B, and SAS10085C are active and segmentation is enabled, then the alert generation process fails to run.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-01-25 13:09:59 |
| Date Created: | 2019-01-08 03:02:46 |