SAP ECC
SAP ECC for AI agents and migration: call BAPIs, RFCs and IDocs today, and move ECC data to S/4HANA or any ERP before maintenance ends in 2027.
Book a demo
SAP ECC: agents today, migration on your schedule.
SAP ends mainstream maintenance for ECC 6.0 at the end of 2027. Until you move, and while you move, engini lets your AI agents and workflows work in SAP ECC, the SAP ERP that still runs much of the world's finance and supply chain: read customers, materials, stock and open items, create sales and purchase orders, post goods movements and accounting documents, call any BAPI or RFC function module, and send and receive IDocs. ECC stays where it is, and the On-Prem Agent connects it out to engini with no inbound ports. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
Move off SAP ECC on your schedule. To S/4HANA or the ERP you choose, with every record accounted for.
SAP ends mainstream maintenance for ECC 6.0 on December 31, 2027, with optional extended maintenance to 2030, and systems on older enhancement packages lost it at the end of 2025. Many companies move to S/4HANA; others choose another ERP. engini connects to SAP ECC where it runs today and to the ERP you are moving to, so you can load the new system, run both side by side and switch when the numbers match. We help you with the move, working with your team or your implementation partner.
Connect SAP ECC as it is
The On-Prem Agent reaches ECC over RFC, BAPIs and IDocs inside your network, with no inbound ports and nothing installed on the ERP.
Map and check
An AI agent proposes how ECC customers, vendors, materials, open items, orders and balances map to the new ERP and lists the records that would not load: missing fields, closed accounts, duplicates. Your team corrects the mapping before anything is written.
Load in batches
Master data, open receivables and payables, balances and the history you choose move in batches. Every record is in History, so nothing is lost or loaded twice, and failed rows are retried.
Run side by side, then switch
During the parallel run, new transactions in SAP ECC sync to the new ERP on a schedule, so both sets of books match until the day you switch. Afterwards, agents can still answer questions from the SAP ECC history.
Source: SAP maintenance strategy for SAP ERP 6.0: mainstream maintenance to December 31, 2027 for enhancement packages 6 to 8, optional extended maintenance to December 31, 2030.
Moving off SAP ECC? We help you do it.
Tell us what you run today and where you are moving. We help you plan the move, map and check the data, load it and run both systems side by side until you switch, working with your team or your implementation partner.
What your agent can do in SAP ECC. Every tool is one you allow or leave out.
The SAP ECC tools in engini, grouped by what they change. In an ERP a write is a financial event, so write tools go only to the agents that need them.
Read
Read customers with their sales areas and payment terms.
Read vendors, materials and stock by plant and storage location.
Read orders, lines, schedules and status.
Read open customer and vendor items for collections and payables.
Read balances by company code, account and period.
Read fields from any table you allow, with a filter.
Write
Enter and change orders in SD.
Raise and change orders in MM.
Post receipts, issues and transfers.
Post FI documents and supplier invoices.
Run any BAPI, with commit or rollback handled for you.
Run any remote-enabled function module, your own Z modules included.
Send an IDoc to ECC, such as an order, an invoice or master data.
Triggers
ECC sent an IDoc to engini: an order confirmation, a delivery, an invoice or master data.
Customers, materials, orders or documents changed, from ECC's change documents.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Already running ECC OData services through SAP Gateway? The OData connector reaches them too.
Connect your AI agent to SAP ECC. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your SAP ECC connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of SAP ECC tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects SAP ECC and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every SAP ECC tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to SAP ECC through engini
{
"mcpServers": {
"engini-sap-ecc": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your SAP ECC connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the SAP ECC tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on SAP ECC. Agents and workflows, across systems.
Orders from every channel into SD
Orders from Salesforce, Shopify or a customer email become ECC sales orders through the sales order BAPI, and the confirmation IDoc goes back to the customer.
Supplier invoices posted
A supplier invoice from the inbox is read by an agent, matched to the purchase order and posted as an incoming invoice in ECC.
ECC and S/4HANA side by side
During a move to S/4HANA, master data and open orders stay in step between ECC and the new system.
Answers without SAP GUI
An agent in Microsoft Teams answers stock, order and open-item questions from ECC. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between SAP ECC and another system engini connects is available.
You decide what each agent may do in SAP ECC. engini enforces it on every call.
Only the tools you allow
A toolset lists the SAP ECC tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own SAP ECC account and engini acts as that person, with their SAP ECC permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
SAP ECC behind your firewall.
If SAP ECC runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to SAP ECC while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.
On-Prem Agent guide →Connect SAP ECC in three steps. Then decide what each agent may do.
Sign in to SAP ECC
Install the engini On-Prem Agent on a server that can reach ECC, create an SAP communication user with only the authorizations the workflows need, then add an ECC connection with the application server or message server, system number, client and that user. Register the agent as an RFC destination in ECC to receive IDocs.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in SAP ECC from Claude, ChatGPT, Cursor or your own code.
SAP ECC and engini. Straight answers.
Can an AI agent write to SAP ECC, or only read?
Both. engini has tools to create and change sales and purchase orders, post goods movements, accounting documents and incoming invoices, call any BAPI or RFC function module, and send IDocs. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does engini help with the migration from SAP ECC?
Yes. We help you plan the move, map and check the data, load it and run the parallel period until you switch, working with your team or your implementation partner. Book a call and tell us what you run today and where you are moving.
Can we move from SAP ECC to an ERP other than S/4HANA?
Yes. engini connects to S/4HANA, NetSuite, Sage Intacct, Acumatica, SAP, Oracle and more, so you choose the ERP that fits the business, not the one the old vendor points to.
Do we have to switch everything on one day?
No. Load the new ERP first, then keep SAP ECC and the new system in sync during a parallel run, area by area if you like, and switch when the numbers match.
What happens to our SAP ECC history?
Bring the history you need into the new ERP, or keep SAP ECC read-only and let agents answer questions from it, through the same connection, until you retire it.
Can our implementation partner use engini?
Yes. Partners use engini to load, check and sync data during the move, and the same connections keep running the integrations after go-live.
When does maintenance for SAP ECC end?
SAP ends mainstream maintenance for ECC 6.0 on enhancement packages 6 to 8 on December 31, 2027, with optional extended maintenance to December 31, 2030. Systems on older enhancement packages lost mainstream maintenance at the end of 2025.
Do I need SAP Gateway or OData?
No. The ECC connector talks RFC, BAPI and IDoc, which every ECC system has. If you already publish OData services through SAP Gateway, the OData connector reaches them too.
Can it call our own Z function modules?
Yes. Call RFC Function Module runs any remote-enabled function module, your own included, and Call BAPI handles commit and rollback.
What if the tool I need is not listed?
Use Call BAPI or Call RFC Function Module to run any remote-enabled function in your system, and give them only to the agents that need them.
Does it also work with S/4HANA and Business One?
Yes. SAP S/4HANA and SAP Business One have their own connectors and pages.
Does the agent act as me in SAP ECC?
It acts as the SAP user behind the connection, with that user's authorizations. Every run is recorded under the person who started it.
Can a change in SAP ECC start work?
Yes. ECC sends IDocs to engini through the On-Prem Agent, and each one can start a workflow. Scheduled triggers check change documents for changed records. A workflow can include an AI agent step.