Human Resources
Release Notes 3.3.6 / 3.3.7
Pay Period 26
December 21, 2007
The following items have been moved (migrated) to Production for use by Agencies beginning on December 21, 2007.
-
IM127690 – Users are unable to enter a concurrent job for an employee in which they do not have row level security access. They were able to do this in 8.0
ISSUE: Users need to be able to add a concurrent job for an employee who is outside of their row level security to give them a job within their agency.
RESOLUTION: Changed the search record to allow users to enter concurrent jobs for any employee, regardless of row level security
USER IMPACT: Users will be able to initiate a concurrent hire on any employee
regardless of row level access.
-
IM123517 – Users encountering issues with reinstating TSP and Health Benefits for termed employees.
ISSUE: Users encountering issues with reinstating TSP and Health Benefits after an automatic termination is cancelled via the PAR Pages.
RESOLUTION: research determined that the issue related to the employee being terminated through the automatic NTE Termination mass mask. Made multiple changes to the program to resolve the issue.
USER IMPACT: The Auto NTE Term process is working more effectively. If an auto termination is cancelled via the PAR Pages, the user can successfully reinstate benefits and/or TSP.
-
IM129964 – Changes to the CFC Stop program.
ISSUE: Prepare this program for running at year end.
RESOLUTION:
(1) These CFC Stop records will not be sent to DFAS on the Non-SF50 interface (i.e. do not populate the “Action Stage” table);
(2) We will populate the General Deduction Tracking link for each CFC Stop record created.
(3) Deduction Stop Reason will be set to “Yes”, so most fields on the page will be grayed out.
(4) In previous years, this program ran for all active employees who had an active CFC deduction. Now, we will end all active CFC deductions, even of the employee is not active. (If the employee is termed / retired, he should not have an active CFC deduction, but this might have been missed).
USER IMPACT: All employees will receive an annual CFC Stop as expected.
-
IM128870 – NTE process not inserting into tracking data on the benefits side.
ISSUE: NTE process not inserting into tracking data on the benefits side
RESOLUTION: Changed program to insert tracking data for Health Benefits, Savings, Direct Deposit and TSP.
USER IMPACT: Benefit changes resulting from a termination inserted by the NTE Term
process will have tracking information. This will assist users in determining how the
changes were inserted into the employee’s benefits records.
-
IM129583 - Error received when saving PAR Action
ISSUE: Error message received when processing a PAR action for an employee with Job Earnings Distribution set to HOURS, in troubleshooting we determined that delivered code for distribution equal to HOURS was incorrect.
RESOLUTION: Resolved error message by correcting logic. In addition, we corrected all employee data with a value not equal to NONE, as this is the only correct value for HHS employees. Because we only had two employees set to a different value, we had never experienced the error in the past.
USER IMPACT: These employees now have correct data and PAR actions can be processed successfully. In addition if we ever start using Job Earnings Distribution, we will also be able to process PAR actions successfully if the value is ever equal to HOURS.
-
IM130293 – EHRI Edits, online enforcement + reporting
ISSUE: (1) there were some cases where the edits were firing on a cancelled PAR action. (2) There are a few edits which users have no way of correcting, but we still show these errors on the EHRI Edits report.
RESOLUTION: (1) programming has been corrected. (2) We will prevent these errors from coming out on the report until such time as we give the users a way to correct the error condition.
USER IMPACT: Online processing of EHRI edits is working more effectively and efficiently.
-
IM131069 - Error received when terminating TSP for an employee without TSP Catch-up.
ISSUE: Users trying to terminate TSP for an employee who did not have TSP Catch-Up were receiving an error about invalid row number. In addition- when testing we found a scenario that allowed users to terminate TSP even though TSP Catch Up was still active (but did have a termination date in the future).
RESOLUTION: Code modification was implemented to allow users without TSP Catch Up to terminate TSP. Modifications ensured that logic checking for TSP Catch Up term only fired when TSP Catch Up existed. In addition modified existing code that looked for TSP Catch Up Term to ensure that the term date was <= the TSP term date.
USER IMPACT: Users can successfully process TSP and TSP Catch Up online.
EHRP Public Queries
Name |
Purpose |
Parameters |
Data Provided |
N/A |
|
|
|
|
Last
revised:
March 13, 2008
|
|
|
|
