Last updated on JULY 13, 2016
Applies to:PeopleSoft Enterprise HRMS Time and Labor - Version 8 to 8.9 [Release 8 to 8.9]
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 713930
***Checked for relevance on 23-OCT-2009***
***Checked for relevance on 20-Apr-2011***
If Time Administration is run before an employee is inactivated in T&L, the customer cannot inactivate the employee because payable time already exists for exception reporters. If the employee goes on Leave during the period and payable time has already been created, customer wants to be able to inactivate employee on Time and Labor Time Reporter data page.
Once Payable Time has been created after TA has been run, employee cannot be inactivated in Maintain Time Reporter Data. Customer would like to be able to inactivate an employee with payable Time, with a warning appearing and then would like the Pay.
We run TA every 1-2 days, which creates payable time for the entire time period for exception reporters. When we receive the information that an employee is going on Leave or Disability in mid-period, it is too late to change his status to Inactive in Time & Labor as of the date of the Job Data change. We are not allowed to inactivate the employee because the payable time has been created for the entire period. We should be allowed to inactivate the employee as long as the payable time is still Estimated (ES) or Needs Approval (NA). When TA is re-run, there should then be no payable time created for the days when the employee is inactive.
I would prefer that the payable time (for the days including and after the date where the TL status is changed to Inactive) be automatically removed from the tables when the TA is run after the employee has been inactivated.
Perhaps a Warning message could be displayed on the Maintain Time Reporter Data page when trying to inactivate an employee that has payable time already created for the dates equal to or greater than the day of
inactivation. This would ensure that the employee is being correctly inactivated.
Because our Time & Labor activities will be eventually decentralized to our operations, it would be best to avoid manual interventions with the tables via SQL.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms