2525275 - Forwarded and Referred Candidates Not Showing up in Reports (Recruiting V2 and Recruiting V2 Secured)

SAP Knowledge Base Article - Public

2525275 - Forwarded and Referred Candidates Not Showing up in Reports (Recruiting V2 and Recruiting V2 Secured)

Symptom

Recruiting V2 Adhoc Report
If the Referral Table is used to show "Forwarded" or “Invited to apply” referral records for candidates who have not yet applied to a requisition, the respective records will not show up in the report IF corresponding fields from Candidate or Job Requisition Table are also included in the report.
 
Referral fields selected
KBA1.png

Candidate and/or Job Req fields are also selected. The “Forwarded” and “Invited to Apply” records are lost.
KBA2.png

 

However, the candidates will show up if Candidate and Job Req fields are NOT included.

No Candidate or Job Req fields are selected. All records show up correctly.
KBA3.png

 

The same occurs for candidates who have been forwarded or added by agencies and not yet applied, they do not show up in Adhoc report if fields from Agency and Agency Recruiter Table are included along with the associated fields from the Candidate or Job Requisition Tables.

KBA4.png

Recruiting V2 Secured Adhoc Report
For Referral fields, the “Forwarded” and “Invited to Apply” records NEVER show up if the candidate has not applied yet. Same with Agency and Agency Recruiter fields.

Environment

  • SAP SuccessFactors Recruiting Management
  • Adhoc Recruiting V2 and Recruiting V2 Secured reports

Reproducing the Issue

Following these steps to reproduce error message:

Recruiting V2

  • Navigate to Analytics / Reports from top menu.
  • Navigate to Adhoc reports tab.
  • Create a Recruiting V2 report and select report columns.
  • Select Referral table and select all fields. Also select fields from Agency and Agency Recruiter tables.

KBA7.png

  • Execute the report
  • Select all fields from Candidate table
  • Execute the report and observe that records are missing.
  • Select fields from Job Req table and remove Candidate fields.
  • Execute the report and observe that records are missing.

 

Recruiting V2 Secured

  • Navigate to Analytics / Reports from top menu.
  • Navigate to Adhoc reports tab.
  • Create a Recruiting V2 secured report and select report columns.
  • Select Referral table and select all fields. Also select fields from Agency and Agency Recruiter tables.

KBA9.png

  • Execute the report
  • Execute the report and observe that records are missing.

 

Cause

Recruiting V2

The design of the reporting domain necessitates that every table included in a report has a relationship to another table.

 

The result of this is that if you include the Referral table, it needs to have a relation to the other tables within the report. The relationship for this was defined as a link through Job Requisition to Application to Referral. This means that any report that involves the Referral table requires there to be an existing Application record, which removes any candidates who have not applied for a Job Requisition.

 

The unintended side effect of this is – all Referrals records without a corresponding Application get filtered out from the Adhoc report. This explains all of the observed problems.

By extension, Agency and Agency Recruiter tables joined to the rest of the RCM entities through the Referral table – so the same behavior was observed there.

 

Recruiting V2 Secured

The problem is compounded in Recruiting V2 secured domain as it includes an implicit filter on Job Requisition due to the Requisition Pill security selection (e.g. choosing the security operator such as “Hiring Manager”) . So even if only Referral is included in the report, the join path of Job Requisition to Application, and Application to Referral is implicitly present in the report query.

Resolution

Recruiting V2

To work around this problem so correct data would be displayed while maintaining backward compatibility for existing reports, it was decided to split up the current Referral table into 3 – one linked directly to Job Requisition, one to Candidate, and (the original) Referral table linked to Application. The same was done for Agency and Agency Recruiter tables. This approach makes the join relationship between the entities explicit.

 

There are now 6 new tables and 9 overall for referral and agency data.

  • Referral Agency linked on Application
  • Referral Agency linked on Candidate
  • Referral Agency linked on Job Requisition 
  • Referral Agency Recruiter linked on Application
  • Referral Agency Recruiter linked on Candidate
  • Referral Agency Recruiter linked on Job Requisition 
  • Referrals linked on Application
  • Referrals linked on Candidate
  • Referrals linked on Job Requisition

 

With this solution if a customer wants to join Referral with the other 3 entities they have to select the corresponding Referral tables.

  • Only Referrals – Use any of the 3 tables
  • Referral + Job Req – Use Referrals linked on Job Requisition (will include Forwarded and Invited to Apply records)
  • Referral + Application – Use the original Referrals linked on Application (filters out referrals without applications i.e. Forwarded and Invited to Apply records; should fetch 1 record for each Job Req a Candidate has been referred and applied to)
  • Referral + Candidate – Use Referrals linked on Candidate (apart from Forwarded and Invited to Apply records this should include even agency referrals by duration i.e. without associated job reqs)

 

Recruiting V2 Secured

The Recruiting V2 Secured schema has 1 limitation – because of the implicit join on Job Requisition the Referrals linked on Candidate would make no sense. It would still always go through the join path of Job Req to Application, Application to Candidate, and Candidate to Referral i.e. it would end up with the same dataset as the original Referrals linked on Application i.e. Forwarded and Invited to Apply records would still get filtered out.

Therefore, the secured schema only has 6 tables

  • Referral Agency linked on Application
  • Referral Agency linked on Job Requisition 
  • Referral Agency Recruiter linked on Application
  • Referral Agency Recruiter linked on Job Requisition 
  • Referrals linked on Application
  • Referrals linked on Job Requisition

See Also

Quick Facts and Known Limitations:

  • At one time, only Referrals linked on 1 out of Application, Candidate, and Job Req can be selected for a report. If Referrals linked on Job Requisition table is selected the alternate tables linked on Application and Candidate are greyed out and cannot be selected and vice versa. This extends to Referral Agency and Referral Agency Recruiter tables as well.
  • As a result, there is still no way to join together all the entities in the report – Job Req, Application, Candidate and Referral and get ALL correct matching results in each row.
  • In the secured report, there is no way to join together referrals with their associated candidate data in the same row if no application exists yet.

The Referrals linked on Job Requisition links to Job Requisition which links to Application which links to Candidate – but the candidate restriction gets lost in the relationship chain at the Job Requisition table.

The Referrals linked on Application maintains the candidate join but cannot show Forwarded and Invited to Apply records.

Keywords

ERP; Employee Referral; Forwarded; Fwd; Reporting; Analytics; Agency Candidate; , KBA , LOD-SF-RCM , Recruiting Management , Problem

Product

SAP SuccessFactors Recruiting all versions