EPY: PSPPSHUP Load/Reset paysheets enhancement requests

(Doc ID 620508.1)

Last updated on DECEMBER 18, 2015

Applies to:

PeopleSoft Enterprise HRMS Payroll for North America - Version: 8 and later   [Release: 8 and later ]
Information in this document applies to any platform.

This document was previously published as Customer Connection Solution 200755786


Customers request the following functionality to be reviewed for inclusion to the PSPPSHUP process in a future release:

-   Request functionality to allow update and override of Hourly Rate when it is provided on the PSHUP_TXN table on either PAY_EARNINGS or PAY_OTH_EARNS.  Currently only the rate on Job is used.    

-  Request functionality to allow the override of  the deduction taken (benefit and General)and deduction subset fields when PU_SOURCE = 'OT'.  Current recommendation is to leave these fields Blank, except for Manual Checks.  

-  Would like process to issue an error or warning message if paysheet for Inactive Employee is created and there is a row in the PSHUP_TXN file for this employee because the data is not loaded to the paysheet .

-  Request functionality for shift overrides.  The basic need would be the addition of a SHIFT field to the PS_PSHUP_TXN table, and then an update of the PSPPSHUP COBOL process to use the new SHIFT field and update the PS_PAY_EARNINGS table.

-  Several clients feel that we should create paysheets and/or load transactions for inactive employees.   They understand that the process was not built to do this, but would like development to reconsider and add this functionality.   In the real world, this is a necessity for all PSHUP_TXN.PU_SOURCE activity (except WI).

-  Customers would like the ability to enter negative earnings into the AMT field.      Hours is a signed field, so amounts should be also.

-  Customer would like multiple earnings lines for a single employee to be inserted on the same addl number instead of a new addl number for each.

-   Allow users to update PSHUP_TXN table via online page, specifically delete and/or inactivate a record they do not want to attempt to Load via PSPPSHUP.  Right now the only way to manage this table is via SQL.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms