Loading
Loading
Integrations
Z-SYSTEM works with SAP Business One over SAP’s supported integration surface. Every request travels from the browser into our server-side layer first. The browser never talks to SAP directly, and SAP Business One is never exposed to the public internet.
Architecture
These six steps are the only route data takes. There is no shortcut, no direct link from the user’s screen, and every step leaves a record you can review later.
A member of staff opens a screen scoped to their role — approving a sales order, checking stock — without opening the SAP Business One Client.
The browser interface collects the input, validates it on the spot, and turns it into a request signed with that user’s session.
Our server-side layer authenticates the user, checks their role permissions, revalidates every field, and writes an audit record before the request goes any further.
The component that translates a Z-SYSTEM request into the shape SAP Business One expects. It queues work, paces the calls, and keeps connection credentials server-side only.
SAP’s standard entry point into the system. SAP’s own business rules and authorisation checks still apply in full at this layer.
Your company database remains the single source of truth. A document created through Z-SYSTEM is the same document your finance team sees in SAP.
The user’s browser never connects to SAP Business One directly. All connection credentials are stored and used server-side only. This design reduces day-to-day dependence on the SAP Business One Client, and your use of SAP Business One and any integration remains subject to your organisation’s licence agreement.
Connector profiles
No two SAP Business One estates look the same, so environment settings live in profiles. Moving between environments is a configuration change, not an architecture change.
For organisations running SAP Business One on SAP HANA, whether on their own hardware or in a private cloud.
For organisations running SAP Business One on Microsoft SQL Server, still the most common setup among mid-market companies.
An option for organisations that do not want the Service Layer accepting external requests directly and prefer an extra layer of control.
The profile, the supported versions and the deployment shape are agreed together during the technical survey for each organisation. Your use of SAP Business One and any integration remains subject to your organisation’s licence agreement.
Reliability
An integration is judged on the bad days, not the good ones. These mechanisms exist so documents are not lost, duplicates are not created, and your IT team can find the cause quickly. Results depend on your processes, existing systems and the scope of each deployment.
Work that arrives at the same moment is queued rather than fired all at once, so a heavy invoicing run or month-end close does not slow everyone else down.
Transient failures are retried with a widening gap between attempts, instead of hammering an endpoint that is already under strain.
Every call has a defined ceiling. Past it, the request is cut and the result reported, so nobody sits watching a frozen screen wondering what happened.
Sales orders, deliveries and invoices carry an idempotency key. A double-click or a dropped connection will not produce a second document.
Call volume can be capped per interval so the load Z-SYSTEM places on your SAP environment stays within what that environment is sized for.
Connectivity is polled on a schedule. When an endpoint stops responding, the operations team knows before the first user picks up the phone.
Administrators can run a connection test from the settings screen and see whether the problem sits with the network, the certificate, or the service account’s permissions.
Errors returned by the target system are mapped to plain language for the user, with a reference code your IT team can trace back to the original response.
Each outbound request records who acted, when, against which document, and what came back — enough to answer an auditor without a forensic exercise.
The profile structure already anticipates organisations running several company databases. What is enabled in each phase is agreed before installation.
Data scope
This table lists the SAP Business One objects that come up most often in projects, so process owners and IT can picture the scope from the first conversation.
| Business area | Representative SAP Business One objects | Direction |
|---|---|---|
| Customers and suppliers | Business Partners, Contact Persons | Read and write |
| Item master data | Items, Item Groups, Price Lists | Read |
| Sales | Sales Quotations, Sales Orders | Read and write |
| Outbound shipments | Deliveries, Returns | Read and write |
| Accounts receivable | A/R Invoices, A/R Credit Memos | Read and write |
| Purchasing | Purchase Requests, Purchase Orders | Read and write |
| Goods receipt | Goods Receipt PO, Goods Returns | Read and write |
| Warehouse transfers | Inventory Transfer Requests, Inventory Transfers | Read and write |
| Stock adjustments | Inventory Postings, Goods Issue, Goods Receipt | Read and write |
| Service | Service Calls, Service Contracts | Read and write |
| Reporting views | Business Partner Balances, Warehouse Stock Views | Read |
The exact object set is agreed per deployment. It depends on the permissions granted to the service account, the permissions held by each user role, and your system version and customisations. Treat this table as a planning aid, not a list that is switched on automatically.
What you need
Have these eight items ready and the setup phase gets considerably shorter. Our team can walk the readiness check with your IT team before the project formally starts.
The address and port that Z-SYSTEM servers will call, confirmed as live and serving requests.
A dedicated account for the integration, separate from any employee login, holding only the permissions the agreed scope needs.
Connectivity from the Z-SYSTEM servers to your SAP environment — typically a private network link or firewall rules limited to approved source addresses.
A certificate on the endpoint issued by a trusted authority, with a named owner responsible for renewing it before it lapses.
Confirmation of which company database the connection targets. Where several exist, agree the order in which each is brought online.
Somewhere to validate processes and train users, so people can post practice documents without touching live data.
Confirmation from whoever manages your agreements that your use of SAP Business One and this integration remains subject to, and covered by, your organisation’s licence agreement.
One person who can reach system details and make network decisions. It is the single biggest factor in how quickly questions get answered during setup.
How Z-SYSTEM connects to SAP Business One