Overview
SmartRecruiters is SAP's next-generation recruiting platform, integrated within the SAP SuccessFactors HCM suite. When creating job postings, recruiters work with a set of standard job fields that directly influence the candidate experience on the career site — how jobs are categorised, filtered, and discovered.
Five fields are especially important: Location, Function, Industry, Experience Level, and Type of Employment. These are structural picklist fields that drive job-board categorisation, candidate search filters, and downstream application workflow logic.
As documented in KBA 3746432, there is currently a product gap: these fields cannot be automatically populated from a Position object in SAP SuccessFactors. This means every job created via Position must have these fields manually updated by a recruiting stakeholder — an inefficient and error-prone process at scale.
This blog presents a supported workaround using the SmartRecruiters REST API combined with a job.created webhook to automate the update as soon as a job is created.
Understanding the Product Gap
The five affected fields and their impact on the recruiting process are summarised below:
Field | Type | Impact | Mappable from Position? |
Industry | Drop Down | Job board category; candidate search filter | Not available |
Function | Drop Down | Role category; drives career site taxonomy | Not available |
Experience Level | Drop Down | Seniority filter for candidates | Not available |
Type of Employment | Drop Down | Contract type; mandatory for many job boards | Not available |
Location | Structured/ Pre-defined | Country / region / city; drives geo-targeted postings | Not available |
Current state: Because these fields cannot be sourced from the Position, recruiters must manually open each newly created job and populate these fields before publishing. In high-volume recruiting organisations this introduces significant manual overhead and the risk of miscategorisation.
Source link