Register the OData v4 service in the SAP Gateway server via transaction /IWFND/V4_ADMIN and activate it; verify accessibility via the service document URL /sap/opu/odata4/<namespace>/<service>/<binding>/
Test $filter expressions against the entity set: string filters use single quotes and the 'eq', 'ne', 'gt', 'lt', 'contains', 'startswith' functions; date literals use the format YYYY-MM-DDThh:mm:ssZ
Use $expand with navigation properties to retrieve related entities in a single request; in OData v4 $expand supports nested $select, $filter, and $orderby within the expanded navigation
For deep insert (creating a parent entity and its related entities in one POST), include the navigation property data as a nested object in the POST body under the navigation property name
Validate that the ABAP backend implements the necessary CREATE_DEEP_ENTITY method in the data provider class for deep insert; absence of this implementation returns a 405 Method Not Allowed
Known gotchas
OData v4 on SAP Gateway differs from the cloud-native SAP Business Accelerator Hub services; on-premise v4 implementations may lack features present in the cloud APIs (e.g. draft handling, cross-join)
Deep insert and deep update are not the same: deep insert creates the parent and child in one request, but a PATCH on the parent does not automatically upsert children — use a $batch or separate child entity requests for updates
The X-CSRF-Token fetch-and-use pattern required for OData v2 also applies to OData v4 on SAP Gateway for all modifying operations
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp