# SAP Business One

Mercura connects directly to your **SAP Business One** through its
**Service Layer**: articles with prices, customers and contact persons come in
from SAP Business One, and quotations and sales orders go back. Like the other
chapters under *Ready-made connections*, this is not an endpoint of the
Mercura API. Mercura calls your Service Layer, and SAP Business One never
calls Mercura.
There is nothing to install in SAP Business One. You need a **technical user**
and a Service Layer that Mercura can reach. Everything else is configured in
Mercura under **Settings → Integrations → SAP Business One**. Each data flow
has its own switch there, so you can start with one part and add more later.
![Data flows between SAP Business One and Mercura: articles with prices, customers and contact persons flow from SAP Business One to Mercura; quotations and sales orders flow from Mercura to SAP Business One, and the document number comes back.](https://prod-euapi.mercura.ai/api/public/v1/docs-assets/sap-business-one-data-flows.svg)
| Data flow | Direction | Trigger | Result |
|  --- | --- | --- | --- |
| Articles and prices | SAP Business One → Mercura | Schedule: hourly or nightly | Items become Mercura articles, with the price of one price list as list price |
| Customers | SAP Business One → Mercura | Schedule: hourly or nightly | Business partners of type customer become Mercura customers |
| Contact persons | SAP Business One → Mercura | Schedule: hourly or nightly | The customers' active contact persons become Mercura contacts |
| Quotations | Mercura → SAP Business One | Tender completed in Mercura | Quotation in SAP Business One; its number is stored in Mercura |
| Orders | Mercura → SAP Business One | Order completed in Mercura | Sales order in SAP Business One; its number is stored in Mercura |

**Which system leads which data.** SAP Business One leads articles, prices,
customers and contact persons. Mercura reads them and does not change them.
The positions of a request, the article matching and the order capture happen
in Mercura. The quotation or order Mercura creates is an ordinary document in
SAP Business One; further processing stays there.

 - [How the connection works](https://docs.mercura.ai/openapi/sap-business-one/how-the-connection-works.md): ## How the connection works - **Service Layer.** Mercura uses SAP Business One's standard REST interface, the Service Layer (OData v3 at `/b1s/v1` or OData v4 at `/b1s/v2`). - **Authentication.** Merc
 - [Setup in SAP Business One](https://docs.mercura.ai/openapi/sap-business-one/setup-in-sap-business-one.md): ## Setup in SAP Business One 1. **Create a technical user** for Mercura, e.g. "MERCURA", in the company database Mercura should work with. A dedicated user keeps Mercura's changes apart in the change
 - [Authorisations of the technical user](https://docs.mercura.ai/openapi/sap-business-one/authorisations-of-the-technical-user.md): ### Authorisations of the technical user | Data flow | Authorisations | | --- | --- | | Articles and prices | Read on Item Master Data, Item Groups and Price Lists | | Customers and contact persons |
 - [Connecting in Mercura](https://docs.mercura.ai/openapi/sap-business-one/connecting-in-mercura.md): ## Connecting in Mercura In Mercura, open **Settings → Integrations → SAP Business One**. Under **Access**, enter the **Service Layer URL** (ending in `/b1s/v1` or `/b1s/v2`), the **company database**
 - [Configuring the data flows](https://docs.mercura.ai/openapi/sap-business-one/configuring-the-data-flows.md): ## Configuring the data flows Under **Which data is exchanged** you switch each data flow on separately. Changes apply after **Save**.
 - [Articles and prices](https://docs.mercura.ai/openapi/sap-business-one/articles-and-prices.md): ### Articles and prices Items become Mercura articles, keyed by the item code (`ItemCode`): | Mercura | SAP Business One | | --- | --- | | Article number | `ItemCode` | | Name | `ItemName` | | Unit |
 - [Customers and contact persons](https://docs.mercura.ai/openapi/sap-business-one/customers-and-contact-persons.md): ### Customers and contact persons Business partners of type customer become Mercura customers, keyed by the customer code (`CardCode`), with name, e-mail, VAT ID, phone, postal code, city and country.
 - [Documents](https://docs.mercura.ai/openapi/sap-business-one/documents.md): ### Documents **Quotations:** when a tender is completed in Mercura, Mercura creates a quotation in SAP Business One. **Orders:** when an order is completed in Mercura, Mercura creates a sales order.
 - [Activity and errors](https://docs.mercura.ai/openapi/sap-business-one/activity-and-errors.md): ## Activity and errors **Activity** at the top of the page opens the connection with every pull and every document sent: when it ran, how many records were read and which were rejected, and the answer
 - [Notes and limits](https://docs.mercura.ai/openapi/sap-business-one/notes-and-limits.md): ## Notes and limits - **One source per data.** Articles and customers that Mercura takes from SAP Business One should not also reach Mercura by another import; otherwise they overwrite each other. - *
 - [Getting started](https://docs.mercura.ai/openapi/sap-business-one/getting-started.md): ## Getting started 1. Create the technical user in a test company database. 2. Enter the access in your Mercura test organisation and save to test the connection. 3. Switch on the pulls you need and c