The fcf_replicate_transactions routine that is called during the alert generation process does not replicate the transaction dimension data from the Core database table Fsc_Transaction_Dim to the Knowledge Center database table Fsk_Transaction_Alert for those transaction keys that are related to the replicated fact table for external party (EXT) alerts. 

To work around this problem, create a post process for the  fcf_replicate_transaction routine that performs the following steps:

1. Identify the list of external party alerts (primary_entity_level_code='EXT') in the Fsk_Alert table,
2. Find the transaction keys that are associated with these alerts in the Fsk_Cash_Flow_Alert table that are not found in the Fsk_Transaction_Alert table.
3. Derive the transaction data from the Fsc_Transaction_Dim table (Core database) for the identified alerts and add the associated alert IDs.
4. Load this data to the Fsk_Transaction_Alert table.

Click 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 Compliance Solutions 6.3_M1 is available at: