When creating a Recruiting report in either Reports Table or Detailed Reporting (same live data source as the Report Table), the user states the generated results display duplicate lines of information within the report.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP Success Factors Recruiting Management
The short answer is that they are not duplicates.
There are 3 scenarios to be considered:
- If there are several columns, one of the columns might have one different value: it could be a slight difference, but the system will show two different rows.
- The columns are all the same, but you have date type of fields: Usually these fields store not only the date, but the time as well. This will be shown when you go to the Configuration tab to configure the fields to display as a timestamp. More details on how to this are described in this KBA: 2354874 - How to display the date and time in adhoc for date fields - Recruiting Management
- The lines appear to be duplicates because only a limited amount of columns from the table were selected to view: by extending the view to include all of columns from the used tables the differnce between the "duplicate" line can be seen.
The data is stored in tables containing groups of data. For example:
- Table 1 = Job request fields
- Table 2 = Application fields
- Table 3 = Audit trail information
- Table 4 = Operator information
This grouping allows selecting specific data needed to report from a specific group of data.
Please keep in mind data is exclusive to that table based on the criteria for that group. Meaning 2 tables may lead to duplicates as the data is unique to each table.
You would like to report on a Job Requisition, and it had 3 applicants and also 3 operators (recruiter, hiring manager, VP of HR).
- If you just want a report that shows the Job Requisition ID and the Application ID associated with the Requisition, then you will probably get a report with 3 lines.
- If you want a report with the Job Requisition ID, the Operators and the Application ID associate with the Requisition, then you will probably get a report with 9 lines.
- If you want a report with the Job Requisition ID, the Operator, Application ID and when the last time the application was updated, then you might get more than 9+ results.
- The application last update could be an operator updating the template, this change will apply to all applications;
- Or, one candidate updating their application. This will count as one update;
- Or, an operator moving application in mass, all of these applications will get an last update date;
The lines appear to be duplicates because you selected to view only a limited about of columns from the table. Hence, if you extend the view to include all of columns from the used tables you will eventually see the difference in the duplicate lines. The thing to have in mind is that the more data you include in your report, the most likely you will see so-called duplicates entries, especially if the data is coming from different groups.
The best approach is report small data sets and then add then to see if the report makes sense, or need additional configuration, such as filters.
SF, Success Factors, RCM, Recruiting, Multiple, copies, ad hoc, reports, duplicates, rows duplicated, row duplicates, ad hoc report duplicates , KBA , sf recruiting , LOD-SF-RCM , Recruiting Management , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , LOD-SF-ANA-ADH , Adhoc Reports & Report Builder , How To