Skip to main content
Use the @bijection/connectors/successfactors entrypoint to declare SAP SuccessFactors resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
OData v2 entity

​
observed: Snapshot-paged pass by last modification with a carried basis

The following example matches configuration standard.

​
Configuration: standard

Case: successfactors/entity/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: successfactors. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: decimals

Case: successfactors/entity/observed/decimals. Connection and resource configuration are declared by this exact case. Credential kind: successfactors. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

successfactors.entity.observed({ entity, key, columns, modified?, lag? }) reads one OData v2 entity set (User, PerPerson, EmpJob, an MDF object, …) under the binding’s baseUrl, the API server’s OData root such as https://api4.successfactors.com/odata/v2/. Each pass asks for the rows whose modification property (default lastModifiedDateTime, Edm.DateTimeOffset; lastModifiedOn is Edm.DateTime) is at or after a bound, with paging=snapshot: SAP keeps the business keys of the whole filtered set at the first request and serves every later page from that list through __next, which the engine follows as the provider’s own continuation. An answer stating X-SF-Paging: offset is SAP falling back to $skip paging, which SAP documents as unreliable for “last modified since” reads; it is refused. The first page’s HTTP Date is the pass’s basis. A finished pass carries the bound lag seconds (default 300) before it (sync.carry), so a row modified while the pass paged is read again by the next pass; re-read rows deduplicate by their modification value, the published opaque version. A failed pass carries nothing. Values: Edm.Decimal and Edm.Int64 arrive as JSON text and are declared decimal and int64, checked on the wire as exact decimal text. Dates stay SAP’s /Date(…)/ text. Each column is its type or null. Not observed or not declared:
  • Deletions. SuccessFactors OData v2 lists no deleted rows; a deleted row stays published. Effective-dated entities return the current slice unless the entity is queried with fromDate/toDate, which this recipe does not send.
  • Entities whose key has several properties, and expanded navigations.
  • Commands: OData v2 entities document no If-Match.
Bind a successfactors credential whose allowed_resource_origins names the API server: basic (user@companyId; SAP retires API Basic authentication in 2027) or a bearer token obtained outside Bijection. SAP’s OAuth SAML-bearer and IAS OIDC exchanges are not performed by the engine. SAP blocks a user for 30 minutes after repeated first-page-only snapshot requests; a pass that fails on its first page counts toward that limit. No SuccessFactors instance has been reached; the registered cases are synthetic.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.