Batch Processing and Positive Input

This topic describes how batch processing works with positive input.

Unprocessed Positive Input

You can finalize a calendar run without processing all positive input. For example, if a payee has 10 units of positive input, and you change the units to 12 after running the Calculate phase, the system generates an iterative trigger (assuming that the units field is set up to generate iterative triggers). If you don't rerun the Calculate phase, only 10 units are processed. If you run a retroactive process, all 12 units are processed (assuming that the units field is also set up to generate a retroactive trigger).

Arrears - Payback

If positive input instances with the action type of Override exist, the system determines any arrears payback amount and adds it to the first positive input instance. If the element resolves multiple times per segment in the current period, the following hierarchy is observed when applying the Arrears - Payback amount:

  1. Normal resolution of the element.

  2. Override occurrence.

  3. Additional occurrence.

When there are only Add type instances of positive input (and no other action types such as Override), the system applies the arrears payback to the initial calculation based on the normal resolution of the element and not to the subsequent additional resolutions of the element. If there is a mix of Override and Add action types, the system applies the arrears - payback amount to the override resolution of the element. Lastly, if a normal resolution of the element does not exist, and an override resolution of the element does not exist, then the system applies the arrears - payback to the additional resolution of the element. It is important to ensure that the system applies the arrears payback amount only once.

Frequency Conversion, Rounding, and Proration

The system does not apply frequency conversion, rounding, or proration to any numeric component or amount entered in positive input. For components not entered through positive input, normal rule processing occurs based on the element definition.

How the Batch Process Stores Positive Input

Manually entered positive input is maintained in a separate record from positive input that's automatically generated. However, all positive input considered during processing is stored in the same output record (GP_RSLT_PI_DATA), regardless of source. A second record (GP_RSLT_PI_SOVR) stores data for supporting elements, such as department or job codes that you entered manually or received from Time and Labor.

One row of data is written to the output table for each instance. Therefore, if entries are bundled, one row of data is written to the output table for the entire bundle. When a separate instance number is assigned to each entry, a row of data is written to the output table for each entry.

The instance numbers stored in the output table enable you to link each entry to the processing results. An automatically generated source code (PI_Source) identifies the origin of the entry: Absence, Generated PI, Manual, or Time & Labor.