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

​
Operational reporting view

​
windowed: Synchronous view API in 30-day update windows

The following example matches configuration standard.

​
Configuration: standard

Case: sap-ariba/view/windowed/standard. Connection and resource configuration are declared by this exact case. Credential kind: sap_ariba. 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.

​
jobs: Asynchronous reporting jobs in 30-day update windows

The following example matches configuration standard.

​
Configuration: standard

Case: sap-ariba/view/jobs/standard. Connection and resource configuration are declared by this exact case. Credential kind: sap_ariba. 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

sapAriba.view.windowed({ viewTemplateName, key, updated, columns, since, lag? }) reads one view of the Operational Reporting API for Procurement (v2) through its synchronous view endpoint, GET views/<viewTemplateName>?realm=…&filters=…, under the binding’s baseUrl (the API’s runtime URL from the developer portal) and realm setup. Ariba refuses filters spanning more than 31 days and pages at most 40 records, so each pass walks consecutive 30-day windows of updatedDateFrom/updatedDateTo from where the last pass ended (the first from since), each to the end of its stated PageToken, sent back as pageToken. The first answer’s Date is the pass’s basis; the pass ends with the window that reaches it and the next begins lag seconds (default 300) before it. Window edges are re-read; records deduplicate by the updated field, their version. Assumptions not established from SAP’s documentation: the records and token fields are named Records and PageToken (SAP names neither; these are the names integrators report), and a window ending after the current time is admitted. Rate limits are low (SAP states them per API on the portal); 429 is a transient failure. sapAriba.view.jobs({ viewTemplateName, key, updated, columns, since, lag?, every? }) reads the same view through the asynchronous job API. Each pass posts one job, POST jobs?realm=… with viewTemplateName and the updatedDateFrom / updatedDateTo filters of a 30-day window from where the last pass ended. It polls GET jobs/<jobId> every minute while the body’s status is pending or processing; completed and completedZeroRecords are ready, and errorMaxReached, errorInternal, errorInvalidDateRange or a 404 end the pass with a typed gap. Each file the ready answer lists is read at GET jobs/<jobId>/files/<fileId>: a ZIP holding one JSON file of up to 1,000 records, published 128 at a time. A stated pageToken is posted with the same filters (POST jobs?pageToken=…) until a page states none. The kick-off answer’s Date bounds the window: the next pass begins at the window’s end, or lag seconds before that date once the window reaches it. Passes default to every six hours because job submission is limited to a few requests an hour and forty a day per realm, shared by every view. Assumptions not established from SAP’s documentation for the job API: the submission answers 200 with jobId, and the zipped JSON keeps its records in Records. Files expire after 48 hours. Deletions are not observed. Bind a sap_ariba credential: oauth_client_credentials against the region’s /v2/oauth/token, with the application key in resource_headers as apiKey. No Ariba realm 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.