The replicateTransactions macro now has a date_key parameter that enables you to choose the date key to use for replication. The parameters and their default values for %replicateTransactions are:

• routedAlertLib is the SAS^® library containing the data set output from the route module.
• routedAlertTable is the output data set from the route module.
• coreFactLib is the SAS library pointing to the Core database.
• coreFactTable is the name of the fact table being replicated from the Core database.
• kcFactLib is the SAS library pointing to the Knowledge Center database.
• kcFactTable is the name of the target replication fact table in the Knowledge Center database.
• triggeringTransLib is the SAS library that contains the triggering transactions data set.
• triggeringTransTable is the SAS data set that contains the triggering transaction keys generated from scenario execution and combine_alerts.
• date_key is the name of the "date_key" column used when replicating fact tables. The default column is DATE_KEY; this value can be replaced with another date key. For example, for FSC_ACCOUNT_TRADE_FACT table the date_key parameter would be set to TRADE_DATE_KEY.
• bl_temp is an option that indicates YES or NO to using bulk loading of the temporary database tables that are loaded to improve performance. If set to YES, the default bulk load options(TRUNCATE/REPLACE) are set by the modules and the temporary database tables are bulkloaded. If set to NO, the temprorary database tables use SQL DELETEs/INSERTs to perform the activity.
• bulkload is the bulk load option specific to DB2 or Oracle. At a minimum, bulkload must be set to YES. Other loading options specific to DB2 or Oracle can be included. All options should be enclosed with %str().
• bl_tempload is the bulk load option specific to DB2 or Oracle. At a minimum, TRUNCATE must be specified for Oracle and REPLACE must be specified for DB2. Other loading options specific to DB2 or Oracle can be included. All options should be enclosed with %str().

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: