Skip to main content
Use the @bijection/connectors/sap-bydesign entrypoint to declare SAP Business ByDesign 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.

Custom OData service collection

observed: Anchored walk by LastChangeDateTime

The following example matches configuration standard.

Configuration: standard

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

sapByDesign.collection.observed({ service, collection, key?, modified?, columns, lag? }) reads one collection of a custom OData service (https://my654321.sapbydesign.com/sap/byd/odata/cust/v1/<service>/<collection>) of the tenant named by the binding’s tenant setup. The service must expose the business object’s change timestamp (default LastChangeDateTime, mapped from its administrative data) and an ObjectID (or named) key. The walk is the anchored walk documented for Cloud for Customer: rows changed at or after the last instant read, ordered by it, skipping by $skip the rows already read at that instant. The published version is the change timestamp; ByDesign’s ETag is a per-service configuration and is not relied on, so no command is declared. Deletions are not observed, and the analytics data sources (“no delta load is supported”) are not read. Bind a sap_bydesign credential (basic for a communication user). No ByDesign tenant has been reached.

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.