SAP Business One

Setup:

1. Identify your Service Layer host (on HANA it usually runs on the database server; SQL Server installs and hosting partners run it on a separate host). Default HTTPS port is 50000.
2. Create or pick a B1 user that has API access for the company database you want to expose. A user without write authorizations is a safe start: every tool except b1_create_order only reads.
3. Find the CompanyDB name in Choose Company dialog of the B1 client (looks like SBODEMOGB).
4. Set the five env vars below. The adapter logs in once per session (~25 min TTL) and re-uses the B1SESSION cookie.

OData: this adapter targets the v2 / OData v4 Service Layer endpoint at /b1s/v2/. Older /b1s/v1/ (OData v3) deployments are not covered — upgrade to FP 2405+ first.

Filtering: use standard OData $filter syntax, e.g. CardCode eq 'C20000' or DocDate ge '2026-01-01'.

Paging: the Service Layer returns 20 rows per call unless the client asks for more, whatever $top says. Every list tool asks for pages of up to 100 rows (Prefer: odata.maxpagesize=100); when a response carries @odata.nextLink, call the same tool again with skip raised by the rows already read. Use select to keep wide documents (journal entries with their lines, invoices) small.

Keys and enums: documents are read by DocEntry (internal key), not by DocNum (the number printed on the document). Booleans are tYES / tNO, document status is bost_Open / bost_Close, and OriginalJournal tells what created a journal entry (ttJournalEntry for manual entries, ttAPInvoice, ttARInvoice, ttVendorPayment, ttReceipt…).

Finance: A/P invoices, A/P and A/R credit memos, outgoing and incoming payments, journal entries, the chart of accounts and bank statements each have a list tool. Bank reconciliations are not a list in the Service Layer: b1_list_external_reconciliations calls its reconciliation service (a POST that only reads) and returns account and number pairs for b1_get_external_reconciliation; open items are the documents whose PaidToDate is below DocTotal.

Permissions: a 403 with SAP error -6006 ("Modifying this object is not permitted for current user") means the login works but the B1 user lacks the authorization for that object. Grant it in Administration → System Initialization → Authorizations, or keep the user read-only on purpose.

Self-host caveat: Business One is on-premise. The Service Layer is reachable from inside the customer network. To use the AnythingMCP Cloud, expose Service Layer via a reverse proxy + TLS cert; otherwise self-host the adapter on the same network.