Yes. Business partners, items, sales and purchase documents and journal entries are read from SAP Business One each night, read-only wherever your setup allows, into a warehouse in your own cloud account. There they meet the CRM, the web shop and the rebate and target files, AI checks that each record finds its match, and margin shows after rebates with every company in the group under one set of report lines. The route into SAP Business One is confirmed in the audit with your partner.
Where SAP Business One's own reports stop
SAP Business One is built to run the operation, and its reporting serves the people who run it: queries built with its Query Generator, which only ever reads, Crystal Reports layouts and, on the version for SAP HANA, Interactive Analysis. For a question about orders, stock or the accounts of one company, that is usually the right place to look.
The questions a commercial director asks sit at the boundary. Where supplier rebates are agreed per item or per volume band and tracked in a workbook rather than in the system, the margin SAP Business One shows is the margin before them. The pipeline lives in a CRM, and the web shop knows which campaign brought a buyer in. None of that is in the ERP unless someone keys it in.
A group is a further step. Each company in SAP Business One has its own company database, or its own company schema on SAP HANA, with its own chart of accounts and its own codes, so a group view has to be assembled before anyone can read it.
What SAP Business One cannot tell you by itself
Every one of these needs the ERP and data held somewhere else. Which matter first in your business is settled in the audit.
Net margin after rebates
Sales and cost of sales from SAP Business One, less the rebates, recharges and discounts kept in workbooks, customer by customer and item by item.
Pipeline against purchasing
What the CRM expects to close, set against open purchase orders and stock in the ERP, so buying follows expected demand.
The group in one view
Every company database combined under shared report lines, while each managing director can still look at their own company alone.
Web orders to campaigns
Orders from the web shop joined to the campaign that brought them, wherever the order records it and the customer's consent allows.
Sales against target
Targets held in a file by salesperson or territory, compared overnight with what the ERP actually invoiced.
How SAP Business One is read, and how the night's data is checked
SAP provides its own interfaces for other systems. The Service Layer is a web interface to SAP Business One's business objects, built on HTTP and OData and installed on both the Microsoft SQL Server and the SAP HANA versions, and the DI API is its COM-based interface; both run on the same core business logic, which SAP calls the DI Core. SAP Business One sets each user's authorisations module by module, as full, read only or none, and the audit confirms with your partner which user the warehouse connects as and that it has no authorisation to add or change documents.
The warehouse never writes to SAP Business One. Reading the database itself for reporting is a different matter: it depends on how and where your system runs, on your own server or with one of SAP's hosting partners, and it is agreed with your partner during the audit rather than assumed. Every company database is read on its own, with its own codes, then combined in the warehouse; where the companies trade with each other, finance agrees how those sales and purchases are shown in the group figures.
AI then compares each night's data with the matching rules below: a CRM account without a BP code, a web shop product with no item number, a line in the rebate workbook that points at no item, a new G/L account not yet placed on a group line. Each is listed for its owner to put right at source, so the margin in the 110 Command Centre each morning is the margin after rebates the commercial director expects.
Loads run outside working hours, with the timing agreed with your partner, and reports read the warehouse rather than the system your team is working in. Should a load fail overnight, someone you have named is told first thing.
Where SAP Business One keeps what the reports need
The middle column is SAP Business One's own, from SAP's documentation. The right column is what the warehouse sets beside it.
| In SAP Business One | Added beside it in the warehouse | |
|---|---|---|
| Customers and suppliers | Business partners (customers, vendors and leads), each with a BP code | The same companies in the CRM and the web shop, matched to that code |
| Products | Items, each with an item number, one item group and stock per warehouse | Rebate terms and targets kept in workbooks |
| Trading | Sales orders, deliveries, invoices and credit notes | The channel or campaign that brought each web order |
| The ledger | Journal entries, tagged with cost centres in up to five dimensions where cost accounting is on | Report lines agreed once for the whole group |
| Plans | Budget scenarios set per G/L account | Sales targets by person or territory |
| The group | One company database, or schema, per company | All companies on shared report lines, and each one on its own too |
A trading group whose margin stopped before the rebates
A trading group in Malta imports technical products and sells them to trade customers through two companies, each in its own SAP Business One company database. The sales team works in a separate CRM, trade customers also order through a web shop, and supplier rebates are tracked in a workbook kept by one person in finance.
- Customer margin in the ERP ignores rebates, so the true figure is worked out a few customers at a time.
- The pipeline never meets the order book, so purchasing works from instinct and last year's pattern.
- The group's monthly figures are built by exporting from both companies and combining them in Excel.
- The rebate workbook has no second keeper.
- Both company databases, the CRM, the web shop and the rebate workbook are copied overnight into one warehouse in the group's own cloud account.
- Net margin after rebates sits on the commercial director's morning screen for every customer, current to yesterday.
- Buyers see the likely pipeline next to open purchase orders and stock before they place the next order.
- The rebate workbook has an owner, a fixed place and a check that flags items with no rebate terms.
Every order still runs through SAP Business One, with the partner's support unchanged. The questions that used to fall between systems now have one place to be answered.
Matching rules to agree before SAP Business One meets the rest
Business partner to CRM account
Storing the BP code on each CRM account gives the cleanest match. A company that both buys from you and sells to you is two business partners in SAP Business One, with two codes, so the rule says when they are one relationship.
Item number to the web shop and the rebate file
Each web shop product and each line of the rebate workbook points to one SAP Business One item, with bundles decided up front.
Each company's accounts to the group lines
Every company's chart of accounts is placed against the lines the group board reads; an account opened later waits on a list until finance places it.
Distribution rules
Where SAP Business One splits a posting across cost centres by a distribution rule, reports show the split as posted, and finance decides how the group view treats it.
Which date a figure uses
Posting date for the accounts, document date for operations, delivery date for stock. Each report names the one it uses.
What we do not do
- We do not sell, license, implement or support SAP Business One. Your SAP partner keeps doing that.
- We do not install add-ons, add user-defined fields or write anything into SAP Business One.
- We do not run your purchasing, stock or ledger. Those stay in the ERP, with your team.
- What we read is copied into a warehouse in your own cloud account.
How it works
- A strategy callThirty minutes with Glen, free, with no pitch deck. Bring the systems you run and the question none of them answers on its own. You leave knowing whether joining them is worth doing, and where to start.
- The data auditAbout three hours with your team, mapping where each figure comes from, which system holds it and which steps are done by hand. The audit confirms how each system can be read, and it ends with a quote.
- The buildThree to four weeks from an accepted quote to a live dashboard. Implementation is the first month. Your team agrees the definitions with us; we do the building.
- The fractional teamAn ongoing senior team keeps the loads running, follows changes made to your systems and connects the next source when the business needs it.
Glen Sultana founded 110 Analytics after a career built where the numbers move daily. Our people have run analytics for tier-one companies, S&P 500 firms and high-growth technology businesses. Glen is the person on the first call, and he runs every data audit himself.
- Built in your environment, under your account
- Every connection approved by you first
- Based in Malta
Straight answers
Does SAP Business One stay as it is?
Yes. It stays your ERP and keeps running orders, stock and the accounts. Each night a copy of what the reports need is read out of it and combined with your other systems.
Will this affect our SAP Business One partner or licence?
Your partner's support stays where it is, and nothing in the system is changed. Any dedicated user the connection needs, and any licence that user requires, is named in the audit before the quote, so your partner can agree it first.
How do you connect to SAP Business One?
Through an interface SAP provides, usually the Service Layer, with authorisations your partner sets, or through another route your partner agrees for your installation. The audit confirms which before anything is quoted.
Our partner already builds reports for us. Why add a warehouse?
Keep those reports; they serve the operation. A warehouse is for the questions that need SAP Business One together with your CRM, web shop or workbooks, and it keeps month-end positions, such as stock and debtors, as they stood on the day.
We run several companies in SAP Business One. Can you combine them?
Yes. Each company database arrives in the warehouse as its own source, and the group is assembled from them along lines your finance lead signs off. Access by role can limit each managing director to their own company, while the board sees all of them on one screen.
Will the overnight loads slow SAP Business One down?
They run outside working hours, only read, and their timing is agreed with your partner. During the day, reports query the warehouse rather than the ERP.
What does it cost?
The build is quoted when the data audit ends, based mainly on the number of sources beside SAP Business One and the matching they need.
A few SAP Business One terms, plainly
- Business partner
- SAP Business One's one record type for customers, vendors and leads, each identified by a BP code. A lead that becomes a customer keeps its record.
- Company database
- Where one company's data is held in SAP Business One; on SAP HANA it is a company schema. Some groups instead run several branches inside one company, with the Multiple Branches feature.
- Service Layer
- SAP Business One's web interface for other systems, built on HTTP and OData, which works with the system's business objects.
- Rebate
- Money a supplier pays back after the sale, usually against volumes bought. It changes true margin, yet it often sits outside the ERP.
Where the product facts come from
Every product fact on this page comes from the vendor's own documentation, read on 22 October 2026. Vendors change their products, so the audit checks the version you run.
- SAP Help: Query Generator
- SAP Help: Interactive Analysis
- SAP Help: Choose Company window (company databases)
- SAP Help: working with multiple branches
- SAP Help: adding new business partners
- SAP Help: SDK, Business Partners table (BP code, customer, vendor, lead)
- SAP Help: item master data, general area
- SAP Help: inventory in warehouse report (stock per warehouse)
- SAP Help: General Settings, Cost Accounting tab (up to five dimensions)
- SAP Help: working with distribution rules
- SAP Help: Budget Scenarios setup window
- SAP Help: Authorisations window (full, read only, none)
- SAP Help: Working with SAP Business One Service Layer
- SAP Help: SAP Business One SDK, Data Interface API
- SAP Help: Administrator's Guide, installing the Service Layer (Microsoft SQL Server)
- SAP Help: Administrator's Guide for SAP HANA, installing the Service Layer
- SAP Help: SAP Business One Cloud Administrator's Guide, introduction (hosting partners)
