This page (revision-9) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

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
9 26-Nov-2021 10:22 5 KB Kevin Higgs to previous
8 26-Nov-2021 10:22 5 KB lurtan to previous | to last
7 26-Nov-2021 10:22 5 KB lurtan to previous | to last
6 26-Nov-2021 10:22 4 KB tchau to previous | to last
5 26-Nov-2021 10:22 4 KB jmyers to previous | to last
4 26-Nov-2021 10:22 4 KB jmyers to previous | to last
3 26-Nov-2021 10:22 4 KB jmyers to previous | to last
2 26-Nov-2021 10:22 4 KB jmyers to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
UPCTS
UPCTS

Version management

Difference between version and

At line 5 removed 2 lines
The Load Time Sheets to Payroll (UPCTS) will load the timesheets to Maintain Pay Transactions (IPTR) screen.
At line 38 removed 2 lines
\\ \\
A new ‘PR in Process’ time sheet status [X_TIME_SHEET_STATUS] has been implemented to enforce NO insert/update/delete rules on time sheet/time sheet details, leave lines and time exceptions and NO Approval on time sheet and leave line. This feature has been implemented only for UPCTS, so once the process is started, the information on the time sheet cannot be modified (a message will pop up) and time sheet status will become ‘PR in Process’. If system refresh is fast enough the time sheet will disappear from the list on [IPTS] and details will be frozen. In case of UPCTS failure, the time sheet status will be restored.
At line 41 removed one line
At line 52 changed 6 lines
|Batch By|Mandatory, [Batch by|X_UPCTS_BATCH_BY] lexicon available\\This will determine how the batches are set, by department, etc.
|Batch For Each PP|Optional, [Yes or No|X_YES_NO] lexicon available\\If <<YES>>, there will be a batch for each pay period.
|Ready for PR Only|Optional, [Yes or No|X_YES_NO] lexicon available\\See note above on how to set YES / NO toggles.
|Add Open Time Sheets|Optional, [Yes or No|X_YES_NO] lexicon available\\See note above on how to set YES / NO toggles.
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.
|Trial|Optional, [Yes or No|X_YES_NO] lexicon available\\You may choose to run the report in a trial mode or in update mode. If <<No>> then the update is committed. If <<Yes>> then the update is not committed and the process may be run again. This field allows you to see the results without committing them.
|Batch By| Mandatory, LOV Available, <Department>\\Users may batch by authorization area, department, department batch code, location, or payroll.
|Ready for PR Only| Optional, LOV Available. See note above on how to set YES / NO toggles.
|Add Open Time Sheets| Optional, LOV Available. See note above on how to set YES / NO toggles.
|Mark Batch as Eligible| Mandatory, LOV Available, <YES>. Should the transaction batch be created as eligible (ready)? The eligible flag is often used to communicate between payroll clerical staff entering time, and the payroll master.
|Exception Level| Mandatory, LOV available, <Exception Only>. This field indicates the exception level (report messages) required.
|Trial| Mandatory, LOV Available, <YES>. If `No' then the update is committed. If `Yes' then the update is not committed and the process may be run again. This field allows users to see the results without committing them.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop