1. Using Pipeline Designer
  2. Managing Batches
  3. Pre-Configured Batches

Pre-Configured Batches

The application contains certain pre-configured batches that can be used to run the default data. You must create new batches to run customer-specific data.

Execute the pre-configured batches in the sequence provided in each table.

Pre-configured TM Batches

Note:

New provisioning implementations should run the batches shown in the following table. Existing customers (provisioned prior to August 31 2024) should continue to use the batches provided in Pre-configured Transaction Monitoring Batches - Existing Implementations .

Contact Oracle Support before starting the data loading process to verify which data loading strategy should be used.

Table 19-1 Pre-configured Transaction Monitoring Batches - New Provisioning Implementations

Sequence Batch Name Purpose
1 Maintentance Configures and creates table partitions for Common Staging Area and business tables.
2 Loads client data.

Note:New provisioning implementations should run the StageDataLoad and StageDataQuality batches to populate data. Existing customers (provisioned prior to August 31 2024) should continue to use AMLDataLoad.

3 AMLHolidayMasterDataLoad Loads Holiday and Non-Working day data.
4 DFCS Ingestion Loads data from staging tables to business tables.

Note: This batch must be executed AFTER the StageDataLoad and StageDataQuality batches have successfully completed without errors.

5 TMScenario Uses the data that is prepared during ingestion and executes the scenario pipelines to generate events.
6 CMIngestion Loads the data to Case Management Business tables.
7 AMLtoCaseManagement Loads Event and Business data to Case Management tables.

Table 19-2 Pre-configured Transaction Monitoring Batches - Existing Implementations

Sequence Batch Name Purpose
1 AMLDataLoad Loads client data.

Note: New provisioning implementations should run the StageDataLoad and StageDataQuality batches to populate data. Existing customers (provisioned prior to August 31 2024) should continue to use AMLDataLoad.

2 AMLHolidayMasterDataLoad Loads Holiday and Non-Working day data.
3 Ingestion Loads data from staging tables to business tables.
4 TMScenario Uses the data that is prepared during ingestion and executes the scenario pipelines to generate events.
5 CMIngestion Loads the data to Case Management Business tables.
6 AMLtoCaseManagement Loads Event and Business data to Case Management tables.

Note:

The FinancialCrimeGlobalGraph batch for Investigation Hub should be executed after the ICIJ and TM/CM batches.

Pre-configured CS Batches

Table 19-3 Pre-configured Customer Screening Batches

Sequence Batch Name Purpose
1 AMLDataLoad Loads client data.
2 Ingestion Loads data from staging tables to business tables.
3 Loads data into the search engine and creates the index.
4 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
5 Runs the matching rules and generates the events.

Note:

This is an out-of the box sample batch. You can create your own batch with specific parameters.
6 ScreeningToCaseManagement Creates cases for the alerts.

Pre-configured TF Batches

Table 19-4 Pre-configured Transaction Filtering Batches

Sequence Batch Name Purpose
1 AMLDataLoad Loads client data.
2 Ingestion Loads data from staging tables to business tables.
3 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
4 Downloads the respective advanced or private watchlist data and loads it into a search engine index.

Pre-configured KYC Batches for Deployment Initiation

Table 19-5 Pre-configured KYC Batches for Deployment Initiation

Sequence Batch Name Purpose
1 AMLDataLoad Loads client data.
2 Ingestion Loads data from staging tables to business tables.
3 KYCCustomerFullLoad Loads KYC data into the search engine and creates the index.
4 Download the respective advanced or private watchlist data and loads it into a search engine index.
5 Runs the matching rules and generates the events.

Note:

This is an out-of the box sample batch. You can create your own batch with specific parameters.
6 KYCDeploymentInitiation KYC is done for the Customers and the customers who are to be further investigated are decided.
7 CMIngestion Loads the data to Case Management Business tables.
8 KYCToCaseManagement Customers who require investigation are pushed to the Case Manager.

Pre-configured Batches for KYC Daily

Table 19-6 Pre-configured Batches for KYC Daily

Sequence Batch Name Purpose
1 AMLDataLoad Loads client data.
2 CustomerChangeLog Identifies changes in the Customer's Details. These customers are picked up for KYC.
3 Ingestion Loads data from staging tables to business tables.
4 Download the respective advanced or private watchlist data and loads it into a search engine index. If this batch has already been run once, rerunning this batch is required only if there is new Watchlist data.

Note:

If this batch has already been run once, rerunning this batch is required only if there is new Watchlist data.
5 KYCDaily KYC is done for the Customers and the customers who are to be further investigated are decided.
6 CMIngestion Loads the data to Case Management Business tables.
7 KYCToCaseManagement Customers who require investigation are pushed to the Case Manager.