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
Fetch a CSRF token by sending a GET request to the API_SALES_ORDER_SRV service root with the header 'x-csrf-token: fetch'; capture the token returned in the response header 'x-csrf-token'.
Obtain an OAuth 2.0 bearer token from the BTP service key for the communication scenario that exposes the Sales Order API (SAP_COM_0109 or equivalent).
POST to /sap/opu/odata/sap/API_SALES_ORDER_SRV/A_SalesOrder with a JSON body containing at minimum: SalesOrderType, SalesOrganization, DistributionChannel, Division, SoldToParty, and a deep-insert 'to_Item' array with each item's Material, RequestedQuantity, and SalesUnit.
Check the HTTP 201 response body for the created SalesOrder number; handle any error messages surfaced in the 'error.innererror.errordetails' array.
Known gotchas
Deep insert of items and schedule lines in a single POST may be rejected if the sales order type does not allow automatic schedule line creation; create items separately if needed.
The SalesOrganization, DistributionChannel, and Division combination must form a valid sales area in the system configuration or the request returns a business validation error.
CSRF tokens are single-use and session-scoped; re-fetch before each modifying request in long-running agent loops.
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?