Skip to main content
Use the @bijection/connectors/sap entrypoint to declare SAP RFC/BAPI and transactional CDC 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.

RFC function

rfc: RFC/BAPI

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: sap/function/rfc/standard. Connection and resource configuration are declared by this exact case. Credential kind: http. 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.

SAP change stream

cdc: ABAP CDC

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: sap/stream/cdc/standard. Connection and resource configuration are declared by this exact case. Credential kind: http. 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

Use bijection source sap capture to capture selected JCo function interfaces and seeded ABAP CDC stream schemas. A sap.contract project generates typed bindings under _generated/sap. Private gateway endpoint, bearer credentials and CDC epoch belong to the normal HTTP connection binding. Function resources use exact captured signatures, explicit governing rules and single-attempt delivery. The customer gateway uses SAP JCo and keeps a BAPI and its explicit commit/rollback on one stateful session. RETURN selectors and BAPI mode are operator declarations. A lost reply remains unknown; no resend, durable SAP receipt or changed business state is inferred. CDC resources require the versioned Bijection ABAP add-on, complete committed seed and customer-installed business update hooks. The stream retains full after-images and deletions from sequence zero. Update-task failure rolls back its log records and sequence. Schema drift, a changed epoch or missing history refuses progress. The source does not claim atomic publication of an entire multi-row SAP transaction. The gateway and installable ABAP source live with Bijection’s SAP integration. SAP JCo binaries are supplied by the customer, and are not redistributed. These bindings neither install SAP objects nor establish live SAP qualification.

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.