What is the order being taken in consideration when returning candidates on the Candidate Search page?
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP SuccessFactors Recruiting Management
- Candidate Search;
Reproducing the Issue
- Go to Recruiting -> Candidates;
- Keyword and Item Search;
- In the search criteria, set the State to be equals to Washington;
- Notice that the results don't come in a specific sorting, but if you do this same search again, it will also come in the same order again:
This is because the system is not searching using a specific Database Query, but the search is being performed in an Index.
We can think of the Database Index as a Book index. Let's say you want to search though a book a 1000 pages long, you would have to look through every single page to find what you are looking for without the index. On the database it is not different, the index will create sections of information, like pairs, so it will reduce the amount of information that it has to go through to find the specific information you are looking for. Instead of going record by record on the database, the system will look through the index of grouped information, finding the information it is looking for, it will return the specific information that you want, in this case, Candidate information.
This is why also you have the same order when searching over and over again by using the same parameters, or criteria, you are still searching through the same index.
We cannot predict the order that the information will return back, since the indexes are automatically generated on our databases and they are created focusing on optimizing the search performance, which when working in a huge base of candidates is something crucial.
search, order, candidate, index, return, page, database, recruiting, result, criteria, parameter, keyword , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , How To