SAP SuccessFactors Jobs Feed Implementation Guide

This document defines the requirements and process for implementing a Jobs Feed integration between SAP Success Factors Recruiting and Radancy Talent Acquisition Cloud (TAC).

Scope Overview

The Jobs Feed serves as the primary source of truth for open job requisitions displayed on the Radancy Career Site and supports downstream Radancy modules.

Additional integrations may be required based on the Radancy modules under contract, including but not limited to CRM, Employee Referrals, Hiring Events, Screening & Scheduling, Insights & Analytics, and Programmatic AdTech.

Out of Scope

This is a one-way integration from SAP SuccessFactors Recruiting to Radancy. This document covers job requisition data only. Applicant data is out of scope and is handled separately if contracted.

Integration Summary

Integration Details

• Integration Type: API-based job feed
• Integration Method: SAP SuccessFactors OData API (v2)
• Data Direction: SuccessFactors → Radancy
• Data Format: JSON (preferred)
• Authentication: OAuth, Basic Authentication, or no authentication (tenant-dependent)
• Refresh Frequency: Up to four imports per day (standard), configurable

Integration Architecture

The integration retrieves job data from SAP SuccessFactors Recruiting via a configurable OData query and processes it through the Radancy Job Importer before publishing to the Radancy platform for career site display and downstream processing. Job data is refreshed during scheduled import cycles.

Feed Configuration

The SuccessFactors integration is configured using a client-specific OData request URL.

Required Inputs

• API Host URL (e.g., https://api12.successfactors.com)
• Company Identifier (tenant ID)
• Request URL (OData query)

Request URL Structure

The request URL defines:

• filtering criteria
• selected fields
• expanded entities

Example structure:

The request URL is configured and maintained by Radancy and may be updated based on client configuration and business requirements.

Reference: SAP SuccessFactors OData API Documentation

Data Retrieval Model

The integration uses a query-based retrieval model that leverages a configurable OData query.
The query retrieves:

• job requisition data
• posting data (jobReqPostings)
• localized content (jobReqLocale)
• organizational attributes
• recruiter and hiring manager details

To ensure performance and efficiency, a restricted field set is used. Only required fields are included in the query, and additional fields must be explicitly configured.

OData parameters used:

• $filter — defines job eligibility
• $select — limits returned fields
• $expand — retrieves related entities

This approach enables retrieval of all required job data in a single response.

The query structure is optimized for performance and may vary by client implementation. The integration supports both standard and custom field mappings based on client-specific Job Requisition Templates.

Job Eligibility Logic

Job eligibility is controlled through the OData query.

Filtering is configured per client and typically includes:

• job status (e.g., approved or open)
• posting status
• posting destination / board
• job family requirements

Example:

Pagination Handling

SuccessFactors OData APIs support pagination using:

Example:

The Radancy Job Importer continues requests until all records are retrieved.

Authentication & Security

Supported authentication methods include:

OAuth (recommended)

• Token endpoint
• Client credentials
• Grant type
• Assertion

OAuth authentication may require additional configuration depending on the client’s SuccessFactors environment. This can include certificate-based setup and identity configuration aligned with SAP requirements.

Reference: SAP SuccessFactors OAuth Configuration Guide

Basic Authentication

• Username and password (tenant-dependent)

No Authentication

• Only applicable if the endpoint is publicly accessible

Authentication requirements are determined by the client’s SuccessFactors configuration and may vary by tenant. Radancy will configure and validate authentication during implementation.

Required Client Configuration

Clients must provide:

IP Whitelisting (if required)

Some SuccessFactors environments require IP address whitelisting to allow API access. If enabled, the client must allowlist Radancy IP addresses prior to integration.

Known Integration Considerations

Data Variability

Field availability and structure vary by client configuration.

Location Data

Location data in SuccessFactors is configured through location objects and may vary by client implementation. In some cases, location values may not be fully normalized across city, state, and country fields.

Clients are responsible for ensuring location data is configured correctly within SuccessFactors. Radancy will validate and map location data during implementation and may identify discrepancies that require alignment.

Multi-Location Jobs

Multi-location jobs are configured within SuccessFactors and may vary based on the Job Requisition Template.

Radancy’s preferred approach is to support a single requisition with multiple associated locations, where supported by the client’s configuration.

Display and handling of multi-location jobs are confirmed during implementation based on client requirements.

Localization

Multi-language content is supported via the jobReqLocale object.

XML Feed Alternative

XML feeds may be available via the SuccessFactors career site; however, these feeds are typically limited in available fields and depend on UI configuration. API-based integration is the preferred approach.

Application URL

Apply URLs may require configuration based on the client’s SuccessFactors setup. Clients should confirm the expected apply URL format to ensure proper redirection from the career site.

Example format:

ATS Constraints

SuccessFactors may limit:

• field exposure
• configuration changes
• tracking implementation

Job Feed Data Requirements

Below is a list of required, recommended and optional fields. The customer/ATS must provide the fields and data in the format to be displayed on their career site. Please note that certain fields (not all are displayed on your career site) will be required/recommended to support your Radancy TAC platform (i.e. CRM, Employee Referrals, Hiring Events, Programmatic AdTech, etc.)

Notes:

Referrals: If all correlated fields are included in the jobs feed integration, jobs are automatically published within the Employee Referrals dashboard (ready to refer). If any jobs are missing required data, they will instead be listed under “draft” status requiring manual intervention by the customer (recruiter) to complete. Once completed, the job can then be published and “enabled” to begin referring. If any data is not available from your ATS, it is possible for Radancy to apply conditional logic to streamline workflow processes.

• Fields can be defaulted to a standard selected value (e.g., Reward plan is for all jobs “$500”)
• Fields can be conditionally mapped based on other fields (e.g., if experience level is “Entry”, Reward plan is “$100”, if experience level is “Advanced”, Reward plan is “$500”)

Please contact your assigned Digital Project Manager or Integration Specialist.

High-Level Implementation Timeline

*Timeline is subject to change based on implementation variables.