MCP for SAP
Use SAP metrics for reporting and planning
Actual-versus-plan variances, cost centres and open purchase orders: we make agreed SAP analyses accessible through targeted queries for your business team. In the pilot, we define sources, metrics, business rules and reference results. MCP provides the connection to your approved AI application.
The connection
We assess OData services through SAP Gateway and, where needed, RFC or BAPI as connection options. Available data and functions depend on your SAP version, configuration and approved interfaces. Your SAP team confirms suitable access and acceptable load limits.
If new SAP development is needed, we identify it as a separate scope. For the AI connection, we also document which results are transmitted to the AI application and model provider and which logs may contain them. You approve hosting, model destination and retention; a local MCP server alone does not guarantee local processing.
Verify SAP permissions in the connection
Existing SAP permissions are the starting point. However, a shared service user may have broader permissions than the requesting person. User mapping and permission checks for the interfaces actually used are therefore defined with your SAP team.
We test access to relevant authorisation objects, plants, company codes and clients using permitted and denied requests. The connection is approved only for the scope whose access controls have been demonstrated. Production operation requires separate permission acceptance.
Typical uses
- Controlling
- Variances against plan, contribution margins, development of individual cost centres over several periods, without building a new report for every variant.
- Purchasing
- Price development per supplier, open purchase orders, delivery reliability as a question rather than a report run.
- Sales
- Order situation, margins per customer and item, follow-up questions during the conversation rather than afterwards.
- Maintenance
- Notifications and orders in connection with equipment data — the bridge to the production side, which we also connect.
Limits we state up front
- No write access to SAP in the standard scope. Postings and document changes stay in SAP.
- No circumvention of the authorisation system through a collective user.
- No additional replication, indexing or caching without an approved purpose, permissions and retention rules.
- No commitments regarding modules whose interfaces we have not checked.
Frequently asked questions
Does this work with S/4HANA and with SAP ECC?
A connection may be possible with either. We work with your SAP team to establish which OData, RFC or BAPI functions are usable and what activation or development is needed. A commitment to your use case follows only after checking the specific interfaces.
How do you prevent someone from seeing figures they are not allowed to see?
We verify the mapping between the requesting person and the SAP permission context and test both permitted and denied access. This covers the authorisation objects, company codes and plants relevant to your workflow. A shared technical account is not evidence of correct permission mapping.
Can the AI post in SAP?
Not in the standard scope. We only deliver read-only servers. Write functions are technically possible, but require an approval chain, an allowlist of permitted transactions and complete logging, and that is a separate project with its own risk assessment.
How quickly does the system respond?
Response time depends on the SAP service, data volume, network connection and model. In the pilot, we measure representative queries and agree limits for data volume, runtime and system load. Larger analyses are constrained to stay within the agreed load limits.
Let’s check whether it holds up for your systems.
We first clarify your use case, data sources, permissions and acceptance criteria. The feasibility review documents prerequisites and limits before a pilot is agreed.
Discuss your use case