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

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

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
99 26-Nov-2021 10:22 12 KB jlawler to previous
98 26-Nov-2021 10:22 12 KB jlawler to previous | to last
97 26-Nov-2021 10:22 12 KB jlawler to previous | to last
96 26-Nov-2021 10:22 11 KB khiggs to previous | to last
95 26-Nov-2021 10:22 11 KB khiggs to previous | to last
94 26-Nov-2021 10:22 11 KB khiggs to previous | to last
93 26-Nov-2021 10:22 10 KB mhodgins to previous | to last
92 26-Nov-2021 10:22 10 KB mhodgins to previous | to last
91 26-Nov-2021 10:22 10 KB mhodgins to previous | to last
90 26-Nov-2021 10:22 10 KB mhodgins to previous | to last
89 26-Nov-2021 10:22 10 KB mhodgins to previous | to last
88 26-Nov-2021 10:22 12 KB mhodgins to previous | to last
87 26-Nov-2021 10:22 12 KB mhodgins to previous | to last
86 26-Nov-2021 10:22 12 KB mhodgins to previous | to last
85 26-Nov-2021 10:22 11 KB mhodgins to previous | to last
84 26-Nov-2021 10:22 11 KB mhodgins to previous | to last
83 26-Nov-2021 10:22 11 KB mhodgins to previous | to last
82 26-Nov-2021 10:22 11 KB mhodgins to previous | to last
81 26-Nov-2021 10:22 11 KB mhodgins to previous | to last

Page References

Incoming links Outgoing links
UBRETRO
UBRETRO

Version management

Difference between version and

At line 9 added 15 lines
!__UPRETRO/UBRETRO key processing differences__
[UPRETRO] and UBRETRO work differently with regards to pay header requirements.
In the case of [UPRETRO] the program will include all the old pays that are to have retro calculated. Prior to launching UPRETRO all the pay’s that will be processed will be displayed using the “List” button on [UPRETRO].
[UPRETRO] will create a new pay if there is no applicable pay header or will update an existing pay header if no applicable pay header can be found.
UBRETRO behaves differently in that it does not create a pay header. Instead prior to processing, UBRETRO requires the creation of a single "To Be Audited" pay for the specific pay period in which the retro amounts are to appear.
Therefore the “[Trigger BE Retro|TRIGGER_BE_RETRO]" toggle found on [IEAS] must be enabled on a EASD record that has effective and expiry dates that fall within the specified pay period start and end dates on the pay header selected.
If there are no "To Be Audited" pays that fall in period specified on the EASD records, than UBRETRO will not process.
At line 82 added 3 lines
*A report parameter __Post Negative Retro__ controls if negative amounts should be posted to IPPH. If set to __NO__ the negative amounts are not recorded; however, exception messages will still be logged.
*Reversals and pays that have been reversed are ignored
*Unit and Group information is obtained from the assignment, not the from the __old__ pay header being evaluated.
At line 68 removed 2 lines
When the UBRETRO process is run in 'Update' mode, a User Defined Field on the IPPH called 'Posted UBRETRO' is updated with a value of 'Y'.
At line 131 added one line
|Post Negative Retro| Optional, Toggle\\If 'Yes' then negative amounts will be posted on the pay header\\If 'No' the negative amounts will not be posted\\In both cases exception messages will appear on the report
At line 144 added 3 lines
----
![Notes|Edit:Internal.UBRETRO]
[{InsertPage page='Internal.UBRETRO' default='Click to create a new notes page'}]
At line 150 added 2 lines
This page (revision-99) was last changed on 26-Nov-2021 10:22 by jlawlerTop