A.17 Parameters for Entity Resolution Job execution

This section describes parameters for job execution and cleanup for Entity Resolution.

Table A-7 Parameter for Entity Resolution

Parameter	Description	ER Job Execution	Cleanup
Pipeline ID	ER Type has taken as Pipelined ID to execute. For example, CSA_8128.	Yes	Yes
ErSchemaID	The identifier of the schema on which Entity Resolution has to be run.	Yes	Yes
ErSchemaName	Entity Resolution schema alias name.	Yes	No
MatchType	It processes the records based on the dataset, either Full Load or Delta Load.	Yes	No
LoadType	It can be either FullLoad or DeltaLoad. FullLoad: Clear all the records from the history tables and match all the records based on the fic_mis_date. DeltaLoad: Match the modified and new records with the current fic_mis_date against all the historical records.	Yes	No
FIC_MIS_DATE	The date on which the data is entered/loaded in the system in YYYYMMDD format.	Yes	Yes
FSDF VERSION	The version of FSDF for the underlying Stage tables.	Yes	No
Current_batch	The processing group for which batch needs to be run (Only one batch can run at a time for a processing group).	Yes	Yes
Source_batch	Future parameter. You can use the same value as the current batch for now.	Yes	No
Data_origin	Origin of data.	Yes	No
Execution_Mode	It executes the following modes that you want to perform the cleanup. Run: This execution mode displays the list of queries that will be executed under the specified Cleanup_Type. Preview: You can preview the list of queries that will be executed under the specified Cleanup_Type without executing them.	No	Yes
Current_runskey	This indicates the latest runskey on which particular job cleanup is to be performed. In case of resetting ER fully, this is the latest runskey in the FCC_BATCH_RUN run table and this table information is available in the studio schema.	No	Yes
Run_type	If Run_Type as RUN, the batch is triggered for the first time for the given FIC_MIS_DATE and Current_Batch. You can re-execute the failed job against the same FIC_MIS_DATE and Current_Batch using Run_Type as RERUN.	Yes	No
Cleanup_type	This indicates which specific ER job type the user wants to perform the cleanup operation. The cleanup types are: RESET-TO-DAY0: This mode type helps to perform full cleanup and reset the ER schema to DAY 0 execution CLEANUP-JOB1-INSTANCE: This mode type helps to perform cleanup when job1 is failed/ manually terminated CLEANUP-JOB2-INSTANCE: This mode type helps to perform cleanup when job2 is failed/ manually terminated CLEANUP-JOB3-INSTANCE: This mode type helps to perform cleanup when job3 is failed/ manually terminated CLEANUP-JOB4-INSTANCE: This mode type helps to perform cleanup when job4 is failed/ manually terminated	No	Yes