For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
The SAP Ariba connector is part of the Integration Hub. It is inbound only: SAP publishes no write endpoint for supplier master data, so Coverbase reads from Ariba and does not write back.
What it does
Supplier master records also appear on Configuration → Vendor Master Data, with the steward queue and the sync log.
Authentication
Ariba issues a token fromhttps://api.ariba.com/v2/oauth/token with client credentials in HTTP Basic, and every data call to https://openapi.ariba.com also carries your application’s API key and your realm.
- In the SAP Ariba developer portal, create an application with access to the Supplier Data API with Pagination and Operational Reporting for Sourcing.
- Note the OAuth client ID and secret, the application key, and your realm name.
- If you use a sourcing reporting view other than
SourcingProjectSourcingSystemView, note its name.
Set up in Coverbase
- Open Configuration → External Integrations and click SAP Ariba.
- On Authentication, enter the Client ID, Client secret, Application key and Realm, and the Sourcing reporting view if you use your own.
- Turn on Open an intake request for each new requisition to open intake requests from sourcing events.
- Set Sync Interval (Minutes), click Save, then Test connection.
- Click Sync now and read the Sync Log. Work the Steward Queue for suppliers that did not match.
Onboarding checklist
- An Ariba test realm to connect first.
- An application with both APIs, and its client ID, secret and application key.
- Tax IDs or D-U-N-S numbers on your Ariba suppliers, so they link without a steward.
- A steward to work the steward queue.
Related
Integration Hub guide
The sync log and the steward queue.
Coupa
The two-way procure-to-pay connector.
Front Door triage
Where a sourcing event is reviewed.
Workday Strategic Sourcing
Another source of new suppliers.