How to connect Claude to SAP Business ByDesign
Short answer
Claude reaches ByDesign through tools: usually an MCP server that wraps your custom OData services or web services, called from Claude on the desktop, in an app, or through the API. Hosting options include the Anthropic API, AWS Bedrock and Google Vertex AI, and a private open-weight model is the alternative when records cannot leave your network.
Finance and operations teams on ByDesign often reach for Claude for long-document work: reading a supplier contract against a purchase order, writing audit explanations, or reasoning over a messy export. That works with files alone. The more interesting move is letting Claude look things up in ByDesign itself while a person watches.
Claude's route to live data is tool use. You define tools with clear schemas and Claude decides when to call them. The Model Context Protocol packages that idea so one server can be reused by Claude Desktop, Claude Code, other clients and your own applications.
Because ByDesign is a SAP-hosted cloud product, the setup is about three choices: where Claude runs, what the tools expose, and which credential the tools use inside ByDesign.
What teams use it for
Contract versus purchase order review
Upload a supplier agreement and let Claude compare payment terms, lead times and price breaks with the lines of an open purchase order that a tool fetched.
Audit query answers
An auditor asks why a posting exists. Claude reads the document flow via a tool and writes a traceable explanation citing document IDs.
Month-end commentary
Feed it extracted P&L and balance sheet data to produce draft variance narratives for the controller to edit.
Customer-facing replies with facts
Claude drafts a reply to a delivery enquiry after retrieving status and dates, leaving the sending to a person.
Data cleanup planning
Before a master data load, have it inspect a sample of material or business partner records and list inconsistencies and proposed rules.
SAP Business ByDesign integration surface
- Custom OData services built on analytics data sources: the cleanest read interface for a Claude tool, with explicit fields and filters.
- SOAP web services bound to communication scenarios in a communication arrangement. Suitable for operations that have no OData equivalent, wrapped by your MCP server.
- Technical user in the communication system, with basic authentication or a certificate. The MCP server holds this; Claude never sees it.
- Document flow and business object references in ByDesign, which let a tool return links between order, delivery and invoice for explainable answers.
- Cloud Applications Studio actions for any controlled write that needs validation logic inside the tenant.
How it works
- 1
Choose where Claude runs
Options are the Anthropic API, Claude through AWS Bedrock, or Google Vertex AI. Pick the one your data residency and procurement rules allow, and read the data retention terms for it.
- 2
Define five to eight read tools
For example get_sales_order, get_purchase_order, get_supplier_invoice, get_stock_by_material, search_business_partner. Keep each output small and include IDs.
- 3
Implement them as an MCP server
The server translates a tool call into an OData or web service request using the technical user, and shapes the response.
- 4
Choose transport
Use stdio for a single user on a workstation. Use an authenticated HTTP transport for team use, with the identity of the caller passed through for logging.
- 5
Write a short system prompt
Tell Claude it is read-only, must cite document IDs, and must say when a tool returned nothing instead of guessing.
- 6
Evaluate on real questions
Collect twenty or thirty real questions from your team, record expected answers and re-run them after every ByDesign release or tool change.
Example flows
Why was this invoice blocked
Trigger: An accounts payable clerk asks, 'Why is supplier invoice 5100234 not paid?'
- Claude calls the invoice tool and gets status, amounts and block reason.
- It calls the purchase order and goods receipt tools for the linked lines.
- It compares quantities and prices against tolerance.
- It explains the mismatch and suggests who should act.
Result: A traceable explanation with document IDs in under a minute.
Contract check on upload
Trigger: A buyer uploads a renewed supplier agreement PDF.
- Claude extracts payment terms, Incoterms and price schedule from the document.
- A tool returns the current supplier terms and open order prices from ByDesign.
- Claude lists the differences.
- The buyer decides what to update in master data.
Result: Fewer silent mismatches between paper and system.
Keeping data on-prem
ByDesign runs in SAP's cloud, so the thing you can keep inside your walls is the model and the tool server. If your policy allows a hosted Claude via the Anthropic API, Bedrock or Vertex AI, you can still run the MCP server in your own network and send the model only what a tool returns. If it does not, run an open-weight model such as a Llama, Qwen or Mistral class model on your own GPUs behind the same MCP interface. Tools stay identical; you trade some reasoning quality for full control, and you can route sensitive questions to the private model and general ones to Claude.
Security checklist
- Hold the ByDesign credential in the MCP server, never in prompts or client configuration.
- Start read-only; add writes only as draft-and-approve actions.
- Pass the end user's identity to the server so logs show who asked, and scope tools by role.
- Review the retention and training terms of the specific Claude hosting option you choose.
- Rate-limit and alert on unusual query volumes against the tenant.
Ways to get it done
Claude with uploaded files only
Effort: None.
Good for contract and report analysis with no integration work.
Your own MCP server over custom OData
Effort: One to three weeks for a read-only set of tools.
Fits teams with a developer who can build and maintain a small service.
Netray-built tool layer with optional private model
Effort: A scoped pilot of a few weeks.
Fits teams that want governance, evaluation and a path to on-prem models.
Pitfalls
- !Exposing a generic query tool that lets the model request any field, which makes access control impossible to reason about.
- !Returning huge payloads and hitting context limits. Page results and summarise server-side.
- !Assuming Claude knows your custom fields and extension names. Describe them in tool descriptions.
- !Skipping regression tests after SAP's quarterly releases change a service.
- !Leaving stdio setups on shared laptops with the credential in a config file.
Frequently asked questions
Does Claude have a native SAP Business ByDesign connector?
I am not aware of an official one, and connector catalogues change, so check current listings. The practical route is an MCP server you or a partner build over ByDesign's custom OData or web services.
Where does my ByDesign data go when I use Claude?
Only the content you send, including tool results, goes to the model host you chose: Anthropic API, Bedrock or Vertex AI. Read the retention and training terms of that option. ByDesign data otherwise stays in your SAP tenant.
Can Claude post transactions in ByDesign?
It can be given tools that do, but the safer pattern is draft and approve. Claude prepares the content and a person or a separate service posts it with a restricted credential.
What if we cannot send data to any cloud model?
Run an open-weight model on your own infrastructure behind the same tool interface. ByDesign data still travels from SAP to your network over HTTPS, then stays within your control.
Do I need MCP specifically?
No. Plain tool use through the API works. MCP is useful because the same server then serves Claude Desktop, other clients and your own apps without rewriting the integration each time.
Want Claude working on your SAP Business ByDesign?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment