SAP B1 manages your inventory, orders, and financials. WA.Expert puts those events on WhatsApp — instantly. This guide covers every technical approach: DI API, SAP B1 Service Layer, B1if middleware, and Boyum IT's B1UP. With working code examples from SAP's own documentation.
SAP Business One is deeply embedded in Indian manufacturing, distribution, and wholesale businesses. But SAP B1's built-in notification system is email-only. This guide shows you exactly how to bridge SAP B1 events — new sales orders, invoice approvals, delivery notes, payment applications — to WhatsApp messages via WA.Expert API. We cover three integration methods so you can choose the right one for your infrastructure.
| Integration approach | Complexity | Best for |
|---|---|---|
| SAP B1 Service Layer (REST API) | ⭐⭐ Medium — requires SAP HANA or 10.0+ | Best for modern SAP B1 deployments on HANA. Clean REST API, no SDK needed. |
| SAP B1 DI API (COM/SDK) | ⭐⭐⭐ Complex — requires Windows server, VB.NET or C# | Legacy deployments on SQL Server. Full object model access. |
| B1if / SAP Integration Framework | ⭐⭐ Medium — requires B1if license | Enterprise B1 setups. Visual workflow builder, no code for simple flows. |
| Boyum B1UP / Beas | ⭐ Easy — if Boyum IT is already installed | If your SAP B1 already has Boyum IT addons — quickest path. |
| Zapier/Make via Service Layer | ⭐ Easy — no server code | For non-developers. Poll Service Layer via Zapier/Make → WA.Expert. |
Service Layer is available on SAP B1 9.2+ with HANA or SQL Server. In SAP B1 Administration → System Initialization → General Settings → Services tab → Enable Service Layer. Default port: 50000 (HTTP) or 50001 (HTTPS).
POST to /b1s/v1/Login with your SAP B1 company database, username, and password. You receive a session cookie (B1SESSION) valid for 30 minutes. All subsequent API calls must include this cookie.
Create a scheduled SQL job or a SAP B1 Formatted Search (FMS) that fires when a document is added/updated. The script calls your middleware endpoint with the document details.
Your Node.js/Python middleware receives the SAP B1 event, fetches the customer's phone from Business Partner master data via Service Layer, then calls WA.Expert API to send the WhatsApp.
If real-time webhook is complex, a scheduled script polls the Service Layer every 5 minutes for new documents (filter by CreateDate = today, DocStatus = Open) and processes the queue.
Service Layer base URL format: https://[server]:[port]/b1s/v1. Default ports: 50000 (HTTP), 50001 (HTTPS). SSL certificate is self-signed by default — use verify=False in requests for internal networks.
Download SAP B1 SDK from SAP Support Portal (SAP Note 886895). Install on a Windows server that has network access to the SAP B1 application server. The DI API is a COM component — requires 32-bit .NET application.
In Visual Studio: Add Reference → COM → SAPbobsCOM. This gives you access to the Company object, Document objects (oOrders, oInvoices, oDeliveryNotes) and Business Partner objects.
Create a Company object, set ServerName, CompanyDB, UserName, Password, DbServerType, and call Connect(). Check return value — 0 means success.
Use the BusinessObjectsXML event or set up a scheduled Windows service that queries new documents since last run. Store the last processed DocEntry to avoid duplicates.
For each new document, use BusinessPartners.GetByKey(CardCode) to get the BP master. Access CardForeignName or the U_WhatsApp user-defined field if you've added one. Call WA.Expert REST API via HttpClient.
The SAP B1 DI API is a 32-bit COM object — your integration application must run as 32-bit (x86) on Windows. Add a custom User-Defined Field U_Mobile (Character, 15 chars) to Business Partner master for clean phone storage.
WA.Expert provides the API key, template management, and WhatsApp delivery. Your team handles the SAP B1 trigger logic using this guide.