Transaction Sources
By default, scenarios can be configured to be run against a particular type of transaction (such as wire, MI, or cash) or a particular product type (such as EFT-SWIFT, EFT-ACH). For clients who wish to specify more granular transaction sources, this release supports loading client-specified transaction codes and provides the ability to filter through the Transaction Codes filter.
For OOB scenarios, this filter is not included by default. You can include this filter as part of the HLD widget in the scenario pipeline.
To support this functionality, the Load Transaction Data and Derive External Entities and Risk data pipeline has been updated, to add the V_TRXN_TYPE4_CD column to the FCC_TRXN table. In addition, the AMLTransactionSourcesDataLoad batch has been added which loads data into metadata tables that serve as transaction codes in the high-level dataset (HLD).
Increased granularity allows organizations to better detect behaviors of interest.
Steps to Enable
-
-
Copy the new version of the Load Transaction Data and Derive External Entities and Risk data pipeline and create a new Job using similar naming conventions.
-
Attach the newly created job to the existing Ingestion batch task for the changes to be reflected.
-
Populate the FCC_TRXN.V_TRXN_TYPE4_CD of the DIM_TRANS_CODE and DIM_TRANS_CODE_MLS tables with the transaction codes required for your implementation.
-
Run the AMLTransactionSourcesDataLoad batch to load the client-specified transaction codes.
-
In the HLD widget of the scenario pipeline, configure the Transaction Code from the List of Filters.