How does it work?

When the batch process is submitted to the queue from the application, it looks for the following three parameters:

1. CreationDateSearchInd
2. DateFrom
3. DateTo
4. ProcessingDate

Note that the parameters listed above are not mandatory. If the dates are not entered, they default to the system null date.

CreationDateSearchInd

CreationDateSearchInd indicates whether the extract is based on creation date or effective date. If CreationDateSearchInd was set to 'True' by the user, a creation date range search is performed, otherwise, an effective date range search is used.

When specifying the value for CreationDateRangeInd, it must be either 'True' or 'False'. It cannot be '1' or '0', or 'Yes' or 'No'. Validation is performed on the client to prevent entries of this type.

DateFrom / DateTo

As mentioned above, if the user does not specify DateFrom or DateTo when submitting the batch process, they default to the system null date.

The reason DateFrom/DateTo are not defaulted to the current date on submission to the queue, if the user does not specify them, is because the client current date may not be 'in sync' with the server current date. In general terms, this can potentially lead to problems when batch processes run.

Inside the batch process, the following date checks are performed:

• If DateFrom is found to be a null date, i.e., not specified by a user, an error is thrown and the batch process will not succeed.
• Similarly, if DateTo is found to be a null date, i.e., not specified by a user, an error is thrown and the batch process will not succeed.

ProcessingDate

This is the business date that should be used while executing the batch process. See Business Processing Date details above.