A plant on SAP Business One keeps Business One as its record. Morsa, the AI that operates the factory for you, reads the production orders, purchase orders, goods receipt POs, stock transfers and sales orders that SAP exposes through its documented interfaces, connects them to what people say in the plant’s group chats and email, and handles what happens when reality moves off the plan: who is told, what is chased, what is proven done. Nothing is migrated, nobody gets a new login, and Business One is not replaced. SAP Business One is one of the systems shown on Morsa’s integration flow, alongside Business Central, Odoo, Zoho, QuickBooks and spreadsheets.
In this guide
What does SAP Business One do well, and where is the gap?
Which SAP interfaces does Morsa use to read Business One?
Which Business One objects does Morsa read, and what does it do with each?
What does a caught shortage look like on a Business One plant?
Does Morsa write to Business One?
Does SAP’s own AI cover this for Business One?
Where does Morsa run alongside Business One?
What should a plant check before starting?
What changed at plants running Morsa above their ERP?
Sources, Changelog
What does SAP Business One do well, and where is the gap?
SAP describes Business One as “an integrated enterprise resource planning (ERP) solution for small and midsize businesses, as well as subsidiaries of large enterprises” (SAP Help Portal), and its 2024 solution brief says “Every day over 80,000 customers rely on SAP Business One” with “local support from over 850 partners” (SAP solution brief). For a manufacturer the relevant module is Production and MRP: “create and maintain multilevel bills of materials (BOMs), issue and release production orders manually or by backflush,” and “Production orders can be created manually or generated automatically based on sales orders using the Procurement Confirmation Wizard or from an MRP order recommendation” (SAP Help Portal, Production).
That is the record, and it is a good one. The gap is the floor and the day. Business One does not message the purchasing head when a supplier’s email moves a delivery by three days, does not know that the stores message at 9:10 p.m. affects three sales orders on Line 2, and does not chase anyone. On the practitioner thread quoted in manufacturing ERP software, a user calls it “fine as an ERP but you cannot really use it to manage a shop floor” without an overlay or heavy partner work. Morsa is that overlay for coordination, not for execution.
Which SAP interfaces does Morsa use to read Business One?
SAP documents three ways in, and Morsa uses whichever the plant’s Business One version and partner setup allow. All three are SAP’s own, not a third-party connector.
Interface | What SAP says it is | What it means for Morsa |
|---|---|---|
Service Layer | “SAP Business One Service Layer is a new generation of extension API for consuming SAP Business One data and services. It builds on core protocols such as HTTP and OData” (SAP, Working with SAP Business One Service Layer) | The preferred path: standard HTTPS and OData, read-mostly, on HANA or SQL Server |
DI API | “A collection of COM business objects and services for updating, retrieving, and manipulating data in SAP Business One” (SAP SDK Help Center) | The older Windows path; SAP states the Service Layer and DI API “have identical definitions for objects and object properties” |
Integration framework | “The integration framework for SAP Business One comprises a number of business scenarios that enable you to integrate the SAP Business One application with third-party software and mobile devices” (SAP Help Portal) | Where a partner already runs B1if scenarios, Morsa can take an event feed from it instead of polling |
Three facts about the Service Layer set the shape of the integration. It “supports OData version 3, version 4” with separate metadata endpoints for each (“/b1s/v1/$metadata is for odata v3”, “/b1s/v2/$metadata is for odata v4”). It “runs on both SUSE Linux Enterprise and Microsoft Windows operating systems (as of SAP Business One 10.0 PL01).” And it works on both database editions; SAP’s guides cover “versions for both Microsoft SQL and SAP HANA.” If the plant runs a database-level export or a partner’s reporting extract instead, Morsa can read that too; any platform with an API, a database, a file export or an email trail can be connected.
Which Business One objects does Morsa read, and what does it do with each?
The object names below are SAP’s Service Layer names, from SAP’s own documentation. Morsa reads them; it does not define them.
Business One object (Service Layer name) | What it holds | What Morsa does with it |
|---|---|---|
ProductionOrders | The order to make: item, planned quantity, due date, components, stages | Watches quantity and date against the sales orders behind it; when a component is short or a stage slips, works out which customer orders move |
PurchaseOrders | What was ordered from a supplier, with promised dates | Compares the promised date with what the supplier actually said in email or a group, and chases purchasing before the date, not after |
PurchaseDeliveryNotes | Goods receipt POs: what actually arrived | Closes a material job on the receipt, not on a “done” message; flags short or wrong receipts against the order |
StockTransfer | Material moved between warehouses or bins | Confirms that staged material reached the line the schedule assumed |
Orders | Sales orders and their delivery dates | The consequence side: which customer commitment a shortage or a slipped production order puts at risk |
InventoryGenEntries, InventoryGenExits | Goods receipts and issues, including issue to production | Reconciles what the plan consumed against what the floor drew |
Items, BusinessPartners | The material master and the suppliers and customers | Names things the way the plant does, and knows who to call |
The names are confirmed in SAP’s Service Layer guide, which lists PurchaseDeliveryNotes, PurchaseOrders, Orders, InventoryGenEntries, InventoryGenExits, Items and BusinessPartners among the objects “enabled with the Etag mechanism” as of 10.0 FP 2102, names ProductionOrders in its metadata appendix, and uses the singular StockTransfer for the transfer object (SAP, Working with SAP Business One Service Layer). In plain English, SAP’s process map calls these “Purchase order, Goods receipt PO, A/P invoice”, “Production order”, “Issue to production, Receipt from production” and “Sales order, Delivery note” (SAP Business One road map, March 2026).
What does a caught shortage look like on a Business One plant?
The pattern is the same as the one on the J4S customer story, with Business One as the ERP.
9:10 p.m., Stores group. The stores in-charge posts that 6 mm clear stock is enough until Wednesday. Nobody replies.
9:10 p.m., Morsa. Reads the message, reads the open Orders and ProductionOrders in Business One that consume that item, finds three on Line 2 dispatching Thursday and Friday.
9:11 p.m., Purchase group. Morsa creates “Cover 6 mm clear for Line 2 orders 4471, 4473, 4478”, owner the purchasing head, due Tuesday noon, and posts it with the three orders and their dispatch dates.
Tuesday 3:20 p.m. Purchasing posts the supplier’s confirmation for Wednesday morning. Morsa moves the due date and notes who moved it and why. If the plant’s rules allow, the promised date on the PurchaseOrders record is updated too; if not, Morsa asks the owner to do it.
Wednesday. The goods receipt PO (PurchaseDeliveryNotes) posts. The job closes on the receipt.
The night-shift case runs the same way with different objects. A manager sets an 8,000-part target; seven hours later dispatch posts photos showing parts unavailable. Morsa compares the schedule (4,131 units) with dispatch (4,035), finds the 96-piece shortage, links it to the target, tells dispatch to arrange the parts, tells production the target is blocked by supply, and opens a high-priority dependency, in under a minute.
Does Morsa write to Business One?
Only within the rules the plant approves, and Business One stays the record either way. Reading is the default. Routine writes a plant typically allows are a promised-date change on a purchase order once the supplier has confirmed it in writing, a remark on a production order, and an activity against a business partner. Consequential actions, such as changing a production plan or committing to a supplier, follow the customer’s approval rules and go to a named person. Every write is attributed and reversible, and system actions are verified from system state, not from a “done” message.
Where a partner has locked the Service Layer to read-only, Morsa works read-only and routes every change to the person who owns it. That is a configuration choice, not a limitation of the loop.
Does SAP’s own AI cover this for Business One?
Not today, by SAP’s own road map. SAP’s March 2026 road map for Business One lists “SAP Document AI solution and available integration to SAP Business One” for vendor invoices, and planned items including “SAP’s generative AI hub and SAP AI Core services enablement for SAP Business One for partner extensions” and “Open-source support for MCP server to enable SAP Business One for AI agents’ adoption with partner extensions” (SAP Business One road map, March 2026). The road map does not name Joule, SAP’s assistant, anywhere in its 49 pages, and it carries SAP’s caveat: “This is the current state of planning and may be changed by SAP at any time.”
Two things follow. SAP’s AI for Business One is document processing and a platform for partners to build on, not coordination across the plant’s people. And the planned MCP server is good news for a plant on Morsa: it is a documented, open way for an agent to reach Business One that would sit beside the Service Layer. The road map also states “Version 11 to follow version 10 in 2027” and a feature-package cadence through “SP 2605, FP 2608, SP 2611, FP 2702”, so the interfaces above are the ones a plant will be on for the next two years.
Where does Morsa run alongside Business One?
Wherever Business One does. SAP: “Flexible for any business, it can be deployed on-premise or in the cloud, running on SAP HANA or Microsoft SQL servers,” with cloud “through partner-hosted options” (SAP solution brief). Morsa runs in its own cloud, in the plant’s private cloud, or fully on-premise with the AI models and databases on hardware inside the plant, so an on-premise Business One under an ITAR or CMMC policy can be read without operational data leaving the perimeter. The Service Layer’s HTTPS endpoint, or a database read, is reachable from any of the three.
What should a plant check before starting?
Five questions for the plant’s Business One partner, each answerable in a day.
Which version and feature package? The Service Layer facts above are documented for 10.0; SAP publishes release planning in SAP Note 2267770.
Is the Service Layer installed and reachable? It is a separate server component “built on the Apache HTTP Web server.” Many partner installs have it; some do not.
HANA or SQL Server? Both work; it decides which administrator’s guide applies.
Which Business One user will Morsa read as? A dedicated user with read rights on Production, Purchasing, Inventory and Sales, and write rights only for the objects the plant approves.
Where do the supplier emails and the group chats live? Business One holds the promised date; the supplier’s real date is usually in an inbox. Morsa needs both.
SAP does not publish a list price for Business One; its brief says the product is “Available exclusively through SAP partners.” Morsa is priced per plant, not per user, with a guarantee; see how Morsa is priced.
What changed at plants running Morsa above their ERP?
J4S, a 120-person glass plant, was onboarded in two days: Morsa joined the Production, Stores, Purchase and Dispatch groups and connected to the ERP on day one. On-time completion of operational commitments rose from about 30% to about 75% in the first four weeks, across about 900 commitments, with no new software. Production Head Anil Kohli: “Our people don’t have to learn any new software. The chasing happens in the group chats they already use.” At JRG Automotive, Morsa identified 5 of 8 production-stopping material shortages early enough to act and saved the plant $2 million.
Bring one problem from your plant. We’ll show you how Morsa would have caught it, against your Business One. Book the call with Vedant.
Sources
SAP, Working with SAP Business One Service Layer, 10.0, PDF, https://help.sap.com/doc/fc2f5477516c404c8bf9ad1315a17238/10.0/en-US/Working_with_SAP_Business_One_Service_Layer.pdf (fetched 20 September 2026)
SAP, SAP Business One SDK, Getting Started (DI API definition), https://help.sap.com/docs/SAP_BUSINESS_ONE/a2c93a1c88a24f1faeee3d3f62fbde7a/8af015f4e12c4848ba17e9b851685cd2.html (text retrieved 20 September 2026 through SAP Help Portal’s search index; the HTML page renders client-side)
SAP, Integration Framework, SAP Business One 10.0, https://help.sap.com/docs/SAP_BUSINESS_ONE/68a2e87fb29941b5bf959a184d9c6727/d7dceab0d1ae42b1929ffaf1168a0bf7.html (same retrieval method)
SAP, SAP Business One 10.0 (product definition), https://help.sap.com/docs/SAP_BUSINESS_ONE/68a2e87fb29941b5bf959a184d9c6727/44c4c1cd7ca22e17e10000000a114a6b.html (same retrieval method)
SAP, Production module topic, https://help.sap.com/docs/SAP_BUSINESS_ONE/68a2e87fb29941b5bf959a184d9c6727/44f29313df7365fbe10000000a1553f7.html (same retrieval method)
SAP, Introduction to SAP Business One, solution brief, 2024, PDF, https://help.sap.com/doc/776407cb9fa24a149341faee1d9b60ac/10.0/en-US/SBO_Solution_Brief_Online_2024_EN.pdf (fetched 20 September 2026)
SAP, SAP Business One road map, March 2026, PDF hosted by an SAP partner, https://www.business-one-beratung.de/fileadmin/user_upload/SAP_Business_One_Road_Map-Maerz26.pdf (fetched 20 September 2026)
SAP, Service Layer APIs Change Log, 10.0 SP 2505 vs FP 2502 (StockTransfer object name), https://help.sap.com/doc/f73267664e244ea9a409cdfb4ea31728/10.0/en-US/10.0_SP2505_VS_FP2502.html (fetched 20 September 2026)
Morsa, J4S customer story, /customers/j4s; manufacturing ERP software, /guides/manufacturing-erp-software
Changelog
21 September 2026: first draft. Every SAP fact quoted from SAP documentation fetched on 20 September 2026; object names taken from the Service Layer guide.
