{"id":165643,"date":"2026-08-13T12:36:58","date_gmt":"2026-08-13T10:36:58","guid":{"rendered":"https:\/\/e3mag.com\/?p=165643"},"modified":"2026-08-13T13:52:14","modified_gmt":"2026-08-13T11:52:14","slug":"sap-erp-exit-with-model-context-protocol","status":"publish","type":"post","link":"https:\/\/e3mag.com\/en\/sap-erp-exit-mit-model-context-protocol\/","title":{"rendered":"SAP ERP Exit with the Model Context Protocol"},"content":{"rendered":"
Media Discontinuities and APIs as Showstoppers<\/h2>\n\n\n\n
In the days before SAP BTP, ABAP developers (Business Technology Platform), had to program custom, isolated interfaces for every single AI application and every data source, which inevitably led to an uncontrollable explosion of interfaces\u2014the infamous NxM integration problem with spiraling complexity, inconsistent security policies, and skyrocketing maintenance costs.<\/p>\n\n\n\n
To this end, MCP has established a radically open, structural solution that is rightly celebrated in the global tech community as the \u201eUSB-C for AI apps.\u201c It standardizes the integration and tool layer and provides a unified definition of how language model-based applications (LLM clients) can securely, transparently, and dynamically access external systems, data sources, and computing cores\u2014without having to program a separate integration for every third-party system.<\/p>\n\n\n\n
<\/div>\n\n\n\n
New SAP ERP Architecture by MCP<\/h2>\n\n\n\n
For an existing SAP customer, an MCP server fundamentally pushes the boundaries of system architecture by acting as a standardized translator and cognitive interface in front of the ERP backend.<\/p>\n\n\n\n
Instead of hard-coding complex interfaces into the logic of AI agents, the ERP system makes its capabilities and data available in a controlled manner via an MCP server as predefined tools and consolidated interfaces. The higher-level AI application acts as an MCP host, recognizes the tools exposed via the server\u2014such as retrieving a purchase order status, querying supplier ratings, or checking material inventory\u2014and calls them up autonomously and contextually as needed for specific processes.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Roland Berger Consulting: MCP Helps AI<\/h2>\n\n\n\n
The invaluable advantage of this approach is that the AI does not need to learn from a private corporate database through expensive, risky, and privacy-sensitive model training, but instead is supplied with precise, filtered live operational data in real time via the MCP server.<\/p>\n\n\n\n
From the perspective of system security and data protection, this is an invaluable milestone: As an analysis by Roland Berger shows, MCP enables autonomous AI agents to request only the specific data that is absolutely necessary for the current task, which drastically minimizes the attack surface and makes compliance with strict governance requirements auditable and scalable in the first place. In addition, token consumption drops dramatically, since there is no need to funnel unnecessary mountains of data through the language models\u2019 context windows.<\/p>\n\n\n\n
<\/div>\n\n\n\n
MCP Openness vs. SAP Licensing Law<\/h2>\n\n\n\n
However, this open architecture conflicts with the economic interests of the Walldorf-based software monopoly SAP, a fact that is painfully evident in the controversial new SAP API Policy issued in April 2026. Under the official pretext of protecting system stability and cybersecurity from uncontrolled access, SAP has significantly tightened the screws on third-party providers and existing customers.<\/p>\n\n\n\n
In its notorious Section 2.2.2, the guideline explicitly prohibits any use of APIs to interact with autonomous or generative AI systems that independently plan, select, or execute sequences of API calls, unless this is done via a path approved and certified by SAP. In addition, systematic bulk data extractions to external data warehouses or data lakes such as Microsoft Fabric are prohibited.<\/p>\n\n\n\n
Particularly controversial is the classification of the popular ODP-RFC interface for data integration as \u201eprohibited use\u201c for third-party applications, effective as of February 2024. This poses an existential risk for existing SAP customers: SAP is attempting to establish itself as the exclusive, toll-charging gatekeeper for the company\u2019s own data intelligence. Anyone who wants to enhance their S\/4 data with superior, third-party algorithms in the dawning age of AI will be systematically blocked and forced to license the expensive and proprietary ecosystem of the Business Technology Platform (SAP BTP) and the Business Data Cloud (SAP BDC).<\/p>\n\n\n\n\n\t\t\t
![\"\"](\"https:\/\/e3mag.com\/wp-content\/uploads\/2026\/08\/e3nl26kw33_grafik-1200x670.png\")