AI assistants can read from and write to SAP ECC 6 today, under each user's own SAP authorizations, with no S/4HANA migration, no SAP BTP and no middleware. CGR MCP Server for SAP does it through a native ABAP add-on installed in the ECC system.
Why most ECC customers think they have to wait
The common assumption is that AI in SAP comes after the move to S/4HANA. It is a reasonable assumption. SAP's own assistant and agent tooling is aimed mainly at S/4HANA and built on SAP BTP, and most of what is written about AI in SAP describes that stack.
For a company on ECC 6, that reads as a queue: migrate first, then get a platform, then get AI. For many, the migration is still years away.
Meanwhile the business has already rolled out an AI assistant, and the first thing people ask it is something only SAP knows.
What ECC 6 can already do
ECC 6 has everything it needs to work with an AI assistant. It can serve data over HTTPS, enforce authorizations on every call and run the same BAPIs a user triggers from a transaction. What it lacks is a governed way to offer those to an assistant.
CGR SAP Connector provides that. It is a native ABAP add-on in its own namespace, installed through SAINT, and it runs inside the ECC system. An administrator approves an SAP object and it becomes available to the assistant:
- Tables, views and classic CDS views
- ALV reports with their saved variants, and SAP queries
- Standard BAPIs
- Custom function modules, including ones that are not RFC-enabled
Nothing is rewritten or wrapped. The report controlling built ten years ago is used as it is, with the same logic and the same numbers.
What is and is not needed
| Needed | Not needed |
|---|---|
| Any SAP ECC 6 release | An S/4HANA migration |
| CGR SAP Connector, installed by your Basis team | SAP BTP |
| A whitelist of approved objects per role | Integration Suite or other middleware |
| An MCP-capable AI assistant your company licenses | OData services built per object |
| Single sign-on mapped to named SAP users | Changes to existing reports or function modules |
See how CGR compares with BTP, Integration Suite and open-source MCP servers.
The order-to-invoice session on our home page, from sales order to posted invoice, ran on an ECC 6 system.
Does this change the migration decision?
No. A move to S/4HANA is decided by maintenance dates, business requirements, the data model and the roadmap. An AI assistant on ECC touches none of those, and nobody should choose whether to migrate based on how users reach the system.
What it changes is the waiting. A company on ECC 6 can give its people AI in SAP now, on the release it runs, and make the migration decision on its own timeline for its own reasons.
What moves with you to S/4HANA
The same add-on runs on ECC 6 and on S/4HANA, on-premise, in private cloud or with RISE. What a company sets up on ECC carries over:
- The roles and the whitelist of approved objects
- The users' habits and the questions they have learned to ask
- Custom function modules written for the assistant
- The audit trail and the security review already completed
A business that has worked with AI against its SAP data for a year arrives at S/4HANA knowing what it needs from it.
What it does not replace
It does not replace the migration, and it does not turn ECC into S/4HANA. The assistant works through tables, reports, BAPIs and function modules; it does not drive SAP screens. Processes that exist only as dialog transactions need a function module before the assistant can run them.
Security on ECC is SAP's own security
The assistant can do only what the person asking is already allowed to do in SAP. Each person maps to one named SAP user, every call must be on IT's whitelist and inside that user's authorizations, writes need an explicit commit, and every call is logged in SAP. The security page lists all eight controls.
On SAP's API Policy: the connector is in-system ABAP, installed in the customer's own on-premise or private-cloud system and running under the customer's own authorization objects. The security page explains how that sits against the policy. Customers should confirm their own use cases against their agreements with SAP.
How to start
A 30-minute live demo on an ECC 6 system shows an assistant answering, acting, recovering from an SAP error and being refused. A four-week pilot follows in your own system: 5 to 10 named users, read-only, for $8,000 fixed, credited in full against the licence.