Recruiters using SAP SuccessFactors have a Candidate Search bar and Talent Pools, allowing them to find matching profiles by skill, tag, or location. However, these tools do not automatically identify strong candidates from previous requisitions for new roles.
That oversight can lead to qualified applicants being overlooked each year across multiple countries and business units. Every closed requisition leaves behind reviewed, parsed, already scored candidates that the system never revisits automatically.
This expert guide explains what tools SAP SuccessFactors provides recruiters for finding people already in the system. It also covers their limitations and how an AI integration addresses those to automate sourcing and scoring past applicants.
What Is Candidate Rediscovery?
Candidate rediscovery involves matching existing profiles in your SAP SuccessFactors database to newly opened roles. This includes applicants from previous requisitions, those in talent pools, and candidates who have partially completed the hiring process.
By automatically checking past candidates against new openings, your application history becomes a valuable sourcing channel. Unlike manual searches, rediscovery ensures that this check occurs every time a role opens, streamlining the hiring process.
Does SAP SuccessFactors Provide Candidate Rediscovery?
No, SAP SuccessFactors doesn't provide a candidate rediscovery feature, nor any way to source past qualified applicants automatically. Instead, it has a Candidate Search component with three methods:
- Simple Search: This searches resumes, candidate profiles, and cover letters.
- Tag Search: This finds candidates with specific tags.
- Advanced Search: This combines keywords, profile fields, and tags in one query.
Search results can display a five-star relevancy ranking that shows how closely each candidate matches the criteria entered. The recruiting module also includes Talent Pools, created and maintained under Candidate Relationship Management, where recruiters group candidates and later assign them to an open requisition.
Both tools depend on a recruiter typing in criteria or opening a specific pool. Neither scans closed requisitions automatically when a new one opens, and neither carries a match score explaining fit against that new role's requirements. Rediscovery still depends on someone remembering a candidate exists and searching for them directly.
How to Rediscover Talent in SAP SuccessFactors
Since SAP SuccessFactors has no built-in way to automatically source, score, or surface past applicants across requisitions, recruitment teams connect Skima AI to scan that history every time a role opens. Below is a 5-step workflow, from connecting your account to a finished shortlist:
Step 1: Connect Your SAP SuccessFactors Account With Skima AI
Set up OAuth 2.0 credentials with read access to candidate data and write access to custom fields. This connection uses SAP's own OData APIs directly for cloud instances, or middleware for on-premises HCM systems. Skima AI needs both read and write access to function.
- Read access: candidate profiles, job applications, requisition details, and resume attachments
- Write access: custom fields, candidate tags, and activity logs
- Pulled data: candidate contact details, resumes, application status, and requisition requirements for scoring context
- Event notifications: application creation and updates, requisition stage changes, and document attachments
If webhooks are not supported in your environment, Skima AI falls back to safe polling every 10 to 15 minutes.
Step 2: Configure Custom Fields and Confirm the Connection
Create custom fields in the 4000 series used for recruiting data, or authorize Skima AI to provision them during setup. These are the Skima AI match score, a number from 0 to 100, and reasons, a long text field listing reasons for the fit. A Skima Screened tag gets added at the candidate level, so screened applicants stay filterable inside SuccessFactors.
Optional hiring manager feedback and comments capture responses once a shortlist goes out, logged in SAP's standard activity tracking.
Before rolling this out further, validate it on two or three test requisitions. Upload a resume, then confirm the Match Score and Reasons actually appear on that application, and check that the activity log captures the entry correctly.
Step 3: Launch Talent Rediscovery Against a Live Requisition
Open the job inside Skima AI, from the Jobs list or from within the job itself. Click the three-dot Actions menu and select Rediscover Candidates. A modal lets you scope the scan two ways. Limit it to a saved candidate segment, or leave it open to every synced SuccessFactors record.
Set the Candidate Created Date range next: All time, Last 6 months, Last 1 year, or a custom window, then click Apply. Skima AI scans the selected pool against this requisition's specific requirements and sends a notification once the scan finishes. Refresh the page to see the results.
Step 4: Review and Filter the Rediscovered Matches
Open the View Candidates tab to see a ranked list pulled from across your entire application history. Each candidate carries an AI match score and reason bullets explaining the fit. Filter by Industry, Work Mode, Experience Level, Notice Period, Location, and Salary Range.
Start broad and tighten the filters gradually. Narrowing too fast hides good candidates, including people who ranked lower in an earlier Candidate Search but line up well against this requisition.
Step 5: Shortlist and Sync Feedback Back to SAP SuccessFactors
Build your shortlist from the ranked matches Skima AI surfaced. Generate a secure, no-login link and send it to the hiring manager. They can click a thumbs up, thumbs down, or maybe on each candidate, with an optional comment.
Skima AI writes that decision back into SuccessFactors through the same API connection for the audit trail, logging it in SAP's standard activity tracking. The feedback stays visible on the record without anyone opening a second tool.
What If Your SAP SuccessFactors Database Is Duplicated
SAP SuccessFactors includes a duplicate detection and merge system, but it requires admin oversight rather than automatic functionality for all recruiters. The system identifies potential duplicates by analyzing the candidate's first name, last name, and postal address, displaying a yellow warning icon on the affected profile.
Furthermore, an admin with the Manage Duplicate Candidates permission can access a potential-duplicate list that scans the entire candidate database. They can also search for specific profiles by email and merge them directly, transferring job applications from the discarded profile to the active one.
However, this process relies on someone with the necessary permissions to regularly check the list. Internal candidates cannot be merged, and profiles with outdated phone numbers or old resumes remain untouched unless they also match another profile by name and address. The detection logic focuses solely on duplicates, ignoring stale information.
In contrast, Skima AI manages this as ongoing maintenance. It prioritises matching by email, phone, or LinkedIn URL, and uses name, location, and company as backup signals.
Before merging, a field comparison modal displays the differences between records. Missing details are filled in through contextual profile enrichment. A dedicated Duplicates tab logs all resolved cases, organised into In Database, From Uploads, and Resolved sub-tabs for easy access.
5 Benefits of Talent Rediscovery with Skima AI
Talent rediscovery with Skima AI changes what a SuccessFactors team can do with its own application history in 5 specific ways:
- Faster Time-to-Screen: Rediscovered candidates arrive already scored, so recruiters skip the raw resume pile entirely. In a documented 30-day SuccessFactors pilot, a team reduced time-to-screen by 58%.
- More Interviews From the Same Shortlist: The same pilot saw interviews from the top shortlist double compared to the prior process.
- Explainable Match Scores With an Audit Trail: Every rediscovered match carries reason bullets tied to skills and experience, logged in SAP's activity tracking alongside a Skima Screened tag for instant filtering.
- Hiring Manager Engagement Without a New Login: The shortlist feedback loop keeps managers responding through a link, no SuccessFactors credentials required. Manager satisfaction rose 24 points on NPS in that same pilot.
- Lower Cost Per Hire on Repeat Roles: Rediscovered candidates were already sourced once, so filling a role you've hired for before needs zero new job board spend.
5 Best Practices to Rediscover Talent in SAP SuccessFactors
These benefits do not happen automatically in SuccessFactors without some intentional habits. The 5 practices below focus on search timing, data hygiene, and integrating rediscovery into a large, multi-entity SAP environment:
- Check Candidate Search and Talent Pools First, Then Widen the Scan: Candidate Search and Talent Pools already cover candidates a recruiter has actively grouped or searched for. Use Skima AI's Talent Rediscovery to reach the much larger set of closed-requisition applicants that neither tool checks again.
- Turn On Automatic Rediscovery for Every New Requisition: Skima AI's setting under Preferences and General starts a database scan the instant a new job is created. Enable it so no requisition slips through without a first look at your existing applicant history.
- Use Reverse Search for Candidates From a Different Business Unit or Country: A candidate who searched well for one location or division often fits an opening elsewhere in a large organization. Reverse Search starts from that profile and returns every open job they match, ranked by score.
- Segment Scans With the Candidate Created Date Filter: Choose a 6-month or 1-year window when a role needs someone who was recently active. Widen to All time for a niche or hard-to-fill role where the applicant pool has always been thin.
- Coordinate the Duplicates Tab With Your SAP Admin's Merge Schedule: Since duplicate merging in SuccessFactors depends on an admin checking a potential-duplicate list, reviewing Skima AI's Duplicates tab on the same schedule catches records the admin process was never built to reach.
Is Candidate Rediscovery Worth It for Your Recruitment Team?
A SuccessFactors system used across various business units or countries gathers thousands of profiles. Once a requisition closes, Candidate Search or Talent Pool rarely revisits these profiles. This backlog is valuable; candidates who excelled in one location may suit similar openings elsewhere. However, recruiters can only connect these dots through name searches.
Setting up Skima AI in an SAP environment requires careful coordination. IT must configure OAuth 2.0 credentials, create custom fields in the 4000 series for recruiting data, and confirm OData API access, especially if any HCM components remain on-premise. This setup isn’t unusual for SAP rollouts, but it isn't instant.
For smaller entities with few open roles, this backlog feels thin, complicating the setup justification. Conversely, large enterprises using SuccessFactors benefit significantly from the candidate history behind each closed requisition, which rediscovery aims to utilize.
Pilot Talent Rediscovery in SAP SuccessFactors Now
For mid-size and enterprise businesses hiring at high volume across SAP SuccessFactors, a pilot with Skima AI can deliver high ROI. The right move is not to switch every business unit over at once. Start with two or three live requisitions, ideally ones your company has filled more than once before.
Connect Skima AI, configure the custom fields, and launch Talent Rediscovery on those roles. Skima AI's own SAP integration structures this as a 30-day pilot, with checkpoints at day 15 and day 30.
Track time-to-screen, how many rediscovered candidates reach an interview, and hiring manager response. Based on a documented 30-day SuccessFactors pilot, expect something close to a 58% drop in time-to-screen and double the interviews from your top shortlist. From there, expanding to more requisitions becomes a decision backed by your own data, not a guess.
Frequently Asked Questions
1. Does SAP SuccessFactors have a built-in talent rediscovery feature?
No, SAP SuccessFactors does not have a built-in talent rediscovery feature. Its recruiting module offers Candidate Search, with Simple, Tag, and Advance Search methods. Plus Talent Pools under Candidate Relationship Management. Neither scans closed requisitions automatically nor scores a past applicant against a newly opened role.
2. How to source qualified past candidates in SAP SuccessFactors?
To source qualified past candidates in SAP SuccessFactors, connect Skima AI to SuccessFactors through OAuth 2.0 credentials and OData API access, configure custom fields in the 4000 series, then launch Talent Rediscovery on a live requisition. Skima AI scans your application history, ranks candidates, and syncs hiring manager feedback back automatically.
3. What are the benefits of SAP SuccessFactors candidate rediscovery?
Rediscovered candidates arrive pre-scored, cutting screening time by over 58% in a documented 30-day pilot and doubling interviews from the top shortlist. Matches carry explainable reasons, a Skima Screened tag for filtering, and hiring manager feedback without a new login.
4. Is Skima AI safe to integrate with SAP SuccessFactors for talent rediscovery?
Yes, Skima AI encrypts candidate data in transit and at rest, follows GDPR, SOC 2 Type II, and ISO 27001 practices, and logs every AI decision and manager response in SAP's standard activity tracking. Scores rely on resume-based evidence only, with no automatic rejections.
5. Is candidate rediscovery useful for SAP SuccessFactors' typical customers?
Yes, especially for large enterprises operating across multiple business units or countries that refill similar roles over time. The value grows the more often the same kinds of positions, and sometimes the same candidates, come back into play.
