Skip to main content
This page records how composerID publishes into SAP SuccessFactors: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. SAP SuccessFactors is the HRIS/HCM system of record - the anchor destination for the permanent-hiring channel. composerID publishes the decision as a Position (Employee Central) and, where Recruiting is live, a Job Requisition, stamps the Intent ID on a custom field, and reconciles the eventual hire (EmpJob) back onto the intent timeline.
Category: HRIS / HCM. Coverage status: Specification mapped. Vendor documentation: public developer portal.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

SAP Business Accelerator Hub - SuccessFactors

OData v2 - Authentication using OAuth 2.0

SuccessFactors Platform docs (API guides)

KBA 3462403 - OData OAuth 2.0 walkthrough

​
API posture

​
Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
SuccessFactors is heavily tenant-configured: MDF objects, picklists and requisition templates differ per tenant, so mapping needs each tenant’s schema. API servers are per data center; the OAuth client is registered per instance and the API user must hold matching Role-Based Permissions. Recruiting (JobRequisition) is a separately licensed module - confirm before planning the requisition step.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.