- What is an index/re-index?
- In what situations should I request an index/re-index?
- How to request an instance index/re-index?
SAP SuccessFactors Recruiting Management
Important Note: The initial index is not required anymore. Once the RCM module is enabled, the index is automatically created. Uploading the Candidate profile XML or changing it does not require a instance reindex.
Changes to the candidate profile will rarely require a re-indexing of the search index. Only the following change to the candidate profile template may require a re-index:
- After an import of new candidates thru legacy import - Check article 2279481 for more detail;
- Changing the field type of a field;
- Issues with the search tab or search results - For this topic, support team will validate if the reindex is necessary;
Tip: It is not recommended to change the field type of a field for live customers, as this can cause application errors on existing records storing data that do not match the new field type.
Indexing is not required for any other candidate profile change;
How to request an re-index:
In order to request a re-index, please open a Support incident with the following information:
- Company ID;
- Data Center;
- Reason for the request;
NOTE: Please be aware that these information are mandatory, if you open an incident without one of these information, Operations team will not proceed with the request. It is also important to mention that for clients under an implementation process, all the required Index/Re-Index requests must be performed by the customer's implementation partner, as they have all the required accesses and trainings to perform this task and would be ready to assist the clients in case anything goes wrong.
2279481 - Candidate imported via Legacy Data Migration but is not visible in the system - RCM
Index, Re-index, Build index, first index, candidate profile index, xml, template, refresh, build, reindex , KBA , LOD-SF-RCM , Recruiting Management , How To