Read business partners via SAP S/4HANA Cloud OData API
domain: SAP S/4HANA Cloud OData · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth 2.0 client credentials token from the SAP BTP subaccount service instance bound to the S/4HANA Cloud tenant; the token endpoint is listed in the service key under 'uaa.url'.
Set the Authorization header to 'Bearer YOUR_TOKEN' and Content-Type to 'application/json'; also set the Accept header to 'application/json'.
Send a GET request to the API_BUSINESS_PARTNER OData service endpoint, e.g. /sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartner, optionally appending $filter, $select, and $top query parameters.
Parse the JSON response body; business partner records are in the 'd.results' array (OData v2) or 'value' array (OData v4 style), with fields such as BusinessPartner, BusinessPartnerFullName, and SearchTerm1.
For paged results follow the '@odata.nextLink' or '__next' property in the response to retrieve subsequent pages until no next link is present.
Known gotchas
The API_BUSINESS_PARTNER service must be explicitly enabled in the Communication Arrangements in the S/4HANA Cloud admin cockpit; calls will return 403 if the arrangement is missing.
OData $expand for associated entities (e.g., A_BusinessPartnerAddress) can significantly increase response time; fetch only what is needed using $select.
CSRF token handling is required for write operations but not for GET reads; however some tenants enforce it on all requests, so include a fetch of the CSRF token if you encounter 403 on safe methods.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?