Incorrect Termination Date in the Job data component - HCM Peoplesoft

Termination date is auto-populated in the peoplesoft when an employee is terminated in the Job data component. Termination date is suppose to be the termination action EFFDT - 1.

Termination date is configured to be popluated as JOB.EFFDT - 1 in the Action table component.
Termination date will not populated correctly due to a delivered bug in HCM 9.0 as well as HCM 9.1.

When you insert new row in the job data component effective date is defaulted to current date or defaulted from the previous row if it is a future date. Select the action as Termination and look at the termination date it is populated correctly with JOB.EFFDT - 1. Now change the EFFDT field it will not refresh the effdt to JOB.EFFDT - 1 value. It lets you save the component with that information. Any logic based on the termination date will fail.

Delivered code fires on the field change of the Action field alone and not on the EFFDT field. This creates the problem of incorrect termination date.

screen shot from HCM 9.1 peopletools 8.50



  1. Anonymous said,

    Termination date functionality (effdt-1) works just fine. You have to save it to see the termination date. Once the job data component is saved, system updates termination date with correct date.

    on August 18, 2010 at 3:19 PM  

  2. Anonymous said,

    Interesting.. does Oracle Support have a patch for this?

    Also, since the JOB record is the most relevant employee information table, is it not appropriate to use the JOB.EFFDT to signify the termination date in the event of the employee being terminated?

    Is it appropriate to classify this feature as a bug?


    on November 13, 2010 at 8:06 AM  

  3. Anonymous said,

    Once you change the effdt you get a push button Calculate Status and dates which is visble in your screenshot as well.
    When you click on this push button your termination date gets corrected per the value of your changed effdt .

    on April 19, 2011 at 12:10 PM  

  4. sitapati said,

    This is now corrected in PPltools 8.52.11 and Application version 9.1.

    on July 18, 2013 at 5:37 AM