Recruiting Fundamentals: Purpose, Process Flow, and Core Objects
Introduces why organizations use SAP SuccessFactors Recruiting, the end-to-end hire process, and the core objects (requisition, candidate profile, application) that consultants must understand before configuring anything.
Explanation
SAP SuccessFactors Recruiting is a cloud talent acquisition solution used to attract, screen, interview, and hire candidates, then hand the selected candidate off to Onboarding and ultimately Employee Central. It is typically split into two connected products: Recruiting Marketing (career site, sourcing, candidate relationship management) and Recruiting Management (requisition workflow, candidate application processing, interview scheduling, offer approval). Understanding this split matters because customers may license only Recruiting Management, only Marketing, or both, and the configuration scope differs accordingly. The process typically begins when a hiring manager or HR business partner initiates a job requisition, which represents an open position to be filled. The requisition carries attributes such as job title, department, location, hiring manager, recruiter, and approval workflow. Once approved, the requisition can be posted internally, externally, or both, generating a job posting that candidates see on a career site or job board. A candidate applies by creating or updating a candidate profile, which is a persistent record of the person's professional history independent of any single requisition. When a candidate applies to a requisition, an application object is created, linking the candidate profile to that specific requisition and tracking status (e.g., new, screened, interviewing, offer, hired, or disqualified). This separation between candidate profile and application is a foundational data model concept: one candidate profile can have multiple applications over time, but each application is tied to one requisition. Recruiters and hiring managers interact with applications through status flows, which are configurable pipelines representing the stages a candidate moves through. Interview scheduling, background check integration, and offer management typically hook into specific statuses. Once an offer is accepted, the record can be transitioned to Onboarding, which begins the new hire's pre-day-one experience and eventually creates or updates the Employee Central record. For a beginner consultant, the critical mental model is: requisition (the job) -> posting (visibility) -> candidate profile (the person) -> application (the person's pursuit of that job) -> status flow (progress) -> offer -> hire -> handoff to Onboarding/Employee Central. Misunderstanding this chain is one of the most common sources of confusion in early-stage projects, because business stakeholders often use
Real project scenario
On a mid-size retail company's SuccessFactors rollout, the project team initially treated 'candidate' and 'application' as the same object during requirements workshops, which led to incorrect assumptions about reporting (they expected one row per candidate rather than one row per application). Clarifying the data model early in discovery sessions prevented rework in the reporting and integration design phases.
Common mistakes
• Treating candidate profile and application as the same object, leading to incorrect reporting expectations • Assuming every customer uses both Recruiting Marketing and Recruiting Management when only one may be licensed • Not clarifying with the business whether requisitions require multi-level approval before posting • Overlooking that a candidate can have multiple applications across different requisitions over time • Assuming job posting automatically means the requisition is approved, without confirming approval workflow status
Best practices
• Always confirm with the customer which Recruiting products are licensed (Marketing, Management, or both) before starting design • Map the full requisition-to-hire lifecycle in a diagram during discovery to align business and technical stakeholders • Clarify early whether reporting requirements are at the candidate level or application level • Document the requisition approval workflow explicitly, since it strongly influences configuration decisions • Validate understanding of status flow terminology with the customer, as naming conventions vary by industry
Interview angle
Interviewers often ask candidates to explain the difference between a candidate profile and an application, and to describe the end-to-end requisition-to-hire flow. Being able to clearly separate these objects and explain the handoff to Onboarding demonstrates genuine functional understanding rather than surface-level familiarity with screen navigation.