Individual314aDIScreening Batch Details

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

To configure the time frame considered by this batch, use the FROM_DATE and TO_DATE parameter calendars in the Individual314aDIScreening batch.

The following table provides the list of tasks in the IndividuDIal314aDIScreeningbatch. 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-56 Individual314aDIScreening Batch Details

Sequence	Tasks for Individual314aDIScreening Batch	Jobs for Individual314aDIScreening Batch	Pipelines for Individual314aDIScreening Batch	Comment
1	StartBatchInd314aDIScreening	Not Applicable	Not Applicable
2	Ind314aDIBatchScreeningTask	Ind314aBatchScreeningJob	Individual 314 A Batch Screening	Data Origin ($DATAORIGIN$) and Slice Name ($SLICENAME$) are mandatory parameters.
3	ValidateInd314aDIBatch	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 ValidateInd314aDIBatch 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	EndBatchInd314aDIScreening	Not Applicable	Not Applicable