Skip to main content
Use the @bijection/connectors/sap-c4c entrypoint to declare SAP Cloud for Customer 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.

​
c4codataapi collection

​
observed: Anchored walk by EntityLastChangedOn with ETag-conditioned updates

The following example matches configuration standard.

​
Configuration: standard

Case: sap-c4c/collection/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: sap_c4c. 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: updates

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

​
Provider guidance

sapC4c.collection.observed({ collection, key?, columns, update?, lag? }) reads one c4codataapi collection (OData v2) of the tenant named by the binding’s tenant setup (my123456, rendered as https://my123456.crm.ondemand.com/sap/c4c/odata/v1/c4codataapi/). The walk filters EntityLastChangedOn (available since release 1911). C4C’s or works only within one property, so a (time, key) keyset cannot be written; each page instead asks for rows changed at or after the last instant read, ordered by it, and $skips the rows already read at exactly that instant. Only rows sharing one millisecond are ever skipped by count, so a change inside such a group while the walk pages is the one way a row can be stepped over. A finished pass carries the last instant and re-reads from lag seconds (default 300) before it. Each entity’s ETag (__metadata.etag, the change time at 100 ns) is its published version. update: { fields, governingRule } declares a single-attempt PATCH of those columns with If-Match set to the record’s ETag: a stale tag is refused with 412, 204 confirms, and a lost answer stays unknown. Writes send no CSRF token, which C4C does not require of technical-user or OAuth callers. Deletions are not observed: the OData API lists none (C4C event notifications are not consumed), so a deleted row stays published. Decimal amounts are complex types in C4C; declare their scalar components as decimal only where the service sends text. Bind a sap_c4c credential: basic for a communication-arrangement user, or a bearer token from a SAML-bearer exchange performed outside Bijection. No C4C tenant 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.