# AI Integration for SAP Business ByDesign, Built on OData

> Source: https://netray.co/erp-ai/sap-bydesign-ai-integration
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

SAP Business ByDesign is a multi-tenant SaaS ERP, which means you cannot self-host the ERP itself, but you can build an AI layer that reads ByDesign through its OData and SOAP communication scenarios and runs on infrastructure you control. For a mid-market finance team, that means natural-language reporting, variance commentary drafting, and document search without financial data ever reaching a public model API.

## Kind

platform

## Erp Family

sap

## Erp Products

- SAP Business ByDesign

## Industries

- Manufacturing
- Professional Services
- Wholesale Distribution

## Region

Europe

## Persona

Finance Director

## Eyebrow

SAP ByDesign + private AI

## Intro

SAP Business ByDesign is a good fit for a mid-market finance director precisely because it is fully managed: SAP hosts it, patches it, and upgrades it twice a year, and you are not carrying the infrastructure burden a larger on-premise SAP deployment would require. The trade-off is that ByDesign has no on-premise option and no direct database access, everything goes through its OData and SOAP web services, which shapes what an AI integration can and cannot do.

In practice, that limitation is less restrictive than it sounds. ByDesign's business configuration lets you activate specific communication scenarios and scope a technical communication user to exactly the entities, general ledger, cost centre reporting, sales quotes, business partner data, an AI layer actually needs, which is a reasonably clean integration surface once you know which scenarios to enable.

What a mid-market finance team is usually missing is not more data inside ByDesign, it is the ability to ask a plain-language question and get an answer, and the time saved not writing month-end variance commentary from scratch. A finance director with a lean team rarely has a dedicated BI resource to build that layer internally, and sending financial data to a public AI assistant is not something most finance leaders are comfortable approving, even when the underlying ERP is already SAP-hosted cloud.

This page describes an AI layer built specifically around ByDesign's OData integration model, deployed in a private cloud tenant or on your own infrastructure, so the model and the data it reasons over never leave an environment you control, and the outputs stay drafts a finance professional reviews rather than numbers that go straight into a board pack.

## Pain Points

### ByDesign's own reporting requires knowing where to look

**Detail:** Answering a specific finance question, why did this cost centre run over budget this quarter, means navigating to the right report variant and filtering it correctly, a skill that sits with one or two people on a lean finance team.

### Month-end variance commentary is written from scratch every cycle

**Detail:** Drafting the board-pack narrative explaining actual-versus-budget variance by cost centre is a recurring, largely repetitive writing task that still takes a finance professional several hours each close.

### ByDesign has limited native extensibility for building custom AI features

**Detail:** The Partner Development Infrastructure supports lightweight extensions, but building a genuinely custom AI experience inside ByDesign itself is not realistic; any serious AI capability has to live in a layer alongside it, reading through OData.

### A lean finance team has no dedicated BI resource

**Detail:** Mid-market finance directors rarely have a data analyst on staff to build and maintain natural-language reporting internally, which means this kind of capability either comes from a vendor or does not happen.

### Sending financial data to a public AI assistant is a hard no for most finance leaders

**Detail:** Even though ByDesign itself is SAP-hosted cloud, routing general ledger or customer data through a public model API for AI-assisted reporting is a different risk decision, and most finance directors we talk to are not willing to make it.

## Use Cases

### Natural-language financial reporting

**Description:** A finance user asks a plain-language question, for example a cost centre variance summary for the current quarter, and gets a grounded answer with the underlying report or journal entries cited.

**Erp Objects:** General ledger and cost centre reporting OData services, journal entry vouchers

**Outcome:** Answers a routine finance question in the time it takes to type it, instead of a report-navigation exercise that only certain team members can do quickly.

### AP/AR exception narrative

**Description:** The agent summarizes open item and payment run data into a plain-language cash and aging position, flagging accounts that have moved significantly since the last check.

**Erp Objects:** Accounts payable/receivable open items, payment run OData entities

**Outcome:** Gives a finance director a quick, readable cash position summary between formal reporting cycles rather than only at month-end.

### Sales quote drafting from history

**Description:** For a new customer quote, the agent finds pricing and terms from similar past quotes and drafts a first-pass proposal for the sales or finance team to adjust.

**Erp Objects:** Customer quote OData entities, business partner and pricing data

**Outcome:** Speeds up quote turnaround by grounding the first draft in actual pricing precedent rather than starting blank.

### Month-end variance commentary drafting

**Description:** Using actual-versus-budget data by cost centre, the agent drafts a first-pass narrative explaining the largest variances, for the finance team to verify and finalize for the board pack.

**Erp Objects:** Actual and budget/plan data by cost centre, general ledger account detail

**Outcome:** Cuts the writing time for month-end commentary meaningfully, since the numbers and likely drivers are already assembled rather than researched from scratch.

### Business partner data quality check

**Description:** Before month-end close, the agent flags likely duplicate or incomplete customer and vendor master records based on name, address, and tax ID similarity.

**Erp Objects:** Business partner OData entities (customer and vendor master)

**Outcome:** Catches a class of master data issues before they distort AR/AP aging or duplicate payment risk reports.

### Production or project order status Q&A

**Description:** For manufacturing or project-services customers on ByDesign, the agent answers plain-language questions about production or project order status pulled from the relevant OData entities.

**Erp Objects:** Production order or project task OData entities, depending on edition

**Outcome:** Gives a finance or operations user a quick status check without navigating to the underlying work centre view.

### Contract and document semantic search

**Description:** The agent indexes attachments linked to business objects, contracts, purchase orders, quotes, and lets a finance user search them in plain language rather than opening each record to find a specific clause or term.

**Erp Objects:** Attachments linked to business partner, sales, and purchasing objects

**Outcome:** Turns document lookup from a manual search-and-open exercise into a direct answer to a specific question.

## Architecture

**Overview:** Because ByDesign cannot be self-hosted, the AI layer connects entirely through its OData and SOAP communication scenarios and runs on infrastructure you control, with the model, retrieval index, and query log all sitting outside SAP's multi-tenant environment.

**Layers:**

#### ERP connectors

**Detail:** Read access through ByDesign OData services and SOAP communication scenarios, each explicitly activated in business configuration and scoped to a technical communication user with defined, limited authorizations.

#### Data and semantic layer

**Detail:** General ledger, cost centre, business partner, and sales entities are mapped to finance-team language, and scheduled batch extraction is used for heavier analytics given ByDesign's OData call rate limits.

#### Model serving

**Detail:** An open-weight model served on your own infrastructure or in a private cloud tenant within the EU, sized for a mid-market finance and operations team's query volume.

#### Retrieval and agents

**Detail:** Retrieval-augmented Q&A over financial and business partner data, plus drafting workflows for variance commentary and quotes, all grounded in data pulled through the connectors above.

#### Governance and audit

**Detail:** Every answer and draft is logged with the OData entities it was based on. Access mirrors the business role assignment a user already has in ByDesign, and nothing writes back to ByDesign by default.

## Deployment Options

### Customer-controlled private cloud AI layer

**Fit:** Mid-market firms comfortable with cloud infrastructure generally but not with sending financial data to a public model API.

**Detail:** The model and retrieval index run in a private cloud tenant you control, connected to ByDesign over a secured OData channel, with no data sent to a third-party model provider.

### On-prem AI layer over scheduled OData extracts

**Fit:** Firms wanting the model and data physically on their own hardware, even though ByDesign itself remains SAP-hosted.

**Detail:** A scheduled extract (hourly or nightly, depending on the use case) pulls OData entities into an on-prem semantic layer, so read-only natural-language Q&A does not require a live connection to ByDesign for every query.

### Hybrid

**Fit:** Organizations wanting near-real-time operational Q&A alongside deeper periodic financial analysis.

**Detail:** Real-time OData queries handle operational questions like current order status, while a scheduled extract feeds the deeper financial analysis and variance commentary use cases.

## Compliance

### Because the AI layer runs on infrastructure you control rather than a third-party model provider's, financial and business partner data used for reporting never leaves an environment covered by your own data processing agreement.

**Framework:** GDPR / UK GDPR

### Read-only, human-reviewed drafting and reporting outputs sit toward the limited-risk end of the Act's classification, and the governance layer's logging supports the transparency documentation a compliance review will ask for.

**Framework:** EU AI Act

### Deploying the AI layer in the same EU region as your ByDesign tenant avoids an unnecessary cross-border data transfer between the ERP and the AI layer reading from it.

**Framework:** Data residency (ByDesign EU data centres)

### SAP publishes its own compliance posture for ByDesign hosting; the AI layer adds its own access logging and role mirroring on top rather than duplicating financial data into a separate, less controlled store.

**Framework:** SOC 1 / SOC 2 (inherited from SAP's ByDesign hosting)

### HR and payroll-related OData entities are excluded from the AI layer's scope by default and only enabled with explicit sign-off, consistent with how most European finance and HR teams want employee data handled around any new reporting tool.

**Framework:** Employee data handling

## Integration Notes

ByDesign only exposes data through OData and SOAP communication scenarios, there is no direct database access as with an on-premise SAP system, so every integration starts with activating and scoping the right scenarios in business configuration.

A dedicated technical communication user is created with authorizations limited to the entities the AI layer needs, mirroring the business role assignment a real finance user would have.

ByDesign's OData call rate limits mean scheduled, batch extraction is generally preferred over constant polling for heavier reporting and analytics use cases.

The Partner Development Infrastructure can support lightweight custom OData extensions where needed, but the integration should tolerate ByDesign's twice-yearly tenant-wide upgrades without breaking, since schema and API details can shift between releases.

No write-back to ByDesign happens by default; ByDesign's process guardrails are intentionally tight, and quotes, journal entries, and master data changes are drafted for review, not submitted automatically.

Attachments and documents linked to business objects are indexed for semantic search as retrieval context, not duplicated as a separate system of record.

## Product Fit

### ERPray

**Why:** Natural-language question answering over ByDesign's general ledger, cost centre, and business partner reporting is ERPray's core pattern, applied through ByDesign's OData services.

### Custom build

**Why:** Month-end variance commentary drafting and quote drafting are bespoke workflows tuned to your board pack format and quoting process.

### DataRay

**Why:** Where a finance team wants to query ByDesign data alongside spreadsheets or other systems in one place, DataRay's mixed-source chat pattern applies.

## Engagement

### Discovery

**Duration:** 2-3 weeks

**Deliverables:**

- Review of which OData and SOAP communication scenarios are currently active and which need enabling
- Business configuration and authorization scoping plan for a technical communication user
- Prioritized use case list, typically natural-language reporting and variance commentary first
- Deployment model decision (private cloud, on-prem extract, or hybrid)

### Pilot

**Duration:** 5-7 weeks

**Deliverables:**

- Natural-language Q&A live over general ledger and cost centre reporting
- First-pass variance commentary drafted for one month-end close cycle
- Accuracy review against the finance team's own reports for the same period
- Go/no-go review with measured time saved on reporting and commentary drafting

### Production

**Duration:** 6-8 weeks

**Deliverables:**

- Rollout to the full finance team and relevant operations users
- Quote drafting and business partner data quality checks added
- Documented runbook for handling ByDesign's twice-yearly upgrade cycle

### Scale

**Duration:** Ongoing

**Deliverables:**

- Document and contract semantic search added
- Extension to additional business units or legal entities on the same ByDesign tenant
- Periodic review of OData scenario usage as ByDesign functionality evolves across releases

## Buyer Questions

- Does any part of the integration send our financial data to a public model API, given ByDesign itself is already SAP-hosted cloud?
- Which specific OData and SOAP communication scenarios does the integration require us to activate, and how tightly are they scoped?
- How does the solution handle ByDesign's twice-yearly tenant upgrades without breaking the integration?
- Can the AI layer run in an EU region matching our ByDesign tenant's data residency?
- Does the system ever write back to ByDesign, submit a journal entry, change a master record, and if so how is that gated?
- How is variance commentary accuracy validated against our own finance team's judgment?
- Is HR or payroll data excluded from the AI layer's scope by default?
- What happens to OData rate limits if multiple users query heavily at month-end close?

## Faq

### Can SAP Business ByDesign be run on-prem for AI purposes?

**Answer:** No, ByDesign itself is multi-tenant SaaS with no on-premise deployment option. What can run on-prem, or in a private cloud tenant you control, is the AI layer that reads ByDesign data through OData and reasons over it, which is the pattern described on this page.

### Does this require custom development inside ByDesign?

**Answer:** Generally no. The integration activates and scopes existing OData and SOAP communication scenarios in ByDesign's business configuration. The Partner Development Infrastructure can support lightweight extensions where genuinely needed, but most use cases do not require them.

### How does the AI layer handle ByDesign's twice-yearly upgrades?

**Answer:** The integration is built to tolerate schema and API drift between ByDesign releases rather than assuming a fixed structure, and the connector configuration is reviewed as part of ongoing support so an upgrade does not silently break a report or query.

### Will this write journal entries or change master data automatically?

**Answer:** No, by default it does not. Quote drafts, variance commentary, and master data quality flags are all drafts a finance professional reviews and acts on through the normal ByDesign process; nothing writes back automatically.

### Is our financial data safe from being used to train a public AI model?

**Answer:** Yes, that is the specific design goal. The model runs on infrastructure you control, private cloud or on-prem, and is never called as a public API, so your data is never sent anywhere a model provider could use it for training or anything else.

### Can this work alongside other systems, not just ByDesign?

**Answer:** Yes, where a finance team wants to query ByDesign data alongside spreadsheets, a CRM, or other sources in one place, that broader mixed-source pattern is what DataRay is built for.

### How long does a typical pilot take for a mid-market finance team?

**Answer:** A pilot covering natural-language reporting and one month-end variance commentary cycle typically runs five to seven weeks, timed to align with an actual close so the drafted commentary can be validated against real numbers.

## Search terms

SAP Business ByDesign AI, ByDesign AI integration, SAP ByDesign copilot, on-prem AI for SAP ByDesign, SAP ByDesign generative AI, SAP ByDesign OData AI, mid-market SAP AI, SAP ByDesign natural language reporting, SAP ByDesign AI Europe, private AI for SAP ByDesign, SAP ByDesign finance AI, SAP ByDesign AI GDPR

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