SAP S/4HANA (OData)
Read SAP S/4HANA on-premise and Private Cloud through its OData services: find services in SAP's catalog, read their fields with SAP's labels, query released APIs and analytical views for finance, sales and inventory figures. Basic auth or OAuth, SAP client aware.
7 天免费 · 无需信用卡 · EU 托管
问 SAP 任何事
通过 AnythingMCP 对 SAP S/4HANA (OData) 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 SAPClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 SAP S/4HANA (OData)。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 SAP S/4HANA (OData)
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
What this connects to: SAP S/4HANA on-premise or Private Cloud (also ECC and BW with SAP Gateway) through its OData services, the interface SAP publishes for integrations. SAP checks the technical user's authorizations on every call.
Start with s4_guide, then s4_list_services to find a service, s4_describe_service / s4_describe_entity to read its fields with their SAP labels, and s4_query to read rows. The ready tools cover the most common released APIs.
Setup (SAP Basis, one-off)
- Create a technical user of type System (not Dialog) in the client you want to read, with a productive password.
- Give it a role with
S_SERVICEfor the OData services the agent may use and read-only business authorizations (display only, activity 03). To let the agent browse the catalog, also allow/IWFND/CATALOGSERVICE(V2) and the V4 service catalog. - Make sure the services are active (
/IWFND/MAINT_SERVICEfor V2,/IWFND/V4_ADMINfor V4). - Fill in:
SAP_ODATA_BASE_URL, the Gateway host with the HTTPS port, e.g.https://s4.example.com:44300(no path);SAP_CLIENT, the three-digit client;SAP_LANGUAGE, e.g.EN;SAP_ODATA_USERandSAP_ODATA_PASSWORD.
Network: the Gateway port is usually internal. Self-host AnythingMCP inside the network (or connect it through a VPN) and add the host to SSRF_ALLOWED_HOSTS.
Restrict services: list the service paths the agent may call under the connector's OData settings (Allowed services, * as wildcard). The authorizations of the SAP user remain the real boundary.
SAP API policy: SAP's API policy expects third-party integrations to use published APIs (the API_* services) or services you built yourself; prefer those over internal UI services.