PeopleSoft: Adding Candidates to PeopleSoft (Add-ins, Workflow, Desktop Tools, Push to ATS)

Applies To:
PeopleSoft
Talemetry
Integrator
(And any of Add-ins, Workflow, Desktop Tools, Push to ATS)

Symptoms:
  • Candidate cannot be found in TAM
  • Candidate is erroring from PSFT and stuck in the Talemetry Integrator (windows)
  • Duplicate Merge was done incorrectly
  • Internals are bouncing or cannot be found in TAM
Usual Causes/Resolutions:
  • This is almost always data related.  The candidate trail will need to be followed from

1.       Talemetry Integrator – make sure this has been running and the service is up

2.       Integration Log

3.       Talemetry Exceptions

  • Please run the SQL in the following section to try to find the candidate submission and determine what happened.  The Talemetry Exceptions table/page logs what dup/merge decisions were made and what record it merged with.  The data with the target and the source need to be compared. 
  • *** External Dup Merge is looking at Last Name + Email address
  • *** Internal Dup Merge is looking at Employee ID and Last Name
All of these steps need to be investigated to determine what decision points were made.

Support Case Requirements  -- Error at Integrator (Windows):
If the candidate error’d at the Integrator there will be no PeopleSoft logs to retrieve as the candidate submission went no further:
  • Start at the Integrator search the logs for that name and find the datetimestamp , error and/or transaction id .  Please validate if there was an error at the Integrator
  • Check the error folder for the rejected transactions.  The filename containing the error’d xml follows the format transaction#.xml (1235456788.xml).
  • Try to resubmit/re-process that xml
  • If the submission STOPS at Integrator, please review the message “why”.  Sometimes it is very obvious i.e. “missing required first name and last name”.  Correct the source xml and resubmit.
  • If resubmission and/or data correct still fails please submit the following to Talemetry Support
  • Candidate Talemetry Integration xml message (resubmitted/re-processed xml)
  • Provide the errorlog Integrator text
  • Provide the symptoms and expected behaviour
Support Case Requirements -- PostCandidate (Submission to PS):

  • If the candidate shows success at the Integrator there will be PSFT integration logs. 
  • Start at the Integrator search the logs for that name and find the datetimestamp , error and/or transaction id .  Please validate if there was an error at the Integrator. 
  • If no error, then use the datetimestamp to find the transaction in the PeopleSoft Integration Logs OR Query that name on the Talemetry Exceptions page.
  • Please run the below SQL to try to find the candidate submission
  • Please submit the following to Talemetry Support:
  • Candidate Talemetry Integration xml message
  • PeopleSoft Integration Log  for PostCandidate XML – 2, 4, 5 boxes of text (can link from Talemetry Exceptions page most of the time)
  • Symptoms and expected behaviour
  • Text from the Talemetry Exceptions page or (PS_TT_EXCEPTIONS)
  • Supporting SQL .Get the SQL below: 
Internal Applicant
SELECT * FROM PS_NAMES_VW WHERE lower(LAST_NAME) = 'lowercase_lastname';
SELECT * FROM PS_HRS_APPLICANT WHERE EMPLID IN (SELECT EMPLID FROM PS_NAMES_VW WHERE lower(LAST_NAME) = 'lowercase_lastname');
SELECT * FROM PS_EMAIL_ADDRESSES WHERE EMPLID IN (SELECT EMPLID FROM PS_NAMES_VW WHERE lower(LAST_NAME) = 'lowercase_lastname');
SELECT * FROM PS_HRS_APP_PROFILE WHERE HRS_PERSON_ID IN (SELECT HRS_PERSON_ID FROM PS_HRS_APPLICANT WHERE EMPLID IN (SELECT EMPLID FROM PS_NAMES_VW WHERE lower(LAST_NAME) = 'lowercase_lastname'));
SELECT * FROM PS_TT_EXCEPTION WHERE DATETIME_STAMP >  'YYYY-DD-MM'; (please modify for your DB platform date format)
select * from PS_HRS_APP_RES where ATTACHUSERFILE like '%111111111111%'; ** where the %111111111111% is from the Talemetry Integrator transaction id i.e. 12323534647.xml, you would look for %12323534647%
External Applicant
SELECT * FROM PS_HRS_APP_NAMES WHERE lower(LAST_NAME) = 'lowercase_lastname';
SELECT * FROM PS_HRS_APPLICANT WHERE HRS_PERSON_ID IN (SELECT HRS_PERSON_ID FROM PS_HRS_APP_NAMES WHERE lower(LAST_NAME) = 'lowercase_lastname');
SELECT * FROM PS_HRS_APP_EMAIL WHERE HRS_PERSON_ID IN (SELECT HRS_PERSON_ID FROM PS_HRS_APP_NAMES WHERE lower(LAST_NAME) = 'lowercase_lastname');
SELECT * FROM PS_HRS_APP_PROFILE WHERE HRS_PERSON_ID IN (SELECT HRS_PERSON_ID FROM PS_HRS_APP_NAMES WHERE lower(LAST_NAME) = 'lowercase_lastname');
SELECT * FROM PS_TT_EXCEPTION WHERE DATETIME_STAMP >  'YYYY-DD-MM'; (please  modify for your DB platform date format)
select * from PS_HRS_APP_RES where ATTACHUSERFILE like '%111111111111%'; ** where the %111111111111% is from the Talemetry Integrator transaction id i.e. 12323534647.xml, you would look for %12323534647%

Feedback and Knowledge Base