SAP SuccessFactors Connector

Sync SAP SuccessFactors employee, employment, job, compensation, and foundation data into your warehouse with OIDC auth and incremental reads.

SourceBronze

Start Free View Documentation

Evaluating against Fivetran? See how Supaflow handles SAP SuccessFactors pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

OIDC Client Credentials Authentication

Connect through SAP Cloud Identity Services using the OAuth 2.0 client credentials grant. A technical user mapped to your OIDC application authorizes OData access, so no SuccessFactors username or password is stored.

Full Catalog Discovery

Supaflow discovers the entity sets your instance exposes through its OData metadata, across modules such as Employee Central, Recruiting, and Performance and Goals. New objects appear after a schema refresh instead of being hard-coded in the connector.

Incremental and Full-Refresh Sync

Objects that expose a last-modified timestamp sync incrementally and fetch only changed records. Objects without one are fully refreshed, and the object list shows the mode for each.

Effective-Dated History

Job, compensation, and other effective-dated objects load their full history. Set a Historical Sync Start Date to bound how far back the first sync reaches, or leave it blank to load all available history.

Per-Object Field Selection

Choose the fields you need for each object and Supaflow requests only those from SuccessFactors. Heavy fields, such as employee photos, are skipped entirely when you do not select them.

Permission-Aware Reads

The connector reads only what the technical user's Role-Based Permissions allow, so you control object and field access from inside SuccessFactors. Newly granted objects become available after a schema refresh.

Supported Objects

Employee Central

People and employment

Core Employee Central objects such as User, PerPerson, and EmpEmployment that describe the people in your organization and their employment with the company.

Job and compensation history

Effective-dated objects such as EmpJob and EmpCompensation load their full history so you can analyze changes over time.

Foundation Objects

Organizational structure such as legal entities, departments, and business units (FOCompany, FODepartment, FOBusinessUnit).

Discovered From Your Instance

Queryable entity sets

Every entity set exposed by your instance's OData service can appear in schema discovery, across the SuccessFactors modules you have enabled. The available list is account-specific.

Incremental eligible

Objects become incremental when SuccessFactors exposes a filterable last-modified timestamp for them; the rest remain available for full refresh.

Not Yet Supported

Parent-scoped and feature-gated entities

Entity sets that cannot be queried directly as a complete collection (returned only when expanded from a parent, requiring a key or filter, or feature-gated) are not offered as standalone tables.

Large binary attachments

Attachment payloads are skipped to keep syncs reliable. Contact support at support@supa-flow.io with the objects you need.

How It Works

Configure an OIDC application in IAS

In SAP Cloud Identity Services, create or open an OIDC application for SuccessFactors, create a client ID and secret for the client credentials grant, and add SuccessFactors as a dependency with the Technical User Access API (sf_technical_access), not Principal Propagation. Note the Dependency Name.

Map a technical user in SuccessFactors

Map the OIDC application to a technical user in SuccessFactors so the issued token can read OData, and grant that user Role-Based Permission to read the objects and fields you plan to sync. SAP support can complete the mapping if it is not available in your admin console.

Enter connection details in Supaflow

Create a SAP SuccessFactors source and enter the SuccessFactors API Host, IAS Token URL, OIDC Client ID, OIDC Client Secret, and Resource Dependency Name. The client secret is stored encrypted.

Set optional sync settings

Leave advanced settings at their defaults for most instances. Use Historical Sync Start Date to bound how far back history loads on the first sync, and Page Size to control records requested per page.

Test and save

Click Test & Save. Supaflow authenticates with IAS, reads a sample record, and then discovers the SuccessFactors objects available to the technical user.

Use Cases

People and workforce analytics

Land employee, employment, job, and compensation data in your warehouse so people analytics and HR teams can build reporting models outside the SuccessFactors UI.

Headcount and organizational reporting

Combine person and employment records with Foundation Objects such as departments and business units to report on headcount and organizational structure.

Compensation history analysis

Use the full effective-dated history of job and compensation objects to analyze pay changes and job movements over time.

Frequently Asked Questions

How does Supaflow authenticate with SAP SuccessFactors?

Supaflow uses SAP Cloud Identity Services with the OAuth 2.0 client credentials grant. A technical user mapped to your OIDC application authorizes OData access, so no SuccessFactors username or password is stored in Supaflow.

What is the Resource Dependency Name?

It is the dependency name configured for SuccessFactors on your IAS application, found under Application APIs and Dependencies. Enter just the name; the full resource URN is also accepted.

Which objects can I sync?

Supaflow discovers entity sets dynamically from your instance's OData metadata. The available objects depend on the SuccessFactors modules you have enabled and the Role-Based Permissions granted to the technical user.

How does incremental sync work?

An object syncs incrementally when SuccessFactors exposes a filterable last-modified timestamp for it, fetching only records changed since the last run. Objects without one use full refresh.

How is historical data handled?

Effective-dated objects such as job and compensation history load their full history. By default the connector loads all available history; set a Historical Sync Start Date to limit how far back the first sync reaches.

Why is an object or field missing?

SuccessFactors follows Role-Based Permissions. Objects the technical user cannot access are still listed but fail at read time, and a single restricted field makes its object fail until you grant the field or deselect it. Some entity sets are also not queryable as standalone tables. Grant the access you need (or deselect what you do not), refresh the schema, and re-run the sync.

Does Supaflow capture deletes?

The connector reads SuccessFactors deletion markers where the source exposes them. Records that simply disappear from the source without a deletion marker are not emitted as delete events.

Can I run SAP SuccessFactors pipelines natively inside Snowflake?

Yes. Supaflow runs as a Snowflake Native App via Snowpark Container Services, so SuccessFactors data can be extracted and loaded without leaving your Snowflake account.