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

SAS® Money Laundering Detection does not support large numeric surrogate keys. These large key values may generate errors within the alert-generation process, scenario administrator, and investigation UI.

The following are alert-generation macros that do not support large surrogate keys values:

• ACCOUNT_DIM.SAS
• ASSOCIATE_DIM.SAS
• BRANCH_DIM.SAS
• PARTY_DIM.SAS
• TRANSACTION_DIM.SAS
• SUPPRESSION.SAS
• WC_LOAD_ENTITY_WATCH_LIST.SAS
• WC_LOAD_WATCH_LIST_COUNTRY.SAS
• RISK_FACTOR_DETAILS.SAS
• BATCH_REPORTS.SAS WC_UPDATE_ENTITY_WATCH_LIST.SAS
• WC_UPDATE_WATCH_LIST_COUNTRY.SAS

The problem occurs when a large key value is stored to a SAS macro using the (best.) format. If the key is greater than 8 digits, SAS writes the value in scientific notation. This notation generates errounous results or errors, within the alert generation process, scenario administrator, and investigation UI.

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

To avoid this issue, the (best.) format has been replaced with the (best32.)format. This allows surrogate keys up to 32 digits.

For the investigation UI, the current format for the surrogate keys is (11.). This format is specified in the DDL for Core, Base SAS^®, and SAR data models. Once keys values exceed this length, the UI may generate errors or display scientific notation for these values. This format will be changed to (Best32.) in the following DDLS, sas_base_core_ddl.sas, sas_base_kc_ddl.sas, and sar_sas_ddl.sas

Note existing SAS Money Laundering Detection sites do not need to apply this updatd DDL. They should modify the Core, KC, and SAR table formats and informats of these key fields to Best 32. format.

Operating System and Release Information

A fix for this issue for SAS Money Laundering Detection 1.4 is available at: