What should you consider regarding mapping candidate statuses for Advanced Analytics?

 According to the SAP Help Portal1, you should consider the following regarding mapping candidate statuses for Advanced Analytics:

Any status that indicates that the candidate was NOT hired, such as Automatically Disqualified, does need to be mapped. This is because all statuses must be mapped to one of the five standard statuses in Advanced Analytics: Apply Completed, Qualified, Interviewed, Offer Made, or Hired. If you have multiple not hired statuses, you can map them to ATS Capture, which is a hidden status that does not appear in the reports1.

After saving the status mappings in Command Center, you can correct mapping errors as long as you do it during the same session. This is because the status mappings are not pushed to the Advanced Analytics database until you log out of Command Center or close the browser. If you need to make any changes after logging out, you must contact SAP Customer Support to request a data purge and re-sync1.

With some exceptions, if a status is NOT mapped when the OData integration is run, the sync will fail. This is because the OData integration requires that all statuses are mapped to ensure data consistency and accuracy. The exceptions are when you have a new status that has not been used by any candidates yet, or when you have a status that is not used by any active job requisitions. In these cases, the sync will not fail, but you will receive a warning message and you should map the status as soon as possible1.

Status mappings can be completed even when there is no candidate data associated with each status on the Talent Pipeline. This is because the status mappings are based on the status names and not on the candidate data. You can map any status that exists in your Recruiting Management system, regardless of whether it has been used by any candidates or not1.

References: Career Site Builder Status Mappings in Advanced Analytics