7 Batch Screening

The following diagram describes the data movement from Customer Screening to Enterprise Case Management (ECM) during the batch screening process.

Figure 7-1 Batch Screening Workflow

Figure 7-2 Batch Screening Workflow with EXTRNL_ORG table

The data movement in the workflow is as follows:

1. Data is moved from the STG_PARTY_MASTER, STG_PARTY_ADDRESS, STG_CASA, STG_LOAN_CONTRACTS, STG_PARTY_ACCOUNT_ROLE_MAP, STG_PARTY_ROLE_MAP, STG_TD_CONTRACTS, STG_TRADING_ACCOUNT, and STG_PARTY_OTHER_NAMES tables to the CUST, CUST_ADDR, ACCT, CUST_NAME and other associated customer tables using the Table-to- Table (T2T) mode.

   Data is moved from the STG_PARTY_MASTER, STG_PARTY_ADDRESS, STG_CASA, STG_LOAN_CONTRACTS, STG_PARTY_ACCOUNT_ROLE_MAP, STG_PARTY_ROLE_MAP, STG_TD_CONTRACTS, STG_TRADING_ACCOUNT, and STG_PARTY_OTHER_NAMES tables to the EXTRL_ENTITY, EXTRL_ORG, EXTRL_ORG_STG, EXTRL_ORG_ADDR, LINK_STAGE, EXTRL_ENTITY_ADDR, DERIVED_ADDRESS, ACCT, CUST_NAME and other associated customer tables using the Table-to-Table (T2T) mode. See batch screening workflow with EXTRNL_ORG table.

2. The watch list data is downloaded from the watch list-management project in EDQ. The watch list data is matched with the data in the CUST and CUST_ADDR tables in the Customer- Screening project.
3. The matches are loaded into the CS_MATCHES table and the corresponding watch list data is loaded into the CS_WATCHLIST table.
4. Data from the CS_MATCHES_HIST table is generated as alerts in the CS_ALERTS and CS_ALERTS_MATCHES tables.

   Note:

   1. The CS_MATCHES_HIST table contains all the matches made. Each time screening is run, the CS_MATCHES table is compared to the CS_MATCHES_HIST table and any new or updated matches are added to the CS_MATCHES_HIST table. This creates a new alert.
   2. Every time you run the Customer-Screening project, data is cleared from the CS_MATCHES table.
5. Data is correlated and loaded into the KDD_CASES and FCC_EVENTS tables in ECM.