SAP Business One — Service Layer / DI API
OData Service Layer (HANA or SQL) with DI API as fallback, per company database
A dedicated service user is created in your SAP Business One environment and BizBloqs authenticates against the Service Layer with it. Documents are read and posted as proper SAP objects — goods receipt PO, delivery, inventory counting, inventory posting — so the audit trail inside SAP stays intact and journal entries are created by SAP itself. Where a document type is not exposed by the Service Layer in your version, the DI API is used for that object. The connection is bound to a company database; a customer with several company databases gets a connection per database.
What you need
- SAP Business One 9.x or newer with the Service Layer reachable (HANA or SQL Server)
- A licensed service user with rights on the relevant company database
- Outbound HTTPS from the SAP environment to BizBloqs, or a published endpoint if SAP is hosted
- Agreement on warehouse codes and bin location management inside SAP






















