Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Scenario SAS10009, for repeated passes of the transactions, is not clearing out the list of transaction keys in the Save area for each pass. Therefore, additional transaction keys are being appended to the triggering transaction, which fills up the Save area.

Scenario SAS10009 looks for clusters of transactions that have values in similar amounts over many days. For each pass of the transactions where the result of the pass satisfies the limits set by the scenario parameters, the saved transaction keys from the field trigger_trans_keys field are saved in a temporary field. Then the transaction count is reset. The trigger_trans_keys field is then cleared out. If the scenario is triggered, the saved transaction keys are placed in the alert record.

When the scenario starts filling up the save area, the transaction key field will have only the transactions that triggered the alert. Thus, not all transactions will be analyzed.

When this occurs, the user will start to see the following messages in the log:

WARNING: AML Transaction key limit reached for SAS1009 No more transaction keys
will be saved
WARNING: AML Transaction key limit reached for SAS1009 No more transaction keys
will be saved
WARNING: AML Transaction key limit reached for SAS1009 No more transaction keys
will be saved

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Anti-Money Laundering 2.1 is available at:

A fix for this issue for SAS Anti-Money Laundering 2.1.1 is available at: