Skip to main content
Eva can read SAP Business One data after the connection and its permissions have been checked. SAP remains in control of that data.

Requirements

  • A SAP Business One Service Layer address that Eva can reach over HTTPS, and your company database name.
  • A dedicated SAP user for Eva with read access to items, price lists, warehouses, business partners, sales orders, deliveries, and invoices.
  • Owner or admin access to the Eva workspace. Ask your SAP administrator for the details and confirm the certificate fingerprint through a separate channel.

What syncs and what does not

If SAP does not answer a live query, Eva does not use old catalog figures to give a price or stock amount.

Connect

1

Open SAP Business One

In Eva, go to Settings → Integrations and open SAP Business One.
2

Enter the four details

Fill in Service Layer URL, Company database, User, and Password with the details from your SAP administrator.
3

Create the connection

Select Connect. The Certificate section shows the server address, validity, and Fingerprint (SPKI).
4

Confirm the certificate

Ask your SAP administrator to confirm the fingerprint through a separate channel. Only then select Accept certificate.
5

Check access

Select Test connection. Review Access and its counts before using the data.
6

Give the agent access

In the agent’s Knowledge, add the SAP connection as a catalog source. In its Behavior, say which price list and warehouse to use.

Test and check the result

Test connection checks sign-in and shows how many items, business partners, sales orders, deliveries, and invoices the user can read. It creates no SAP documents. A successful test shows that Eva signed in; it does not prove the user can see every record. Compare the Access counts with what the administrator sees in SAP. A lower count can mean partial permissions. In What Eva uses, the catalog shows the agent, product count, and last read. If the first read is incomplete, Eva does not publish partial products.

Notifications

If the certificate you accepted changes, Eva pauses reads and notifies the owner inside Eva. Ask your SAP administrator to confirm the new fingerprint before selecting Accept the new certificate. Eva sends no sales order or invoice reminders through this connection.

Disconnect

In Settings → Integrations → SAP Business One, select Disconnect. Eva stops reading SAP. Data already present in Eva conversation history remains; a disconnected connection cannot authorize new reads.

If you see an error

Privacy

Eva stores the user and password encrypted. SAP session cookies are not stored in the connection configuration. Eva copies only the fields needed to search items into the catalog; it reads prices, stock, business partners, and documents without copying them into that catalog.

Limits

The item catalog updates once a day; Eva reads prices and stock live when answering. Availability depends on the Service Layer, its permissions, and HTTPS access. Eva does not provide a fixed outbound IP address for SAP allowlisting. This version does not write data to SAP.