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 20-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 Either DFCS Ingestion or both: 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 20-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:

From release 26.05.01 onwards, as the FinancialCrimeGlobalGraph graph batch is renamed to FinancialGraphEntityRefresh, users must rerun the FinancialGraphEntityRefresh batch with the latest MIS date the AMLToCaseManagement batch was run on to ensure that the graph loads successfully for the older cases.

Pre-configured CS Batches

Table 20-3 Day 0 - Pre-configured Customer Screening Batches - New Provisioning Implementations

Sequence Batch Name Purpose
1 Maintenance Configures and creates table partitions for Common Staging Area and business tables.

Note: If the Maintenance batch is already executed, skip this batch

2 AMLDataLoad Loads client data.

Note: If the customer data is more than 2 million on day 0, it is recommended to create a slice for Screening. For more information, see Slice Documentation.

3 DFCS Ingestion Loads data from staging tables to business tables.
4 CMIngestion Loads the data to Case Management Business tables.
5 CustomerFullLoad Loads data into the search engine and creates the index.
6 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
7 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.

Note: Execute the following batches only if created slices:
8 ScreeningToCaseManagement Creates cases for the alerts.

Table 20-4 Day 1 - Pre-configured Customer Screening Batches - New Provisioning Implementations

Sequence Batch Name Purpose
2 AMLDataLoad Loads client data.

Note: If the customer data is is more than 2 million on day 0, it is recommended to create a slice for Screening. For more information, see the Slice Documentation.

3 DFCS Ingestion Loads data from staging tables to business tables.
4 CMIngestion Loads the data to Case Management Business tables.
5 CustomerDeltaLoad Loads data into the search engine and creates the index.
6 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
7 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.
8 ScreeningToCaseManagement Creates cases for the alerts.

Table 20-5 Day 0 - Pre-configured Customer Screening Batches - Existing Implementations

Sequence Batch Name Purpose
1 Maintenance Configures and creates table partitions for Common Staging Area and business tables.

Note: If the Maintenance batch is already executed, skip this batch

2 AMLDataLoad Loads client data.

Note: If the customer data is is more than 2 million on day 0, it is recommended to create a slice for Screening. For more information, see the Slice Documentation.

3 Ingestion Loads data from staging tables to business tables.
4 CMIngestion Loads the data to Case Management Business tables.
5 CustomerFullLoad Loads data into the search engine and creates the index.
6 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
7 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.

Note: Execute the following batches only if created slices:
8 ScreeningToCaseManagement Creates cases for the alerts.

Table 20-6 Day 1 - Pre-configured Customer Screening Batches - Existing Implementations

Sequence Batch Name Purpose
2 AMLDataLoad Loads client data.

Note: If the customer data is is more than 2 million on day 0, it is recommended to create a slice for Screening. For more information, see the Slice Documentation.

3 Ingestion Loads data from staging tables to business tables.
4 CMIngestion Loads the data to Case Management Business tables.
5 CustomerDeltaLoad Loads data into the search engine and creates the index.
6 Downloads the respective advanced or private watchlist data and loads it into a search engine index.
7 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.
8 ScreeningToCaseManagement Creates cases for the alerts.

Pre-configured TF Batches

Table 20-7 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

Note:

If you do not want screening in KYC (i.e., if there is no Watchlist rule in Business Check/Algorithmic Scoring) then running batches in sequence 3,4, and 5 before the DeploymentInitiation batch is not required:
  • KYCCustomerFullLoad
  • Watchlist batches like WLOFACLoad, WLHMTLoad
  • KYCIndividualScreening
  • KYCEntityScreening

Table 20-8 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
  • KYCIndividualScreening
  • KYCEntityScreening
 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 20-9 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.