# AI for SAP Business One, Without Sending Your Books to a Public API > Source: https://netray.co/erp-ai/sap-business-one-ai-integration > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: AI for ERP ## Short answer SAP Business One's Service Layer and DI API already expose most of what a small manufacturer needs for AI: sales orders, production orders, item master, and financials, all through a documented interface. A private LLM grounded in that data, running on a modest on-prem server or a single private-cloud GPU instance, can answer questions and draft documents without the owner sending customer and financial data to a public AI service. ## Kind platform ## Erp Family sap ## Erp Products - SAP Business One - SAP Business One (HANA) ## Industries - Manufacturing - Electronics ## Region Global ## Persona Owner / Finance Director ## Eyebrow SAP Business One + AI ## Intro If you run SAP Business One, whether on the SQL or HANA edition, you are probably wearing several hats at once: owner, finance director, and de facto IT decision-maker. Most AI copilot pitches assume an enterprise SAP landscape with a dedicated security team to review them, which is not your situation, but the underlying need is the same: reports that take too long, questions that come up between reports, and a reluctance to hand a chatbot your customer list and margins. Business One's data model works in your favor here. The Service Layer, a documented REST interface covering Business Partners, Items, Orders, Invoices, and Production Orders, along with the DI API for older SQL-edition installs, gives a private AI layer a compact, well-understood integration surface. This is a smaller project than grounding an AI on a large enterprise SAP landscape, both in integration effort and in the hardware needed to run it. The hardware requirement itself is modest. Business One's data volume rarely needs more than a single GPU server or a small private-cloud instance to serve a self-hosted model, which keeps the cost proportional to a company your size rather than sized for an enterprise budget you don't have. This page covers what a Business One AI project actually looks like: the use cases, the architecture, and what it costs to keep customer and financial data inside your own control the whole way through. ## Pain Points ### Enterprise AI pricing doesn't fit a five-person finance team **Detail:** Most AI copilots are built for large enterprise SAP landscapes and price themselves out of reach for a Business One shop with a small finance and operations team. ### Reports that should take minutes take hours **Detail:** Questions like which customers are overdue or which items are below reorder point mean exporting to Excel and pivoting by hand, every week, because building a formal report for each one isn't practical. ### Owners are wary of public chatbots but have no security team **Detail:** Sending customer lists, pricing, and margins to a public chatbot feels risky, but there's no dedicated IT security function to evaluate an on-prem alternative properly. ### Custom fields capture business logic nothing else reads **Detail:** User-defined fields and user-defined tables capture years of business-specific logic, like lot tracking or certifications, that no off-the-shelf AI tool knows how to interpret. ### Crystal Reports backlog keeps growing **Detail:** Crystal Reports and B1 query generator reports pile up because nobody has time to build a new one for every ad hoc question a manager asks between formal reporting cycles. ## Use Cases ### AR aging and collections drafting **Description:** The agent reads overdue invoices and drafts a collections email for each overdue account, ready for review. **Erp Objects:** OCRD Business Partners, OINV/INV1 Invoices, Service Layer BusinessPartners and Invoices entities **Outcome:** turns a weekly AR aging review into a ranked list with draft follow-up emails already written ### Reorder point alerts in plain language **Description:** The agent reads stock levels against reorder points and drafts a plain-language summary of what to reorder and why. **Erp Objects:** OITM item master, OITW warehouse stock, MRP recommendation report **Outcome:** replaces a manual spreadsheet export with an on-demand summary a buyer can act on directly ### Production order status Q&A **Description:** A production planner asks which production orders are behind schedule and gets an immediate answer. **Erp Objects:** OWOR Production Orders, WOR1 components **Outcome:** gives a production planner instant status without waiting on a Crystal Reports run ### Margin explanation on sales orders **Description:** When a sales manager flags a low-margin order, the agent explains why, pulling item cost and pricing context. **Erp Objects:** ORDR/RDR1 sales orders, OITM item cost, price lists **Outcome:** shortens the investigation when a sales manager flags a low-margin order that needs an explanation ### Plain-language monthly financial summary **Description:** The owner asks how the business did this month versus last month, and the agent answers from journal entries. **Erp Objects:** OJDT journal entries, OACT chart of accounts **Outcome:** gives an owner without a controller on staff a plain-language monthly summary instead of a raw GL export ### UDF/UDT-aware document search **Description:** The agent understands custom fields captured on sales orders or items, such as lot codes or certifications, and answers questions using them. **Erp Objects:** UDFs on OITM/ORDR, UDTs for custom tracking **Outcome:** makes years of custom fields actually queryable instead of only visible one record at a time on a form ### Vendor price comparison drafting **Description:** A buyer asks how a vendor's current pricing compares to purchase history, and the agent drafts a summary. **Erp Objects:** OPOR/POR1 purchase orders, item purchasing data **Outcome:** gives a buyer a quick comparison without manually pulling and reconciling PO history ## Architecture **Overview:** The architecture is sized to Business One's actual scale: a single GPU server or small private-cloud instance, connected to Business One through its Service Layer or DI API, with UDFs and UDTs indexed alongside the standard fields. **Layers:** #### ERP connectors **Detail:** SAP Business One Service Layer for HANA and current SQL editions, or the DI API for older SQL-edition installs; existing B1if integrations are reused where they already exist. #### Data/semantic layer **Detail:** A read replica or scheduled extract of core tables (OCRD, OITM, OINV, OWOR), including UDFs and UDTs, with filtering by business partner group or warehouse where relevant. #### Model serving **Detail:** A single GPU server or a small private-cloud GPU instance, running an open-weight model with vLLM or Ollama, sized to Business One's typical query volume. #### Retrieval/agents **Detail:** RAG over reports and documents, with agent tools scoped to specific Service Layer entities so the AI cannot act beyond what those entities expose. #### Governance/audit **Detail:** A query log, an approval step before any document such as an email or PO goes out, and a simple audit export for the owner or accountant to review. ## Deployment Options ### Air-gapped on-prem **Fit:** manufacturers with export-controlled products or customers who require it contractually **Detail:** Runs on a single server in the existing server closet; more infrastructure than most Business One shops need unless a customer specifically requires it. ### Private/sovereign cloud **Fit:** the typical SAP Business One SMB, especially those already on B1 Cloud or a hosting partner **Detail:** A dedicated small GPU instance in a private cloud region, sized to Business One's data volume, is usually the most cost-effective option for most shops. ### Hybrid **Fit:** Business One on-prem today, considering B1 Cloud later **Detail:** The model and RAG layer are hosted separately from the Business One server itself, connected over the Service Layer through a secure link, so a later move to B1 Cloud does not require rebuilding the AI layer. ## Compliance ### Keeping the model and retrieval index in a private instance means customer lists, pricing, and margins are never sent to a public AI service as part of normal use. **Framework:** Customer and pricing data privacy ### Personal data in Business Partner records stays inside the private deployment's data boundary; retention and deletion follow the same policy as the underlying Business One database. **Framework:** GDPR (for EU customers or vendors) ### The AI drafts documents such as emails and purchase orders; a named user still approves and sends them, preserving the same approval chain Business One's own authorization system already enforces. **Framework:** Segregation of duties ### AI-assisted financial summaries are logged with the source journal entries and GL accounts used, so an accountant or auditor can trace a plain-language summary back to its source data. **Framework:** Audit trail for finance ## Integration Notes SAP Business One Service Layer is the preferred integration point for HANA and current SQL editions; it exposes Business Partners, Items, Orders, Invoices, and Production Orders as REST resources. Where Service Layer coverage is incomplete on an older SQL-edition install, the DI API SDK provides the same access from a Windows-hosted integration component. UDFs and UDTs need to be inventoried during discovery; they usually carry the business-specific logic, like lot tracking or custom statuses, that makes an AI's answers actually useful. Crystal Reports and the B1 query generator remain the right tool for fixed, scheduled reporting; the AI layer targets the ad hoc, conversational questions those reports don't cover. Write-back, such as creating a draft PO or updating a UDF, should go through the same Service Layer entity a B1 add-on would use, with the standard Business One authorization check applied. For B1if-based integrations already in place, the AI layer can subscribe to the same message flows rather than duplicating existing integration logic. ## Product Fit ### ERPray **Why:** Conversational question-answering and simple dashboards over Business One's Service Layer data fit ERPray directly, without needing a bespoke build for a first phase. ### Custom build **Why:** UDF and UDT-aware retrieval and document drafting, like collections emails or PO comparisons, tailored to a specific Business One configuration usually needs a light custom layer on top. ## Engagement ### Discovery **Duration:** 1-2 weeks **Deliverables:** - Inventory of Service Layer entities in use and key UDFs/UDTs - Priority use cases agreed with the owner or finance director - Hosting decision between a small on-prem server and a private-cloud GPU instance - Data volume and sizing estimate ### Pilot **Duration:** 4-6 weeks **Deliverables:** - Read-only Q&A agent for one or two priority use cases such as AR aging or low-stock alerts - Model serving deployed on the chosen infrastructure - Review of answer accuracy against known reports - Go/no-go decision ### Production **Duration:** 4-8 weeks **Deliverables:** - Document drafting workflows such as collections emails and PO comparisons, with an approval step - Access limited to the users who need it, mapped to existing Business One authorizations - Basic monitoring and query log - Short training session for the finance and operations team ### Scale **Duration:** ongoing **Deliverables:** - Additional reports and use cases added incrementally - Periodic accuracy and cost review - Optional move to B1 Cloud hosting without rebuilding the AI layer - Usage summary for the owner ## Buyer Questions - Does this send our customer list, pricing, or financials to a public AI API at any point? - Does it read our UDFs and UDTs, or only the standard Business One fields? - What's the actual hardware or hosting cost, not just the software cost? - Who has to approve before a drafted email or PO actually goes out? - Does this work with our current Business One edition, SQL or HANA, and version? - What happens to this investment if we move to B1 Cloud later? ## Faq ### Is SAP Business One big enough to justify AI? **Answer:** Yes, and often more directly than a large enterprise SAP landscape. Business One's Service Layer exposes a compact, well-documented set of entities, Business Partners, Items, Orders, and Production Orders, which makes grounding a private LLM in real data a smaller project than on S/4HANA or ECC. Many SMB manufacturers see value from a handful of use cases, like AR aging and low-stock summaries, without a large integration effort. ### What does on-prem AI mean for a company with no dedicated IT team? **Answer:** It typically means a single server or a small private-cloud GPU instance, sized to Business One's data volume, running the model and a lightweight retrieval index. It does not require a data center or a large infrastructure team; a hosting partner or the same firm that supports the Business One install can usually manage it. ### Can the AI read our custom fields (UDFs) and custom tables (UDTs)? **Answer:** Yes, provided they are inventoried during discovery. UDFs and UDTs usually carry the business-specific logic, like lot tracking, certifications, or custom order statuses, that makes an AI's answers actually match how the business runs, rather than only the out-of-the-box Business One fields. ### How much does an SAP Business One AI project cost compared to enterprise SAP AI? **Answer:** Meaningfully less in absolute terms, because Business One's data volume and hardware needs are smaller: often a single GPU server or a modest private-cloud instance is enough, versus a cluster sized for an enterprise S/4HANA landscape. Integration effort is also typically lighter given the Service Layer's compact entity model. ### Is our data safe if we don't have an IT security team to review the vendor? **Answer:** Ask directly where the model and data physically run, and get it in writing that customer and financial data used for grounding never leaves that environment. A private on-prem or private-cloud deployment, with no calls to a public model API, is the simplest architecture to verify even without a dedicated security reviewer. ### Does this replace Crystal Reports or the B1 query generator? **Answer:** No, and it shouldn't try to. Crystal Reports and the query generator remain the right tool for fixed, scheduled reports. The AI layer is for the ad hoc questions that come up between reports, like why a specific order's margin is low, where building a new formal report every time isn't practical. ### What's a realistic first project for a Business One shop? **Answer:** AR aging with draft collections emails, or low-stock alerts explained in plain language, are common starting points: high-frequency manual work, clear source data in OCRD, OITM, and OWOR, and an easy way to measure time saved. A four to six week pilot on one or two such use cases is enough to judge whether it's worth expanding. ## Search terms SAP Business One AI, SAP B1 AI integration, AI for SAP Business One, SAP Business One copilot, on-prem AI for SAP B1, SAP Business One generative AI, SAP B1 Service Layer AI, private LLM for SAP Business One, SAP Business One reporting AI, small manufacturer ERP AI, SAP B1 HANA AI, SAP Business One chatbot --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json