Reference · built on requestConnectorERP & finance

SAP Business One

Business partners, sales and purchase documents, inventory, and journal entries from SAP Business One through Service Layer.

Request accessPricing ↗

About

SAP Business One is SAP's ERP for small and midsize companies. Its Service Layer is an application server built on Apache HTTP Server that exposes the same business objects as the DI API over OData, with OData Version 4 the primary protocol since FP 2405. Entities cover business partners, items, warehouses, sales and purchase documents, payments, and journal entries.

An operator on Fibric signs in to a company database, reads open orders, deliveries, invoices, and stock by warehouse, and proposes the actions SAP exposes on those documents, such as closing or cancelling an order, for your approval. A receipt records what changed, why, and the way back.

This is a reference listing. It documents what Fibric would read from SAP Business One and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • BusinessPartners: customers, vendors, and leads, with their Activities
  • Orders, DeliveryNotes, Invoices, and CreditNotes, each with DocumentLines
  • PurchaseOrders, PurchaseQuotations, and PurchaseReturns
  • Items, Warehouses, StockTransfers, InventoryGenEntries, and PickLists
  • IncomingPayments and JournalEntries
  • ApprovalRequests, and document change history through ChangeLogsService_GetChangeLog
  • Cross-entity reads with $crossjoin and row-level queries through QueryService_PostQuery

Proposed actions

  • Target capability: propose Close, Cancel, or Reopen on an order through Orders(id)/Close, Orders(id)/Cancel, and Orders(id)/Reopen
  • Target capability: propose a new DeliveryNotes or Invoices document with POST
  • Target capability: propose a PATCH to a BusinessPartners record or a document field
  • Target capability: propose closing a pick list through PickListsService_Close

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Close orders that will never ship

    Read open Orders whose lines are fully delivered or dead and propose Orders(id)/Close with the reason attached.

    With Order Risk, Cancellation Window

  • Reorder before the warehouse runs dry

    Compare Items stock by warehouse against demand in open Orders and draft PurchaseOrders for your buyer to approve.

    With Reorder Point, Purchase Order Draft

  • Chase invoices with no payment

    Match Invoices to IncomingPayments and propose the next reminder for each open balance.

    With Dunning Cadence, Cash Application

Requirements

  • SAP Business One with Service Layer installed and reachable over HTTPS; SAP's examples use port 50000
  • A Business One user and the company database name (CompanyDB) for the Login call
  • Network reach to the Service Layer load balancer; SAP recommends several nodes behind it for availability
Authentication
A POST to /b1s/v2/Login with CompanyDB, UserName, and Password; the B1SESSION cookie carries the session, and SAML 2.0 single sign-on through SLD is available on the SAP HANA version.

Limits

  • A session expires after 30 minutes without a request (SessionTimeout in b1s.conf), so the connector signs in again
  • The default page size is 20; odata.maxpagesize in the Prefer header or PageSize in b1s.conf raises it
  • OData batch rollback and user transactions spanning requests are not supported
  • New user-defined objects, fields, and tables stay invisible until Service Layer restarts

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SAP Business One ↗

Questions and answers

Which OData version does Service Layer use?
OData Version 4 is the primary protocol as of SAP Business One FP 2405. OData Version 3 is deprecated but still served for backward compatibility. SAP's current reference documents Version 4 only.
How does a client authenticate?
It posts CompanyDB, UserName, and Password to /b1s/v2/Login. The response sets B1SESSION and ROUTEID cookies. B1SESSION must accompany every later call; ROUTEID keeps a session pinned to one node behind the load balancer.
Can a client run raw SQL through Service Layer?
No. The RecordSet business object is not supported. Cross-entity reads use $crossjoin or QueryService_PostQuery, and change history comes from ChangeLogsService.
Ask about SAP Business One

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SAP Business One through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy