# How to connect Claude to SAP ECC 6.0

> Source: https://netray.co/integrations/sap-ecc-claude
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Claude reaches ECC through a tool layer you control: usually a Model Context Protocol server that wraps BAPIs or OData, reachable by Claude over HTTPS or run locally over stdio. You can call Claude via the Anthropic API, AWS Bedrock or Google Vertex AI, and for plants that cannot send data out, replace it with an open model behind the same tools.

## System

SAP ECC 6.0

## Capability

claude

## Intro

Teams on ECC 6.0 who look at Claude are often attracted to its long-context reading of documents and its careful tool use. The questions that come up are practical: how does Claude see our SAP data, who sees the prompts, and which region do the requests go to?

There is no built-in ECC connector. Claude uses tools. The tools are defined by you, usually through an MCP server, and the server decides which BAPIs and tables are visible. That separation is helpful: SAP security reviews the tool layer, not the model.

Where you run Claude matters as much as how you connect it. The same tool layer can work with the Anthropic API directly, with Claude on AWS Bedrock or Google Vertex AI inside a cloud account you already govern, or with a different model entirely if you need the data to stay inside the plant.

## Use Cases

### Reading long supplier and quality documents against ECC records

**Description:** Claude reads a supplier contract or a corrective action report and checks the stated lead times, part numbers and batch references against the vendor and material master data it can look up.

### Month-end explanation of variances

**Description:** A finance user asks why a production order shows a cost variance. Claude reads the order's settlement data and goods movements through approved tools and writes an explanation in plain language.

### ABAP and user-exit review

**Description:** Developers share a Z program or enhancement for review and a plain-English description of what it does, which is useful when the original author left years ago.

### Procurement analysis

**Description:** Buyers ask for spend by vendor and material group from approved report outputs, then ask Claude to draft sourcing notes.

### Migration preparation

**Description:** Claude helps catalog custom objects and process variants ahead of an S/4HANA move by summarizing exported object lists and usage statistics (such as from the SCMON or UPL tools, hedged to what you have enabled).

## System Surface

A custom MCP server wrapping RFC calls (via the SAP NetWeaver RFC SDK and a Python or Node binding) to BAPIs and Z function modules, exposing each as a named tool.

Optional OData services from SAP Gateway (SEGW) that the MCP server can call over HTTPS rather than RFC, which suits teams that prefer HTTP and already monitor Gateway.

Transport choices: stdio for a local desktop client on the same machine, and streamable HTTP for a shared server that Claude clients reach inside your network or through a controlled gateway.

ECC authorizations: a service user in SU01, a PFCG role restricting S_RFC to named function groups, plus plant and company code limits.

Document sources outside ECC (DMS, SharePoint, file shares) that you can expose as separate MCP resources so Claude reads drawings or certificates alongside the SAP data.

## How It Works

### Define the tool list with SAP owners

**Detail:** Start with four to six read tools: material lookup, stock by plant, open PO lines, production order status, vendor details, sales order status.

### Build the MCP server

**Detail:** Implement each tool with strict input validation. Return compact JSON with units and descriptions. Do not return raw tables with hundreds of columns.

### Pick the Claude deployment

**Detail:** Choose the Anthropic API, Claude on Amazon Bedrock or Claude on Google Vertex AI based on where your governance, billing and region residency already sit. Check current regional availability with the provider.

### Wire the client

**Detail:** Point Claude Desktop, an internal chat app or your own agent code at the MCP server. For shared use, host it over HTTP behind SSO and a reverse proxy.

### Test with real planner questions

**Detail:** Collect twenty actual questions from MRP controllers and buyers. Compare Claude's answers with SAP screens. Fix tool descriptions where it picks the wrong tool.

### Review data handling terms

**Detail:** Read the commercial terms for retention and training on your chosen route, and document them in your vendor risk record.

## Example Flows

### Why is this production order late?

**Trigger:** A supervisor asks Claude about order 1000456.

**Steps:**

- Claude calls the production order status tool and reads operations and confirmations.
- It calls the component availability tool and finds one item short at the work center storage location.
- It checks open POs for that item and the confirmed date.
- It summarizes the root cause and suggests who to contact.

**Result:** A clear cause and next step without browsing CO03, MD04 and ME2M separately.

### Contract versus master data check

**Trigger:** A buyer uploads a new supplier agreement PDF.

**Steps:**

- Claude extracts payment terms, lead times and part numbers.
- It calls the vendor and info record tools to compare them to ECC.
- It lists mismatches for the buyer to resolve.

**Result:** Fewer surprises after contract signature, with no change made in SAP until the buyer decides.

## On Prem

If the rule is that no ECC content may leave the building, Claude as a hosted or cloud-managed model will not meet it. The practical on-prem answer is to keep the MCP tool layer exactly as designed and swap the model for an open-weight one (Llama, Qwen, Mistral or gpt-oss class) served with vLLM or Ollama on local GPUs, since MCP is an open protocol with clients that support various models. Some teams run Claude through Bedrock or Vertex in a private cloud account for general work and the on-prem model for sensitive plants. Netray can build the tool layer once and support both, so you can decide model location per data class rather than per project.

## Security

- Treat the MCP server as a privileged integration: dedicated ECC user, least-privilege PFCG role, no dialog logon type.
- Authenticate users to the MCP server through SSO and pass the identity into audit logs.
- Keep tools read-only at first; add write tools only with an approval step.
- Filter output fields in the server, not just in the system prompt.
- Verify the retention and training terms of the exact route you use (API, Bedrock, Vertex) and record them.

## Options

### Off-the-shelf SAP MCP or connector

**Fit:** Several community and commercial SAP connectors exist, mostly S/4HANA or OData oriented; check ECC 6.0 support and review their code or terms before use.

**Effort:** Low to try, but expect gaps for Z objects.

### Build your own MCP server

**Fit:** Best control and a good fit if you have developers who know RFC and Python or TypeScript.

**Effort:** Two to four weeks for a first read-only set.

### Partner build with model choice

**Fit:** When you need an on-prem option, audit trail and SAP security review support together.

**Effort:** Pilot over a few weeks; Netray builds with your SAP team.

## Pitfalls

- Returning very large result sets, which wastes context and gives worse answers. Summarize server-side.
- Vague tool descriptions that make Claude choose the wrong BAPI or hallucinate parameters.
- Forgetting that RFC calls are synchronous and can hold dialog or background work processes under load.
- Not testing with a restricted user, so authorization errors only appear in production.
- Assuming a cloud region choice equals data residency without checking the provider's current terms.

## Faq

### Does Claude have an SAP ECC connector?

**Answer:** Not an official one for ECC 6.0. Claude connects through MCP servers or tool definitions you supply. You can adapt a community SAP connector or build your own around BAPIs and OData, and have your SAP security team review it.

### Can Claude run on-premises?

**Answer:** Claude is offered through Anthropic's API and cloud platforms such as Bedrock and Vertex AI, not as a model you host in your own data center. For fully on-prem requirements, use an open-weight model behind the same MCP tools.

### Which is better for ECC, stdio or HTTP transport?

**Answer:** Stdio suits a single power user on a workstation. For a team, host the MCP server over HTTP behind single sign-on so you get central logging, rate limits and one place to update tools.

### Can Claude change data in ECC?

**Answer:** Only if you give it a tool that does. We advise read-only first. If you add a write tool, make it narrow, require explicit approval from a named user and log the full request and ECC document number returned.

### Does the plan to leave ECC by 2027 change this?

**Answer:** Build the tools around business functions such as get stock or get PO status. The MCP interface stays the same when the back end moves to S/4HANA, so the work is not wasted.

## Search terms

sap ecc claude integration, claude for sap ecc, connect claude to sap ecc, claude mcp sap ecc, claude sap ecc 6.0, anthropic claude sap integration, claude bedrock sap ecc, claude vertex sap ecc, claude desktop sap connector, claude ai sap manufacturing

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json