4.4 Executing the ER Jobs

Before running the ER jobs, the user should ensure the following:

• Create ER Schema
• Grant Permission to ER Schema
• Add ER Schema Wallet details
• The stg_party_type_master must be populated for the FIC_MIS_DATE for the ER job to be executed.

For more information, see the Entity Resolution Use Case section in the OFS Compliance Studio Installation Guide.

Note:

You can use only one ER schema per pipelineid for each FSDF version, and the same ER schema cannot be used with other pipelineid for any ER job execution.

The input parameters for each ER job are persisted in the FCC_ER_JOB_PARAM_AUDIT table in the ER schema. The relevant database configurations from FCC_ER_CONFIG are also logged against each job execution in the same table.

You can execute the following available jobs either manually or automatically a using wrapper shell script for Entity Resolution in a specified sequence:

1. Create Index and Load the Data (ER_Create_And_Load_Data_Into_Index.sh)
2. Perform Matching (ER_Run_Bulk_Similarity_Job.sh)
3. Data Survival (ER_Run_Data_Survival_Engine.sh)
4. Load Data in FCC_ER_OUTPUT Table (ER_Run_Full_Data_Output.sh)

   Note:

   You can proceed with data movement from staging to FCDM during Load Data in FCC_ER_OUTPUT Table execution.

• Create Index and Load the Data
  
• Perform Matching
  
• Data Survival
  
• Load Data in FCC_ER_OUTPUT Table
  
• Initial Run for High Volume Data
  
• Status Codes
  The fcc_batch_run table in Compliance Studio Schema explains the status codes generated for ER jobs. See the status codes in n_run_status column for respective n_run_skey values.
• Using Wrapper Shell Script
  You can execute the following jobs automatically using wrapper shell script (Wrapper_Run_ER.sh) for Entity Resolution in a specified sequence: