Most people who need something from SAP S/4HANA do not use SAP every day. A controller wants the open purchase orders for a supplier, a sales manager wants a customer’s order history, an AP lead wants to know why an invoice is blocked. The answer is a transaction code and a filter away, but that means a license, training, or a request to the one person who knows where to look.
Now those same people use Claude or ChatGPT all day. The obvious move is to let the assistant ask SAP. The obvious worry is what else it could do once it is in.
What has to be true before IT says yes
- The assistant reaches only the SAP data it needs, ideally read only.
- No SAP password or token is pasted into a prompt or a config file.
- IT can see who is using it, and every call is recorded.
- The same setup works for Claude, ChatGPT, Cursor and in-house agents.
How engini makes it governable
engini connects to SAP S/4HANA through SAP’s standard OData services, one service per connection, with fields loaded from each service’s metadata. You create an engini MCP server that exposes only the connections and tools you choose, for example get operations on the purchase order and sales order services. People add that server to Claude, ChatGPT or Cursor and sign in through engini over OAuth, with no key to copy.
engini shows who is using each MCP server, and records every run under the user who triggered it. For in-house agents built on the SDK, CLI or REST API, a toolset does the same scoping, enforced on the server.
SAP S/4HANA