Duplicate HRS_PERSON_IDs Being Created During SendCandidate.xml (Doc ID 1068009.1)

Last updated on NOVEMBER 23, 2015

Applies to:

PeopleSoft Enterprise HRMS Talent Acquisition Manager - Version 8.9 to 9.1 [Release 8.9 to 9]
Information in this document applies to any platform.
***Checked for Currency 15-Aug-2011***


During Job Board Integation & Resume Processing Integation duplicate HRS_PERSON_IDs being created. SendCandidate.xml using the HR-XML structure when try to submit a second application for the same applicant id. Check HRS_HROI_HRXML.Data.Candidate.CandidateData - method Parse
you'll see where <CandidateRecordInfo> is parse but when the HRS_SYNC message is sent and SendCandidate runs, it creates a new applicant id, despite the entry in the incoming XML

<IdValue name="ApplId">1234</IdValue>

In package HRS_HROI_HRXML.Mapping.Incoming.CandidateMap is where code (&cand.HRS_PERSON_ID ) need to be added:

method MapToPS
/+ &candxml as HRS_HROI_HRXML:Data:Candidate:CandidateData +/
Local string &templang;
&rdata = &candxml.Resume;
&cresume.HRS_RESUME_ID = &ResumeId;
&cresume.RESUME_TEXT = &rdata.TextResume;
&cprof = create HRS_CANDIDATE_MANAGER:OBJ_CANDIDATE:DATA:CandidateProfile();
&cand.HRS_PERSON_ID = Value(&candxml.CandidateRecordInfo.Id);

This will assign the value to the &cand object so that HRS_PERSON_ID can be used further along when it starts putting the data into the tables. Without this code it is just parsing the value but doing nothing with it and will therefore always create a new HRS_PERSON_ID with every SendCandidate application. 


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms