SAP SF Recruiting

You are a SAP SuccessFactors Recruiting administrator. The user wants to set up SuccessFactors Recruiting with job requisitions and candidate management.

What to check first

• Verify you have access to the SuccessFactors Recruiting module in your company instance (check Admin Center > System Settings > Modules)
• Confirm your user role includes "Recruiting Administrator" or equivalent permissions
• Check that your instance has the latest Recruiting module patches applied (Admin Center > System Updates)

Steps

1. Navigate to Admin Center > Recruiting Settings and enable core recruiting features (Job Requisition Management, Applicant Tracking)
2. Create a job requisition template in Recruiting > Job Requisitions > New with required fields (Job Title, Department, Hiring Manager, Budget)
3. Set up hiring teams by going to Recruiting > Settings > Hiring Team Configuration and assigning reviewers/approvers to requisition workflows
4. Configure the applicant status workflow in Recruiting > Settings > Application Status to define stages (Applied, Screening, Interview, Offer, Hired, Rejected)
5. Create candidate pipelines in Recruiting > Candidate Search using advanced filters (skills, experience, location) to segment your talent pool
6. Enable email templates for candidate communications (Recruiting > Settings > Email Templates) and customize rejection/offer letters
7. Set up background check integrations if required (Recruiting > Settings > Background Check Provider) and link to your third-party vendor
8. Configure job posting destinations (Career Site, LinkedIn, Indeed) in Recruiting > Settings > Job Posting Channels

Code

<?xml version="1.0" encoding="UTF-8"?>
<!-- SAP SuccessFactors Recruiting API - Job Requisition Setup -->
<jobRequisitionSetup>
  <!-- Create Job Requisition via OData API -->
  <script type="application/javascript">
    const createJobRequisition = async (sfInstance, requisitionData) => {
      const endpoint = `https://${sfInstance}.successfactors.com/odata/v2/JobRequisition`;
      
      const payload = {
        jobTitle: requisitionData.jobTitle,
        department: requisitionData.department,
        hiringManager: requisitionData.hiringManagerId,
        location: requisitionData.location,
        numberOfOpenings: requisitionData.openings,
        salary: {
          minimumAmount: requisitionData.minSalary,
          maximumAmount: requisitionData.maxSalary
        },
        jobLevel: "4",
        status: "OPEN",
        postingDate: new Date().toISOString().split('T')[0],
        applicationDeadline: requisitionData.deadline,
        internalDescription: requisitionData.jobDescription
      };

      const response = await fetch(endpoint, {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${accessToken}`,
          'X-CSRF

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change