Skip to main content
This page records how composerID publishes into SAP Ariba: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. SAP Ariba is an enterprise source-to-pay and sourcing suite. Contingent services and SOW work are modelled through Sourcing Projects, Requisitions and Contract Workspaces rather than a single VMS object. composerID maps canonical intent onto those objects across Ariba’s REST, SOAP and cXML surfaces.
Category: Vendor Management & Sourcing. Coverage status: Specification mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Vendor documentation

SAP Business Accelerator Hub: Ariba REST APIs

Making REST API calls with OAuth token + application key

SAP Ariba SOAP Web Service APIs

SAP Ariba Developer Portal

API posture

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
SOW / contingent labour is not a first-class REST object; field-level schemas live in per-API WSDL/OpenAPI specs on the Business Accelerator Hub, several behind Hub login. App keys take ~12h to activate, and apps are promoted from test realm to production.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.