My Oracle Support Banner

Primary Solution on Effective Dates in Job Data. (Doc ID 839078.1)

Last updated on JUNE 22, 2022

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
This knowledge document is a replacement for 661950.1 which has been deleted.

Purpose

This document contains the following information:

  • Effective dates in Job Data
  • Handling Multiple Actions with the Same Effective Date
  • Understanding different Dates in Job Data page
  • Different issues around the effective dates in Job Data

Questions and Answers

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
Purpose
Questions and Answers
 <Internal_Only>The following Anchor is used in an Internal Flow.  Do not edit or remove.</Internal_Only>
 What are Effective Dates?
 Effective Dates in Job Data Work Location Page (Workforce Administration, Job Information, Job Data)
 Calculate Status and Dates Button
 Handling Multiple Actions with the Same Effective Date
 Mass Employee Transfers
 Definition of dates associated with Organizational Instance Organizational Assignment
 Difference between Instance Date and Assignment Date
 <Internal_Only>The following Anchor is used in an Internal Flow.  Do not edit or remove.</Internal_Only>
 Difference between 'Company Seniority Date','Hire Date','Rehire Date' and 'Original Hire Date'
 For a new assignment the hire date, last hire date and termination date are not populated in Job.  Is this the way PeopleSoft is designed or is there a bug?
 When hiring a new employee, a Hire Row is created.  Click the Next Contract Number field on the Job Information Page in Job Data.  If user subsequently changes Hire Date prior to saving the Record, when they click the Save button the system issues the error "Data being added conflicts with existing data".
 An employee's Benefits Service Date and Company Seniority Date were originally set at 11/6/1968. The employee had a PAY/GA row inserted into JOB which is a general pay increase. When the increase row was inserted, the application re-sets the Company Seniority Date and Benefits Service Date to the Original Hire Date on the Job row which is 8/16/1975 based on the overrides that are set. 
 If an employee with an Additional Assignment Record has an Effective Date which is greater than the Termination date of the Controlling Record,  the system issues the Error "Error while updating an Employee's Additional Assignment with Employee Record # (1000,1343)." 
 Currently in HRMS 9.0 the action\action reason REH is not updating the company seniority date correctly. Is this the right behavior?
 What is the recommended method to correct the hire date for an employee who actually started working for the company on a date other than the date entered as the hire date?
 
 Why does the system not allow the Last Day Worked date to be the same as effective date of the row when the Person's Leave of Absence (LOA) action is entered?
 Historical dates are cleared when hiring a former Contingent Worker.
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.