This page (revision-26) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
26 26-Nov-2021 10:22 5 KB Karen Parrott to previous
25 26-Nov-2021 10:22 5 KB mmcfarland to previous | to last
24 26-Nov-2021 10:22 5 KB mmcfarland to previous | to last
23 26-Nov-2021 10:22 5 KB khiggs to previous | to last
22 26-Nov-2021 10:22 5 KB khiggs to previous | to last
21 26-Nov-2021 10:22 5 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
UPTR
UPTR

Version management

Difference between version and

At line 13 added 7 lines
The UPTR processes one batch of pay transactions at a time and conditionally updates the Batch Status to 'Processed by UPTR' at the end of the batch.
* Transactions within a batch will be bypassed if the Time Code does not have an associated Pay Component in [IDTC] and also when the Associated Pay Component is not valid (Based on PCRULES) for the Employee Entity, Unit and Group.
* With the introduction of this Preference [UPTR_CLEANUP], the User can force UPTR to mark the Batch as ‘Processed by UPTR’.
* If UPTR locates this Preference with a value of ‘Y’, then it will mark the Batch as Processed regardless of any errors located on Transactions in the Batch.
* In addition, ANY Time codes that do NOT have an associated PC need to have the 'Bypass UPTR' toggle turned on (in [IDTC]) to allow the preference to work properly.
At line 37 removed one line
This page (revision-26) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop