SAP S/4HANA and SAP SuccessFactors integration

What moves between them

Employee and cost center records flow from SuccessFactors into S/4HANA. When an employee is hired or transferred in SuccessFactors, their record and cost center assignment propagate to S/4HANA as a business partner or cost center dimension. Cost center hierarchies are synchronized so allocations and GL postings in S/4HANA align with the organizational structure in SuccessFactors. Data flows on a pull-based schedule; employees marked as inactive in SuccessFactors are deactivated in the corresponding S/4HANA records rather than deleted.

How ml-connector handles it

ml-connector obtains an OAuth 2.0 bearer token from S/4HANA using the Communication Arrangement credentials, and generates a SAML Bearer Assertion signed with the SuccessFactors registered private key to obtain a 24-hour token on each call if one is not cached. It routes requests to the datacenter-specific SuccessFactors API hostname and the tenant-specific S/4HANA OData endpoint. Because SuccessFactors Employee Central and cost centers are separate from Core HR, ml-connector confirms the customer has the right licenses and reads from the FOCostCenter, FODepartment, PerPerson, and EmpJob APIs. The integration polls SuccessFactors with a delta filter on lastModifiedDateTime to retrieve only changed records since the last run, which avoids the default page size of 20 and retrieves up to 1000 records per call by setting $top=1000 explicitly. On S/4HANA, the integration upserts business partner records with the cost center reference and retries any request that returns a throttle response (HTTP 429 or 503) with exponential backoff. Because SuccessFactors does not support Idempotency-Key headers, the integration uses the employee ID as the deterministic key to ensure replaying a failed sync does not create duplicates.

A real-world example

A multinational manufacturer with plants in three regions runs SAP S/4HANA Cloud as its ERP and uses SuccessFactors Employee Central for global workforce management across 8,000 employees in 40 cost centers. Before the integration, the HR team exported employee lists and cost center assignments from SuccessFactors each month and emailed them to finance, who manually updated the cost center master and business partner dimensions in S/4HANA. This lag meant that AP posting and project allocation codes in S/4HANA were often stale, and month-end close required chasing down changed employee assignments to re-allocate GL lines. With SuccessFactors connected to S/4HANA, every hire, termination, and cost center transfer flows automatically to the ERP, and the finance team no longer spends days at close reconciling headcount between HR and the ledger.

What you can do

• •Sync employee records from SuccessFactors into S/4HANA as business partners or cost center members so your ERP headcount matches your HR record.
• •Propagate cost center changes and organizational structure from SuccessFactors to S/4HANA so GL postings and project allocations use the right cost center.
• •Authenticate SuccessFactors with SAML Bearer Assertion and S/4HANA with OAuth 2.0 Client Credentials, handling token refresh and expiry on both sides.
• •Poll SuccessFactors with delta sync filters to retrieve only changed employee and cost center records since the last run.
• •Retry throttle responses with exponential backoff and track every employee and cost center change in an audit trail for compliance.

Questions

Which direction does data move between SuccessFactors and S/4HANA?

Data flows from SuccessFactors into S/4HANA. Employee records, cost centers, job codes, and organizational structure sync from HR to the ERP so S/4HANA always reflects the current workforce and cost allocations. S/4HANA cost center and GL account data is not pushed back to SuccessFactors.

Does the integration use webhooks or pull-based polling?

The integration uses pull-based delta sync by default, querying SuccessFactors for employee records modified since the last run using a lastModifiedDateTime filter. This avoids the need to manually configure webhooks in the SuccessFactors Admin Center UI, which must be done by hand. If you do configure SuccessFactors lifecycle event webhooks, ml-connector can ingest those instead.

How does ml-connector handle SAML authentication on SuccessFactors?

ml-connector signs a SAML assertion with your registered RSA private key, POSTs it to the SuccessFactors OAuth endpoint, and receives a 24-hour bearer token. The token is cached and reused for subsequent calls. ml-connector also tracks token expiry and re-authenticates before the token expires to avoid mid-flow failures.