SAP OData

Let your app read and update the data in SAP: sales orders, materials, business partners.

Ask Claude to connect it

Included on every plan. An admin approves it once.

What your app can do with it

✓Work with live data from your system of record, not a copy
✓Works with SAP in the cloud, such as S/4HANA Cloud
✓Systems behind your company firewall can't be reached yet

For your IT admin

Setting it up

Done once, in your company's own account with SAP.

Create a communication user, or an OAuth client, restricted to the services the application needs.

Expose the OData service and note its full base URL, up to the service root.

Note the SAP client number, usually three digits such as 100.

Give it read-only authorisations unless the application genuinely writes back.

For developers

What your app receives

Reads and writes business data in SAP through an OData service: sales orders, materials, business partners, whatever the endpoint exposes. This is the connector that turns a hosted app into something a functional consultant can actually deliver, because an application that cannot see the system of record is a demo rather than a solution. OData is self describing, so the service metadata gives you the real entity sets and field names instead of leaving you to guess them. Phase one covers public endpoints, meaning S/4HANA Cloud, Sales Cloud and Service Cloud reached over ordinary HTTPS. Anything behind a firewall needs connectivity we do not offer yet, and this connector will not reach it.

SAP OData's own documentation →

SAP_ODATA_URLSAP_CLIENTSAP_USERSAP_PASSWORD