By Vaidya Aiyer, VP of Enterprise AI · Published August 25, 2026
Previously in this series: The SAP Resource Problem Nobody Has Time to Fix →
Every SAP customer is dealing with the same resource problem right now. Whether you're fully on S/4HANA, mid-migration, or still running ECC, there aren't enough SAP people to go around, and the 2027 migration deadline is only making it worse. Meanwhile, the business requests — reports, small changes, bigger asks — don't stop coming.
Two recent conversations with customers show just how this plays out.
One customer is just starting their S/4 journey. Three ECC instances, running globally. A four-year migration plan ahead of them.
Their best people need to be heads-down on S/4. But the business hasn't slowed down asking for reports and changes on those same ECC instances. They can't tell the business to stop. So the same stretched team ends up doing both, and something always slips.
Another customer has a different shape of the same problem. They've got offshore resources ready to build. What they don't have is enough functional people to turn a business ask into something a developer can actually build. That translation step — business requirement to spec — is where everything backs up.
Most business users already have Microsoft Copilot. Most of them have never once pointed it at SAP, because it can't reach SAP data. Not out of the box.
That's the gap SELECCIÓN MCP was built to close. It connects Copilot to live SAP data. Business users ask a plain-English question, get a real answer, pulled straight from the system. No ticket. No queue. It runs inside the infrastructure already in place — no upgrade, no disruption to what's running today. Governed and secure the whole way through.
Most approaches to connecting AI assistants to SAP need a separate OData API for nearly every operation on every business object. One API to read a purchase order. A different one to create it. Another to update it. Another to cancel it. Multiply that across every object in Finance, Sales and Distribution, Materials Management, Production Planning, and every other module, then multiply it again across ECC and S/4HANA. SAP alone exposes literally thousands of OData APIs this way.
And that's before accounting for what most enterprises actually run. Most SAP installations aren't vanilla — they're customized, with custom objects and custom transactions layered in over years. Standard APIs don't cover those. So customers end up building and maintaining their own custom APIs just to reach the parts of SAP that are unique to them. Someone has to build against all of it, document it, secure it, and maintain it forever. Every SAP upgrade, every patch, every module change becomes a maintenance event across some slice of that pile.
SELECCIÓN MCP works differently. One single connector handles plain-English prompts in Microsoft Copilot across FI, SD, MM, PP, and the rest of the SAP modules — on ECC or S/4HANA, standard or custom objects — without a different API for each one. Ask a Finance question, ask a Sales question, ask a Production question: same connection, same governance, same maintenance footprint. Just one.
That eliminates more than the initial integration work. It eliminates the ongoing maintenance tax that comes with every API stood up, including the custom ones built for custom objects. Fewer things to patch. Fewer things to break during a SAP update. Fewer places for something to go wrong quietly. IT teams that are already stretched thin don't need one more sprawling integration layer to babysit, standard or custom.
For the migration customer, this doesn't touch their S/4 timeline at all. It just means the ECC requests that used to pull their best people off migration work can now get answered directly by the business, across whichever module the question touches, without a separate integration for each one. Their team stays focused on getting to S/4. If anything, this clears the noise that was slowing the migration down.
For the second customer, the simple asks — the reports, the quick lookups — don't need to go through the functional bottleneck anymore, no matter which module they touch. That frees up the scarce functional people to spend their time on the complex specs that actually need them.
Neither of these is about avoiding an upgrade or working around SAP. It's about getting the easy stuff off the plate of the people needed for the hard stuff, without adding a maintenance burden of its own.
Ask a real question in plain English, get a live answer straight from SAP data, no ticket required. See a live demo to find out what a 48-hour pilot could look like in your own environment.