Every manufacturer running SAP Business One eventually asks the same question of any quality system they evaluate: how does it talk to SAP? The honest answers range from "it doesn't, you export a spreadsheet" to "through a middleware server you license separately" to "through a connector we wrote against your database that will break at the next upgrade." Synesis has implemented SAP Business One since 1994, so when we built Synesis QMS we built the SAP integration the way we would want it as an SAP partner: against the interfaces SAP ships and supports, with the connection mode as a setting rather than a project. This post explains the three ways the QMS connects to SAP Business One — the Service Layer, SAP HANA and Microsoft SQL Server — why the Service Layer is the one we recommend for new deployments, and what actually flows between the two systems once they are connected.
What the Service Layer Is, and Why SAP Recommends It
For most of Business One's life, the supported way to integrate was the DI API — a COM library installed on a Windows machine, versioned with the SAP client, and awkward to run from anything that was not a Windows desktop application. The Service Layer replaced that model. It is SAP Business One's own web service: a server component that exposes the same business objects the DI API did — Business Partners, Items, Purchase Orders, Goods Receipt POs, Deliveries, Production Orders, Returns, Batch Number Details and hundreds more — as REST resources using the OData protocol, over HTTPS on port 50000 by default. A client logs in with an SAP user and company database, receives a session, and then reads or writes objects with ordinary HTTP calls. The current /b1s/v2 endpoint speaks OData V4; the original /b1s/v1 is still there for older clients.
Three properties make it the right integration surface for a quality system. First, SAP validates every call: a Goods Receipt read through the Service Layer is the same document SAP shows its own users, and a write goes through the same business rules, authorizations and add-on hooks as a user typing in the client. Second, it is platform-independent: since Business One 10.0 the Service Layer is available for the Microsoft SQL Server version as well as the HANA version, so an integration written once works on either, on-premise or in SAP's cloud. Third, it is upgrade-proof in the way a database connection never is. Table names, columns and join logic are SAP's internals and can change; the Service Layer contract is what SAP commits to carrying forward. If you are reading about preparing for SAP Business One version 11, the Service Layer is the interface that survives the move.
Three Connection Modes, One Setting
In Synesis QMS the SAP connection lives in Administration under APIs, on the SAP Business One card. The Connection Mode selector offers three options, and the other fields on the card — server, port, username, password, database — mean what that mode needs them to mean:
The point of making this a setting is that nothing above it changes. The importers, the SAP data pages in the QMS, the inspection and supplier records that reference SAP documents — all of it sits on top of the mode you chose. A plant that starts on SQL Server and moves to HANA, or moves SAP to a hosting provider that exposes only the Service Layer, changes a dropdown and re-tests the connection. That is what "seamless" should mean in an integration: not that it is invisible, but that it does not have to be rebuilt when the landscape moves.
What Flows Between SAP Business One and the QMS
Nine SAP entity types import into the quality system, each with its own page where users can search, filter, export and AI-enrich the records. More important than the list is what each one is for in the QMS:
- Vendors and customers, with contacts. The supplier master behind supplier qualification, scorecards and SCARs is SAP's business partner list, not a re-typed copy. Complaints and RMAs reference the customer SAP invoices.
- Purchase orders and lines. Receiving inspection knows what was ordered, from whom, in what quantity. Maintenance purchase orders in the QMS Asset Management module reference the same suppliers.
- Goods receipt POs. The receipt is the trigger for incoming inspection. A failed inspection puts the receipt on quality hold, and the hold is visible to the ERP so the material is not paid for or consumed.
- Deliveries. Outbound deliveries trigger final inspection; pre-shipment verification is a checkpoint, not a memory.
- Production orders. In-process inspections and nonconformances link to the SAP production order and operation that produced the part.
- Batches and lots. Traceability forward from a raw-material lot to every customer that received product made from it, and backward from a complaint to the supplier lot — following the same batch numbers SAP tracks.
- Returns. Customer returns in SAP create RMA records in the QMS for inspection and disposition, and the disposition feeds the credit note or replacement order.
Why "native" matters more than "integrated"
Plenty of quality systems can be integrated with SAP Business One by a third party for a fee. A native integration means the QMS was designed knowing that the supplier, the purchase order and the batch would come from SAP — so the inspection form has a place for the goods receipt number, the supplier scorecard reads real purchase history, and the traceability report follows SAP's lot numbers rather than a parallel numbering scheme. It also means there is nobody between you and SAP: no middleware server to patch, no per-connector license, and no vendor to call when the connector breaks after an SAP upgrade.
Choosing a Mode: A Practical Guide
If SAP Business One is hosted by a partner or in SAP's cloud, the choice is made for you: hosting providers expose the Service Layer and, sensibly, do not expose the database. If SAP runs on-premise on HANA and you are loading years of history into the QMS on day one, a read-only HANA connection is the fastest path for that initial load, and you can switch to the Service Layer for ongoing sync afterwards. If SAP runs on-premise on SQL Server and your SAP administrator would rather grant a read-only SQL login than create an API user, the SQL Server mode respects that preference and needs no additional SAP component. For everything else — and for any plant that expects to upgrade SAP, move to HANA or move to the cloud within the life of the quality system — start on the Service Layer.
Whichever mode you choose, the security posture is the same: the QMS reads SAP through credentials your SAP administrator controls, the credentials are stored in the QMS's settings store rather than in code, and every import is logged in the QMS audit trail. Our guide to SAP Business One security best practices covers the SAP side of that arrangement.
Where This Fits in the Rest of the Quality System
SAP data is the foundation the other modules build on. Supplier and risk management score the vendors SAP pays. Inspections reference SAP receipts and production orders. The new Safety Data Sheets module refuses a purchase order for a chemical with no active SDS, and the parts ledger that feeds chemical inventory is stocked by SAP goods receipts. The ISO Coverage map shows suppliers under clause 8.4 and release of product under 8.6 with live counts — counts that are only meaningful because the records behind them are the ERP's records. For the full entity list and the connection-mode comparison, see the SAP Business One QMS Integration page.
Frequently Asked Questions
What is the SAP Business One Service Layer?
SAP Business One's web API: business objects exposed as REST resources using OData, over HTTPS on port 50000 by default, on both the HANA and SQL Server versions of Business One. It is the interface SAP recommends for new integrations.
Should a QMS connect through the Service Layer or directly to the database?
For most new deployments, the Service Layer — it enforces SAP's rules, survives upgrades and works with cloud hosting. A read-only HANA or SQL Server connection is still useful for large historical loads on-premise. Synesis QMS supports all three as a setting.
Does the Service Layer work with SAP Business One on SQL Server?
Yes. Since Business One 10.0 the Service Layer ships for the SQL Server version as well as HANA, so the integration is the same on either platform.
The Bottom Line
An SAP Business One integration is only as good as the interface it is built on and the assumptions the quality system makes about the data. Synesis QMS is built on the interfaces SAP supports — the Service Layer first, HANA and SQL Server where they fit — and it was designed from the start around the fact that your suppliers, orders, receipts and batches live in SAP. That is what an SAP Gold Partner's quality system should look like. If you run SAP Business One and are evaluating quality software, ask us for a demo connected to a Business One company database and watch a goods receipt become an inspection.
