
Creating a job posting in SAP SuccessFactors is straightforward once you understand the system’s workflow. I’ll walk you through the core steps, drawing from my experience setting up thousands of requisitions.
First, log into your SAP SuccessFactors instance and navigate to the Recruiting Management module. Look for the “Create Requisition” button—usually located on the dashboard or under the “Jobs” tab. You’ll be prompted to fill in job details: title, location, department, and employment type.
The critical part is the Job Description, which must be clear and compliant with local labor laws. Use structured fields like “Minimum Qualifications” and “Preferred Skills” to improve candidate matching. SAP’s AI-powered search works best when you include specific keywords (e.g., “SAP HCM consultant” or “certified payroll specialist”).
Next, set up the approval workflow. In SAP, you can route the requisition through a predefined chain—hiring manager, HR business partner, and compensation team. I recommend using a parallel approval for non-sensitive roles to speed up time-to-fill.
Finally, configure publishing channels. SAP SuccessFactors integrates with job boards like Indeed, LinkedIn, and Monster. Toggle the “Post Externally” checkbox and select the relevant sites. For internal mobility, enable the Internal Career Site option.
Below is a quick comparison of common SAP modules for job creation:
| Module | Key Feature | Best For |
|---|---|---|
| SAP SuccessFactors Recruiting | End-to-end job posting, AI matching | Medium to large enterprises |
| SAP ERP HCM (On-Premise) | Manual requisition via PA20/PA30 | Legacy systems, high customization |
| SAP Fieldglass | Contingent workforce job creation | Gig workers, contractors |
One common mistake: forgetting to activate the requisition after saving. Always check the status—it should change from “Draft” to “Open” or “Active.” Also, ensure your job title standards align with the company’s job architecture to avoid duplication.
If you need to clone an existing job, use the “Copy Requisition” function. This saves time by copying fields, salary ranges, and posting rules. Just remember to update the job ID and expiration date.
For a smooth experience, test the entire flow in a sandbox environment first. This helps you catch errors in approval chains or posting logic before going live.

I’ve been setting up jobs in SAP for years, and the trick is knowing which transaction code to use. In the classic SAP ERP (ECC), go to SE80 or use PA20 for personnel actions. But honestly, most companies now use SuccessFactors. If you’re on the cloud, just click “Create Job” from the Recruiting Dashboard.
One thing I always do is double-check the validity dates. A job that’s left open for months can flood your system with outdated applications. My rule: set the closing date to 30 days unless it’s a difficult-to-fill role.
Don’t forget to assign a hiring manager in the workflow. I’ve seen jobs stuck because no one was set as the approver.

From a candidate experience perspective, the way you create a job in SAP matters a lot. I’ve applied to companies where the job description was just a copy-paste from a generic template. That’s a red flag.
When you’re filling out the SAP requisition fields, make sure to include a salary range and remote work options. SAP has a “Work Location Type” dropdown—set it to “Hybrid” or “Remote” if applicable.
Also, use the “Custom Questions” feature to filter out unqualified applicants early. For example, ask “Do you have 5+ years of SAP Basis experience?” as a yes/no mandatory question.

I’m all about automation in SAP. Instead of manually creating each job, I set up integration with our ATS via SAP CPI (Cloud Platform Integration). That way, when a manager submits a request in an external tool, a job is automatically created in SuccessFactors.
For high-volume hiring, I use bulk upload via Excel. Export the template from Admin Center → Import/Export → Job Requisition Import, fill in the data, and run the import. Just be careful with the field mapping—one mismatch can break the entire batch.
My advice: always check the error log after a bulk upload. SAP generates a detailed report of failed rows.

You need to think about governance when creating a job in SAP. I’ve seen cases where duplicate job IDs were created because the approval workflow was bypassed.
Make sure your job numbering scheme is clear. For example, use JOB-2026-001 for the first requisition of the year. SAP often auto-generates IDs, but you can override them in the “Job Requisition ID” field.
Also, restrict access to the “Create Job” function. Only authorized recruiters and HR admins should have that permission. I’ve seen junior staff accidentally post a job with the wrong salary range, causing compliance issues.


