Thresholds

Thresholds are used during batch (ICL) aggregation, as a guide for calculating which batches (ICLs) are to be grouped together for extraction. As the Transaction Server extraction process identifies a batch (ICL), it compares the batch (ICL) data to the defined thresholds for the current rule element. If the defined thresholds are not exceeded, the extraction process continues with the next batch (ICL) and repeats the process. Each batch (ICL) is aggregated with the previous one and compared again to its thresholds. Once a threshold is exceeded, the batches (ICLs) that were aggregated are to be extracted. If no more batches (ICLs) are found, any batches (ICLs) that have been aggregated are checked to see if they are within the threshold limit. If they are, they will be extracted. If they do not meet the minimum thresholds, they will not be extracted.

The Transaction Server supports the following thresholds:
debitAmount
Total debit amount for the batches (ICLs), in pennies
creditAmount
Total credit amount for the batches (ICLs), in pennies
totalItems
Total transactions (both credit and debit) for the batches (ICLs)
Table 1. Thresholds
Attribute Required Values/Example Default Description
min No min="5000" 0 Identifies the minimum threshold required for batches (ICLs) to be aggregated.
Note: Minimum thresholds are in effect during events that are triggered in the Transaction Server. During scheduled tasks, the minimum thresholds are ignored to ensure that batches (ICLs) are extracted in a timely manner.
max No max="5000" 0 Identifies the maximum threshold to use during aggregation. The maximum threshold is used as a guide for aggregation calculation of batches (ICLs).
Sample threshold element definitions:
<debitAmount   min="5000" max="5000"    />
<creditAmount  min="0"    max="250000"  />
<totalItems    min="5000" max="25000"   />