The more information about this alert link on the Transaction Details page returns an empty result set if the transaction been rolled off the Core and into the Knowledge Center. This happens because the JSP code for the Transaction Details page is calling the transactionDim query in the metadata.

This query pulls transactional data only from the Core, not the Knowledge Center. To resolve this issue, create a new view in the metadata tables, TransactionAll, which pulls data from the Core and Knowledge Center tables.

The following steps will need to be taken to define the new view.

1. In a RDBMS client session, run the following INSERT statement on the FSK_UI_TABLE table:
   
   insert into fsk_ui_table values ('transactionAll','(select transaction_key, date_key, transaction_reference_number, transaction_description, security_name, deal_number from fsc_transaction_dim union select distinct transaction_key, date_key, transaction_reference_number, transaction_description, security_name, deal_number from fsk_transaction_alert) ','Transaction','CTR','BAS','Y');
2. In the same client session, run the following INSERT statement on the FSK_UI_COLUMN table:
   insert into fsk_ui_column values ('transactionAll','transactionKey','generalInformation','transaction_key','Trans action Key',100,'NUM',null,'LIT','EXT',1,'Y',null,null,null); insert into fsk_ui_column values ('transactionAll','dateKey','generalInformation','date_key','Date',200,'MDY',nul l,'LIT','LIT',1,'Y',null,null,null); insert into fsk_ui_column values ('transactionAll','transactionReferenceNumber','generalInformation','transaction _reference_number','Transaction Reference Number',201,'STR',null,'LIT','LIT',0,'Y',null,null,null); insert into fsk_ui_column values ('transactionAll','securityName','generalInformation','security_name','Security Name',210,'STR',null,'BAS','BAS',0,'Y',null,null,null); insert into fsk_ui_column values ('transactionAll','dealNumber','generalInformation','deal_number','Deal Number',220,'STR',null,'BAS','BAS',0,'Y',null,null,null); insert into fsk_ui_column values ('transactionAll','transactionDescription','generalInformation','transaction_des cription','Transaction Description',900,'STR',null,'BAS','BAS',0,'Y',null,null,null);
3. Edit the UIMetadataResources.properties file and add the following line:
   transactionAll.txt=Transaction All

Operating System and Release Information

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

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