SELECCIÓN MCP+ is the connectivity layer that lets AI agents work with your live SAP data, natively. An ABAP execution engine installs inside your SAP system, so there are no new APIs to build, no middleware to run and no upgrade to schedule. Every SAP request runs under the asking user's own SAP authorizations. MCP+ also reaches the installed-base, in-house, custom and database-based systems around SAP.
This is true wherever you are on your SAP roadmap: today, mid-migration or post-Clean Core.
SAP ECC and other installed-base systems were built before agentic AI existed. Every AI model needs a bridge to reach live transactional data.
Traditional API layers mean new integration projects, security reviews and months before an AI agent can safely touch production.
Business users wait on IT tickets for answers that already live inside the ERP they use every day.
Two components, one governed connection to your live SAP data.
Installs directly inside your SAP system and runs requests as native SAP logic, across standard and custom objects. The ABAP add-on holds SAP clean core certification.
Manages AI agent requests and connects them to the engine. Your IT hosts and runs it on Azure, Google Cloud, AWS or SAP BAIP, ideally next to SAP. SELECCIÓN supports the software.
Each SAP system gets its own connector, so ECC and S/4HANA in parallel, or several regional systems, is a normal case.
MCP+ is built for SAP first. It also connects AI agents to the systems that sit around SAP, so one connection layer reaches more of your landscape.
Older systems built before agentic AI existed become reachable by AI agents, wherever you are on your roadmap.
Applications your own teams built can be connected too, not just packaged software.
Systems that live in a database can be connected as well, so agents can work with the data behind them.
An AI agent, or Microsoft Copilot on a user's behalf, sends a plain-language request.
The request becomes SAP-native logic, executed in your own system under that user's roles.
The user gets a structured answer, and the action is recorded in the audit trail.
SAP's own access control stays the single point of enforcement.
Every request runs under the asking user's own SAP roles. Nothing bypasses your authorization model.
Every query and action is logged, timestamped and traceable to a specific user and agent.
MCP+ operates inside your existing SAP authorizations. It does not change them.
The execution engine runs next to your SAP ERP, inside your own instance, with SSO enabled.
The engine keeps track of your custom objects, not just the standard ones, so answers fit your landscape.
Switch it off or restrict it at the MCP server at any time. Users can always go to SAP directly.
An AI agent with real authority needs an identity, a scope and a lifecycle. See how we govern it with Digital Employee →
Give business users governed, self-serve access to live SAP data through Microsoft Copilot. See Copilot for SAP →
Usage data from the execution layer shows which custom transactions, BAPIs and Z-programs the business really uses, so you decide what to keep, replatform or retire with evidence.
The same engine connects SELECCIÓN AAS to ECC and S/4HANA, where agents resolve routine SAP tickets. See SAP Support & AMS →
Straight answers about SELECCIÓN MCP+.