EntityDIScreening Batch Details

The EntityDIScreening batch runs the matching rules for entities and generates the events. This batch is run during Deployment Initation (DI), that is, Day 0 or Initial screening.

The following table provides the list of tasks in the EntityDIScreeningbatch. These tasks must be executed in the following order:

Note:

ATTENTION: You can slice the customer data and execute the slices instead of executing extensive data. The Data Slicing functionality empowers you to partition the data on the Day 0/Initial screening, facilitating the screening of smaller, more manageable chunks or slices of customer data. Consequently, this reduces resource requirements and the time needed for the screening process. For more information on Slicing Customer data, see the FCCM Cloud Master Data Guide.

Table 19-48 EntityDIScreeningBatch Details

Sequence	Tasks for EntityDIScreeningBatch	Jobs for EntityDIScreeningBatch	Pipelines for EntityDIScreeningBatch	Comment
1	StartBatchEntityDIScreening	Not Applicable	Not Applicable
2	EntityBatchDIScreeningTask	EntityScreeningJob	EntityScreeningJob	Data Origin ($DATAORIGIN$) and Slice Name ($SLICENAME$) are mandatory parameters.
3	ValidateEntityDIBatch	Not Applicable	Not Applicable	Slice Name ($SLICENAME$) is a mandatory parameter. You cannot repeat the slice name if a batch is ongoing with the same slice name. The ValidateEntityDIBatch task will show an error message if you repeat the slice name in a progressing batch. After the successful execution of the batch, you can use the slice name again.
4	EndBatchEntityDIScreening	Not Applicable	Not Applicable