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

​
Service Layer entity

​
observed: Walk by (UpdateDate, key) with ETag-conditioned updates

The following example matches configuration documents.

​
Configuration: documents

Case: sap-business-one/entity/observed/documents. Connection and resource configuration are declared by this exact case. Credential kind: sap_business_one. 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: masterData

Case: sap-business-one/entity/observed/masterData. Connection and resource configuration are declared by this exact case. Credential kind: sap_business_one. 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

sapBusinessOne.entity.observed({ entity, key, columns, update?, lag? }) reads one Service Layer entity set through /b1s/v2 (OData v4) under the binding’s baseUrl, such as https://b1.example.com:50000/b1s/v2/. The Service Layer compares dates at day granularity, so the walk orders by (UpdateDate, key) and asks for rows strictly after the last pair read: (UpdateDate gt 'D') or (UpdateDate eq 'D' and DocEntry gt 9). Each request sends $top and Prefer: odata.maxpagesize; the Service Layer’s own next link is a $skip offset and is never followed. A finished pass carries the last pair and the next one re-reads from one day (lag, 86400 seconds) before it. Re-read rows deduplicate by the entity’s ETag. Every row must carry @odata.etag (Service Layer 10.0 FP 2102 and later, for the entities SAP lists, such as Orders, Invoices, Items and BusinessPartners); a row without one is refused. update: { fields, governingRule } declares a single-attempt PATCH with If-Match: 204 confirms, a stale tag is refused (412), a lost answer stays unknown. String keys are quoted with doubled quotes in filters; an update addresses a string key without escaping, so it suits plain codes only. Limits: amounts arrive as JSON numbers, so columns are number and not exact. Deletions are not observed (Service Layer webhooks, which report them, are not consumed). The engine does not log in: bind a sap_business_one credential whose cookie holds an existing B1SESSION (which expires after the configured idle timeout, 30 minutes by default, and is replaced manually), or a bearer token where the installation authenticates through OIDC. No Service Layer 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.