ETL92: Invalid Error on Comp Time Where Balance is Available
(Doc ID 2255785.1)
Last updated on AUGUST 01, 2024
Applies to:
PeopleSoft Enterprise HCM Time and Labor - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
It appears the below error is triggered after user has comp time entered and time admin run, but when user goes back to correct the previously entered comp time an error is triggered:
Error:
Comp Plan COMPTIME will reach a balance of -4.63 on 2017-02-21. The minimum allowed is 0. (13504,110)
Minimum balance allowed is exceeded for the Compensation Plan. The quantity reported as Compensation Time Taken must be reduced.
The error being triggered is correct, however the balance shown (-4.63) in the message is incorrect.
Step to Recreate:
1. Add Template Built Rule that multiplies Comp time by 1.5 using Template 560.
2. Comp Time Plan KUCTOP1 is set to Limit Positive Balance. Max Positive Allowed = 240
3. Enroll EE in comptime Plan KUCTOP1.
4. In timesheet Report 11.50 hours Comp Time Earned along with 40 REG.
5. Run Time Admin for the weekly period.
6. Verify tl_comleav_tbl and timesheet Leave/Compensatory time shows correct balance.
7. For the next week Report 40 hours REG.
8. Run Time Admin for the weekly period.
9. For the next week Report 40 hours REG.
10. Run Time Admin for the weekly period.
11. For the next week Report 10 hours Comp Time Taken plus 40 hours REG.
12. Run Time Admin for the weekly period.
13. Verify tl_comleav_tbl and timesheet Leave/Compensatory time shows correct balance.
14. For the next week Report 13 hours Comp Time Earned plus 40 hours REG.
15. Run Time Admin for the weekly period.
16. Verify tl_comleav_tbl and timesheet Leave/Compensatory time shows correct balance.
17. Now go back to Week 2 and make the following corrections on Tuesday. Add 7.25 hours Comp Time Taken and change the original 10 REG hours reported on this day to 2.25 Hours REG.
18. Submit the changes. Note: The error being triggered is correct, however the balance shown (-4.63) in the message is incorrect.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |