Reference · built on requestConnectorHR, scheduling & workforce

SAP SuccessFactors

Employee Central person, employment, job, and time off entities from SAP SuccessFactors through its OData v2 API.

Request accessPricing ↗

About

SAP SuccessFactors is SAP's cloud HCM suite. Employee Central stores person data in Per* entities, employment and job data in Emp* and EmpJob* entities, and foundation objects in FO* entities, all exposed over OData v2 at https://<api-server>/odata/v2/ on per-data-center API servers such as api17.sapsf.com. Time Off adds EmployeeTime, TimeAccount, and TimeAccountDetail. Intelligent Services publishes Employee Central events to outside systems, and the SOAP Compound Employee API remains for replication.

An operator on Fibric reads job information, employment, and time accounts, and proposes an upsert to an effective-dated record or a time off entry for your approval. Each proposal is logged with its reason and its undo.

This is a reference listing. It documents what Fibric would read from SAP SuccessFactors and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Job information through EmpJob: manager, department, and job, keyed by userId, startDate, and seqNumber, with effectiveLatestChange for the last record per day
  • Employment through EmpEmployment and terminations through EmpEmploymentTermination
  • Person data through PerPerson, PerPersonal, PerEmail, and PerPhone
  • Compensation through EmpCompensation, EmpPayCompRecurring, and EmpPayCompNonRecurring
  • Time off through EmployeeTime, TimeAccount, TimeAccountDetail, EmpTimeAccountBalance, and TimeManagementAlert
  • Incremental loads filtered on lastModifiedDateTime, and Employee Central events published through Intelligent Services
  • Entity metadata through https://<api-server>/odata/v2/<Entity>/$metadata

Proposed actions

  • Target capability: propose an upsert to EmpJob, for example a manager or department change with an effective date
  • Target capability: propose an EmployeeTime record for an absence
  • Target capability: propose a correction to person contact data through PerEmail or PerPhone
  • Target capability: propose deleting a record by upserting it with operation set to DELETE

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reflect a manager change the day it takes effect

    Query EmpJob with effectiveLatestChange for records changed since the last run and propose the approval and access updates a new manager or department implies.

    With Onboarding Checklist, Access Review

  • Watch time accounts before leave is booked

    Read TimeAccount and EmpTimeAccountBalance alongside EmployeeTime and propose a hold when a request would overdraw the account or collide with the roster.

    With Leave Conflict, Shift Coverage

  • Close terminations without a manual sweep

    Read EmpEmploymentTermination and PersonEmpTerminationInfo daily and propose the offboarding steps for IT and facilities.

    With Offboarding Sweep, Access Offboarding

Requirements

  • A SAP SuccessFactors instance and its data center API server, for example https://api17.sapsf.com/odata/v2/
  • A registered OAuth client and an identity provider that issues the SAML assertion
  • Permissions on Employee Central entities, for example Employee Central Effective Dated Entities > Job Information > Job Information Actions
  • An SAP ID to read the API specifications on SAP Business Accelerator Hub
Authentication
OAuth 2.0 with a client application registered in SAP SuccessFactors for an API key, exchanged together with a SAML assertion from your identity provider for an access token; OpenID Connect is also supported and HTTP Basic is deprecated.

Limits

  • OData v2 access limits: at most 1000 expressions in an in clause, 10 expanded navigation levels, 1000 records per upsert, and 180 requests per $batch
  • Rate limits are per policy and appear in RateLimit-Policy and RateLimit headers; in hard mode a breach returns 429 with Retry-After
  • Effective-dated entities like EmpJob need startDate and seqNumber handling; a day can hold several records
  • SOAP SFAPIs are deprecated except the CompoundEmployee API

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SAP SuccessFactors ↗

Questions and answers

Which entity holds an employee's manager and department?
EmpJob. Its HRIS element is jobInfo, its business keys are userId, startDate, and seqNumber, and it is effective-dated. It supports Query and Upsert. Filter on effectiveLatestChange to get the last record for each day in a range, and on lastModifiedDateTime for incremental loads.
How is API traffic limited?
By tenant-level and resource-level policies. Every response carries RateLimit-Policy with quota, window, and mode, and RateLimit with remaining count and reset time. Soft mode only reports; hard mode returns 429 with a Retry-After header. The OData v2 framework also caps $batch at 180 requests and upserts at 1000 records.
Is there a SOAP option?
Only the Compound Employee API, which extracts Employee Central data for replication. SAP has deprecated the other SOAP-based SFAPIs. New work uses OData v2, OData v4, or REST endpoints under /rest/.
Ask about SAP SuccessFactors

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SAP SuccessFactors through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy