sap_get_services and sap_get_service_metadata let an agent map an SAP system before it writes a single query, which is the part that otherwise needs someone in the Gateway console. Writes run through the same session and the CSRF token is managed for you, so what the SAP user is authorized to do is the real boundary.
A server that talks to an SAP system's OData services: it finds which services a system exposes, reads their entity sets, and creates, updates or deletes records in them.
- The OData services a system exposes, discovered rather than typed in by hand
- The metadata for any one service, so its entity sets are readable before you query them
- Entity-set queries with field selection, filters, ordering, paging and expanded navigation properties
- A single record fetched by its key values
- Create, update and delete on entities, with the CSRF token that SAP demands for writes handled for you
- OData function imports called by name
- Connection status and disconnect, so a dead session looks different from a bad query
An SAP user with authorization for the OData services you want, on a system where SAP Gateway and those services are already activated. Everything goes over HTTP and REST, so nothing SAP-specific has to be installed locally. Setup is a local build: install the dependencies, compile, then point your client at the built entry point.