DI server

E-invoicing in Germany: How to implement the obligation with SAP Business One

Of the DI server is a SOAP-based server component in the SAP Business One SDK, which the Data Interface API (DI API) which provides access over the network as a service. External applications call business objects such as sales order, invoice, or business partner via XML messages to a central Windows service, without needing to install the DI API on each clients a DI API installation is necessary.

Context

Technically, the DI Server bundles multiple simultaneous DI API sessions behind a thread pool architecture and handles login, company assignment, and transaction grouping. It is typically used for integration scenarios where an external application (webshop, third-party system, logistics middleware) needs to write or read large amounts of data to B1 in batches – for example, during the nightly import of orders or the generation of delivery notes. The call is made via a SOAP request with an object session ID, which was previously obtained. LoginEx was generated; the returned XML follows the DI API object model. For licensing reasons, the DI server requires its own B1i/integration- Licences activated via the Licence Server.

Demarcation

Unlike the local DI API, which runs as a COM component directly within the process of a Windows application, the DI Server operates remotely via SOAP and can therefore also be accessed by non-Windows clients – albeit with higher overhead per call. Compared to the Service Layer, the DI Server is the older technology: Service Layer v2 is recommended for new, REST/JSON-based integrations, while the DI Server primarily remains where existing interfaces with complex DI API transactions have already been implemented or where specific stored procedures and add-on objects are only accessible via the DI API.