The Automatic Updating Of The Audit Fields On The Record HRS_APP_RTE Is Not Working Properly
(Doc ID 2396522.1)
Last updated on AUGUST 20, 2018
Applies to:PeopleSoft Enterprise HCM Talent Acquisition Manager - Version 9.2 and later
Information in this document applies to any platform.
On : 9.2 version, Manage Applicant
The automatic updating of the HRS_APP_RTE table by PeopleSoft when Applicants and other Non Recruiters is not working properly.
When both an applicant accepts an offer or someone in HR completes the Manage Hire Process this triggers automatic updates based on Effects of Status changes entered in the Recruitment Status Areas.
The updates are causing both the HRS_ROW_ADD_xxx and HRS_ROW_UPD_xxx fields to be updated when a row of data already exists in the record.
Only the HRS_ROW_UPD_xxx fields should be updated.
Impact is that Internal Applicants are having emails sent to them about the routing status of other applicants because the system sees them as Recruiters.
That is when a hiring manager enters a route response on an applicant that is not the one that accepted the offer, the applicant that accepted the offer is viewed as the Recruiter and is populated in the Route template as the recruiter.
The real recruiter is still on the email because of secondary code that looks to see if the real recruiter was included or not.
There is no workaround for this issue if you want the Route Response emails sent out to Recruiters.
The issue can be reproduced with the following steps:
1. Internal applicants apply for a Job Opening
2. Recruiters Route the Internal Applicants to a Hiring Manager
a. Entries are written to the HRS_APP_RTE table
i. Add Date = 1/2/2018
ii. Add Operator ID = RECRUITER1
iii. Update Date1/2/2018
iv. Update Operator ID = RECRUITER1
3, Applicants remain in a Route status
4. An applicant is given an offer
5. An applicant accepts the offer
a. Status Area 'Effects of Status Change' causes applicants that are in a
Routed Status to be moved to 'Hold'
b. The HRS_APP_RTE table is updated based moving to Hold. (This is where the
Issue is, notice both the ADD and UPD are updated. It should only be the UPD
fields that are Updated.)
i. Add Date = 1/23/2018
ii. Add Operator ID = APPLICANT123
iii. Update Date1/23/2018
iv. Update Operator ID = APPLICANT123
The issue has the following business impact:
Due to this issue, the automatic updating of the HRS_APP_RTE table is not working properly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!