Last updated on MARCH 20, 2017
Applies to:PeopleSoft Enterprise HCM Talent Acquisition Manager - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
HRS_APP_PROFILE is out of sync with HRS_RCMNT on Job Applications after merging an applicant who has applied with no Job Opening selected.
Steps to Replicate:
1. Merge a duplicate applicant who has applied with no Job Opening selected.
2. Apply to a new Job Opening using the Target applicant.
3. Query HRS_APP_PROFILE and HRS_RCMNT.
4. Note that the HRS_PROFILE_SEQ matched with the new Job Application in HRS_RCMNT corresponds to the HRS_APP_PROFILE data that was merged rather than new/current data.
In HRMS 9.1 or HCM 9.2, for some applicants HRS_APP_PROFILE.HRS_PROFILE_SEQ = 0 and there is no corresponding row in HRS_RCMNT with the same HRS_PROFILE_SEQ. As a result of this, the Search Applicant process will not return any results for that application. This has been noticed especially when applicant applies for multiple jobs. HRS_RCMNT will have a record for each job applied for, but the HRS_PROFILE_SEQ will have a value of 1 rather than the 0 that is in the HRS_APP_PROFILE record. A similar mismatch may occur when the value of HRS_APP_PROFILE.HRS_PROFILE_SEQ is other than 0.
When an applicant applies for more than one job opening at the same time, there should be one row in HRS_APP_PROFILE with HRS_PROFILE_SEQ = 1, and multiple rows in HRS_RCMNT with the same Applicant ID and Profile Sequence, but different Job Opening IDs and Recruitment IDs. If the applicant logs out, and then comes back and again applies for one or more jobs, another row should be created in HRS_APP_PROFILE with HRS_PROFILE_SEQ = 2, and corresponding rows in HRS_RCMNT will also have HRS_PROFILE_SEQ = 2 and varying Job Opening IDs and Recruitment IDs.
Instead, for some applicants, HRS_APP_PROFILE.HRS_PROFILE_SEQ = 0, and there are no rows in HRS_RCMNT with HRS_PROFILE_SEQ = 0. There may be circumstances where the value of HRS_APP_PROFILE.HRS_PROFILE_SEQ will be some other number as well, and there will be no corresponding value in the same field in HRS_RCMNT.
Similar scenarios were fixed in HRMS 9.1 bundles 13 and 15. In testing in Oracle Global Customer Support, it has been discovered that similar mismatch can occur after merging and linking to a new Job and also when an applicant is scheduled for an interview with no job opening associated, and then is linked to a job opening.
Due to this issue, users may not be able to find the applicant in Find Applicants component, in all circumstances.
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