1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

ORA-20001: This person either does not exist at all or does not exist as of the

Discussion in 'Oracle HRMS & Payroll' started by neelambhumij, Aug 13, 2014.

  1. neelambhumij

    neelambhumij Active Member

    Messages:
    51
    Likes Received:
    2
    Trophy Points:
    160
    Location:
    JOHANNESBURG
    Hi All

    I have issues with two cases---
    1> I trying to update attributeN in per_all_people_f.
    Using the api hr_person_api.update_person --- its an "update" for the employees that are active as of sysdate, p_effective_date is sysdate.
    But am facing error for some records..ORA-20001: This person either does not exist at all or does not exist as of the effective date.

    2>
    i using the same api for ex- employees(as of sysdate).
    here doing 'correction' effective_date= papf.effective_start_date when the employee was an active employee.
    here also facing the same error.

    any suggestions plz....:confused:

    Thanks
    Kind Regards
     
  2. DTSIGuy

    DTSIGuy Forum Advisor

    Messages:
    402
    Likes Received:
    58
    Trophy Points:
    410
    Location:
    Texas
  3. neelambhumij

    neelambhumij Active Member

    Messages:
    51
    Likes Received:
    2
    Trophy Points:
    160
    Location:
    JOHANNESBURG
    Hi CJ

    I Want to confirm something with you..
    Ideally we are not suppose to execute any dml statements on oracle base table.
    But i guess its fine for dff fields...

    I would like to know ur suggestions on this.. as there are like 1000 rcords giving me the same error as stated above...

    Thanks..
     
  4. DTSIGuy

    DTSIGuy Forum Advisor

    Messages:
    402
    Likes Received:
    58
    Trophy Points:
    410
    Location:
    Texas
    True...you are not to directly alter the contents of the tables via SQL...EVER. And no, it is not fine to do that for the DFFs.

    However, you should be able to create a process to find those erroneous records and call the appropriate API to fix them.

    CJ
     
    neelambhumij likes this.