SAP Connector — Azuvio on top of SAP Business One or S/4HANA, without touching accounting
Native bidirectional integration between the Azuvio Smart Operations Layer and SAP (Business One via DI API + Service Layer, S/4HANA via OData + IDoc). Sync partners, items, orders, invoices, goods receipts and payments in <2 min. SAP remains the master for accounting, ledger and tax reporting. Azuvio adds OMS, WMS, EDI, CRM, SFA and a B2B Portal on top — the operations SAP does poorly or not at all.
Why SAP alone is no longer enough in 2026
Your SAP is excellent at what it was built for: accounting, general ledger, monthly close, multi-company consolidation, tax reporting, financial control, planning. Anyone who uses it well will tell you the same thing — once parameterized, SAP becomes the financial heart of the business, and you don't want to touch it.
The problem shows up on the operations side: you run an online store with 5,000 SKUs, sell on eMAG/Amazon, ship to 8 countries via 4 couriers, run EDI with Auchan/Lidl/Carrefour, manage field reps in 12 counties writing orders on mobile, operate a warehouse with 3 zones and mandatory FEFO per lot, and serve 200+ B2B customers who want a self-service ordering portal. Standard SAP handles none of these elegantly. ABAP customizations cost months and tens of thousands of euros per release. Third-party SAP Marketplace modules carry enterprise pricing and uneven quality.
Azuvio fills exactly that gap: it runs on top of SAP as a Smart Operations Layer, with a native connector that uses official APIs (DI API + Service Layer for Business One, OData + IDoc + RFC for S/4HANA). All day-to-day operations — multi-channel orders, warehouse picking, retailer EDI, lifecycle CRM, field reps, B2B portal — happen inside Azuvio, and SAP receives exactly what it needs: partners, items, orders, invoices, goods receipts and payments, in clean, reconcilable form. Your SAP accountant changes nothing. You add new capabilities in weeks, not quarters.
What the Azuvio SAP connector does
8 native capabilities, included in the standard product — not separate modules, not extra consulting.
- Bidirectional partner sync — Business Partners (customers + suppliers) flow between SAP and Azuvio CRM with automatic matching on tax ID. A new lead converted in Azuvio becomes a BP in SAP with an ANAF-validated tax ID; a BP edited in SAP appears in Azuvio in <2 min.
- Items + price lists sync — Item Master Data (SKU, attributes, UoM, standard prices, per-customer Price Lists) published from SAP to Azuvio. Or the reverse — new products from eCom/OMS written back to SAP with auto-generated item codes.
- Orders: Azuvio → SAP — Sales Orders captured via OMS (EDI, marketplace, eCom, B2B portal, SFA, phone) are automatically written into SAP with the right BP, item lines, the correct customer price list and delivery terms. Status returned on changes.
- Invoices: Azuvio ↔ SAP — An AR Invoice issued in Azuvio (at WMS dispatch) is written into SAP for accounting. Or the reverse — invoices issued in SAP synced to Azuvio for tracking. e-Factura/SDI/Peppol delivered from whichever side suits your flow.
- Synced master stock — Master stock stays where it already lives (SAP MM or Azuvio WMS — your choice). Sync at configurable intervals (5–15 min) or event-driven. Buffer rules, multi-warehouse allocations, FBE/FBA support.
- Goods receipts & inbound — Goods Receipt PO auto-created in SAP when goods are received in Azuvio WMS (with photos, quantity discrepancies, lot/expiry). PO → GR → Invoice reconciliation runs automatically.
- Incoming payments + auto-matching — Payments from POS, eCom and Azuvio AR collection are written into SAP as Incoming Payments with automatic invoice ↔ payment matching. Your accountant's bank reconciliation gets 2x faster.
- Multi-company + multi-currency — Supports scenarios with several SAP Companies (subsidiaries, divisions, countries) — Azuvio maps BP/item/order to the correct Company and respects different currencies and chart of accounts.
Native Azuvio connector vs custom ABAP vs third-party middleware
Same SAP integration, three different approaches — wildly different cost, time and risk.
| Aspect | Native Azuvio connector | ABAP development / SAP extension | Third-party middleware (iPaaS, MuleSoft, Boomi) |
|---|
| Time to first flow in production | 2–6 weeks | 3–9 months | 6–12 weeks |
| Implementation cost | Included in Azuvio subscription (small scoping) | Tens of thousands € (ABAP consultants) | Medium-high (iPaaS licenses + integrator) |
| Maintenance after SAP updates | Included — we update the connector | Redone each time (cost) | Paid separately per mapping |
| Operations covered (OMS, EDI, WMS, SFA, B2B) | All, native | Only if you build them yourself in ABAP | Data transport only, no UI/UX |
| Client-side skill required | None — you use Azuvio UI | In-house or contracted ABAP team | In-house iPaaS team |
| Risk to existing SAP | Zero — only official APIs used | High — you modify the master system | Low-medium (depends on mapping) |
| Multi-company SAP support | Native | Re-done per Company | Mapped per flow |
| Marketplace, retailer EDI, eCom, SFA connectors | Included (ships with Azuvio) | Built separately from scratch | Built separately on iPaaS |
Implementing the Azuvio SAP connector — 6 steps
Typically 4–6 weeks for SAP Business One, 6–10 weeks for S/4HANA, depending on catalog complexity and number of flows.
- Kick-off + SAP audit — SAP version (B1 / S/4HANA / ECC), patch level, active modules (FI, MM, SD, CO), BP count, item count, multi-company, existing customizations. We agree which Azuvio modules connect in phase one (typically: partners + items + orders).
- Technical access + credentials — For Business One: DI API/Service Layer account with rights on BP + Items + Sales Order + AR Invoice. For S/4HANA: OData/IDoc communication user + RFC if needed. Connectivity test, latency measurement, rate-limiting agreement.
- BP + Items + chart of accounts mapping — Field mapping Azuvio ↔ SAP: tax ID, internal BP code, VAT payer flag, payment terms, Price Lists. Same for Items: code, name, UoM, group, prices. Chart of accounts mapping for payments/invoices. Documentation delivered to the client.
- Initial history sync + dry-run — Import historical BPs + Items + Price Lists from SAP into Azuvio. Dry-run for orders: we push 10 test orders from Azuvio into SAP and validate. Any missing mapping is fixed before pilot.
- 2-week parallel pilot — Two weeks running Azuvio and SAP in parallel on a limited segment (one channel, one category, one warehouse). Your team validates daily. Tuning. Training for the operations team on Azuvio.
- Go-live + first-week monitoring — Connector enabled across all flows. Proactive monitoring for 7 days (alert on any error > 0). Daily checkpoint with your team. At the end, full handover to Azuvio support with an agreed SLA.
Real problems solved by the Azuvio SAP connector
- Problem: Orders from the online store are entered manually in SAP by an operator (2–3 minutes/order × 200 orders/day = 8 person-hours/day wasted, plus typing errors). Azuvio + SAP solution: The order enters Azuvio OMS from eCom and is written into SAP with the correct BP, item lines and Price List price. The operator becomes an exception handler, not a data entry clerk.
- Problem: EDI with Auchan/Lidl/Carrefour runs on legacy middleware that doesn't connect natively to SAP — orders arrive on spreadsheets, DESADV/INVOIC done manually. Azuvio + SAP solution: Azuvio EDIconnect (live since 2014, certified with major RO retailers) receives ORDERS, writes them into SAP as Sales Orders, generates DESADV on dispatch and INVOIC on invoicing. Zero manual steps.
- Problem: FMCG sales reps capture orders on paper or WhatsApp; data entry into SAP happens next day with 24h lag, no per-customer price and no real stock. Azuvio + SAP solution: Azuvio SFA mobile (offline-first) with bidirectional SAP sync: the rep sees live stock, the correct per-customer Price List price, and writes the order directly into SAP at the end of the visit. Zero lag.
- Problem: Warehouse goods receipt happens on paper; the SAP NIR is entered 1–2 days later with mismatches between physical and book stock. Azuvio + SAP solution: Azuvio WMS on handhelds: receipt via barcode, photo on discrepancies, lot/expiry captured. Goods Receipt PO generated automatically in SAP within seconds, with the photo attached as evidence.
- Problem: B2B customers call 20 times a day asking for stock, price, invoice and order status — sales reps answer manually from SAP, burning time on repetitive calls. Azuvio + SAP solution: Azuvio B2B Portal connects to SAP: the customer sees live stock, their own price (from the SAP Price List), orders, invoices, payments and recurring orders. Inbound calls drop 60–80% in 90 days.
What Azuvio on top of SAP looks like in practice
Built by Azuvio (2014–present, team with 200+ implementations across distribution, retail and manufacturing). The scenarios below are representative — typical combinations of the challenges we solve.
- Mid-market FMCG distributor on SAP Business One — Used SAP B1 for accounting + inventory, but orders from 80 field reps were transcribed manually the next day. Added Azuvio SFA + OMS + SAP B1 connector: reps write orders on mobile, they hit SAP instantly with the right Price List price. Representative result: order lag from 24h to 0, zero transcription errors.
- Industrial manufacturer on S/4HANA, 4 subsidiaries — S/4HANA for multi-company consolidation, but retailer EDI and B2B distributor portal were on spreadsheets + email. Added Azuvio EDI + B2B Portal + OData S/4HANA connector: retailer ORDERS and distributor B2B orders flow into S/4HANA on the right Company, in the right currency.
- Omnichannel retailer on SAP B1 + 12 stores — SAP B1 for centralized inventory, but eCom/marketplace on a separate system with no stock sync. Frequent oversell, chaotic returns. Added Azuvio OMS + WMS + SAP connector: stock unified live across stores + eCom + marketplaces, returns in one workflow.
Technical & operational details for the SAP connector
Supported SAP versions
SAP Business One 9.3 SP01 and above (HANA and SQL), all localizations (RO, BG, HU, GR, DE etc.). SAP S/4HANA Cloud and On-Premise (1909 and later). SAP ECC 6.0 EHP6+ supported via RFC + IDoc for projects transitioning to S/4. Older versions — analyzed at kick-off.
APIs and protocols used
For Business One: DI API (in-process DLL) or Service Layer (REST/HTTPS) — chosen based on environment and volume. For S/4HANA: OData v2/v4 for standard transactions, IDoc for classic B2B flows (ORDERS, INVOIC, DESADV), RFC for custom cases. For ECC: BAPI/RFC + IDoc. Custom webhook scheduler for event-driven push where SAP doesn't support it natively.
Security and compliance
VPN or IPsec connection into the client's SAP landscape. Dedicated SAP user with minimal rights (principle of least privilege) on the required objects. Full logging of every API call (who, what, when, response) for audit. GDPR-compliant — BP data stays in the chosen datacenter (AWS Europe or on-premise at the client). Contabo backups, Prometheus + Grafana monitoring.
Performance and rate limiting
Configurable per client based on SAP load. Default: 5 calls/sec for Business One, 20 calls/sec for S/4HANA. Exponential retry on transient errors, dead-letter queue on permanent errors with alert to the support team. Event-driven webhook where SAP supports it, polling with configurable interval where it doesn't.
Typical flows and volumes
A mid-sized SAP B1 client runs roughly 5,000–15,000 messages/day through the connector (BP updates, item sync, sales orders, invoices, payments). An enterprise S/4HANA client can reach 100,000+ messages/day at peak. Azuvio's k8s pod-per-tenant architecture supports horizontal scaling without limits.
Gradual migration vs big-bang
Standard recommendation: do not enable all flows at once. Start with BP + Items sync (low risk, read-only), then add orders (write to SAP) after a 2-week pilot, then invoices and payments. Drastically reduces risk. Big-bang only when the client has an external constraint (new channel launch on a fixed date).
Frequently asked questions
- Does the SAP connector affect my existing SAP performance?
- No. We only use official SAP APIs (DI API / Service Layer / OData / IDoc / RFC) with rate limiting calibrated to your ERP's load. At kick-off we measure latency and volume, then configure the connector to stay under the agreed threshold. For high-traffic SAP we use event-driven architecture (webhook) instead of intensive polling.
- How long does the SAP connector implementation take?
- SAP Business One: 4–6 weeks from kick-off to first flow in production. SAP S/4HANA: 6–10 weeks. Includes audit, BP+Items+chart of accounts mapping, history sync, a 2-week parallel pilot and go-live with 7-day monitoring. Multi-company or ABAP customizations add 1–3 weeks.
- Who issues e-invoicing (e-Factura/SDI/Peppol) — Azuvio or SAP?
- You decide with us based on your flow. Case 1 (most common): Azuvio generates the invoice at dispatch and sends it directly to the national e-invoicing system, then passes the invoice to SAP for accounting evidence only. Case 2: SAP generates the invoice and sends it to the e-invoicing system (if you have a SAP module for it), and Azuvio only receives the confirmation for tracking. Both work.
- Does the connector support multiple SAP Companies?
- Yes, natively. We map each SAP Company (subsidiary, division, country) to an Azuvio entity, with separate currencies, charts of accounts and Price Lists. Orders, invoices and payments hit the correct Company without manual intervention. Useful for groups with presence across multiple SE European countries.
- What happens if SAP has downtime or an update?
- The Azuvio connector queues all operations during SAP downtime, with no data loss. When SAP comes back, operations are resent in chronological order. For planned updates you receive advance notice and we can switch temporarily to ‘degraded’ mode (orders captured in Azuvio, written in batch after the update). Zero impact on the end customer.
- Does the connector also work with on-premise SAP in our own datacenter?
- Yes. The connector supports both SAP Cloud and on-premise. For on-premise we set up a site-to-site VPN or IPsec into your SAP landscape. For clients who also need Azuvio on-premise, we support that deployment too (default is SaaS on AWS Europe, but on-premise is available).
- How do you handle existing ABAP customizations in our SAP?
- Customizations exposing custom BAPI/RFC are integrated directly via RFC. Customizations modifying standard structures are explicitly mapped in the audit phase (kick-off). Customizations that would block standard SAP APIs are flagged and we propose alternatives (typically: workflow in Azuvio rather than modifying SAP).
- Can we start with just partner/item sync and add the rest later?
- Yes, that's the standard recommended approach. We start read-only (BP + Items + Price Lists) — zero risk on SAP. After 2 stable weeks we add write (Sales Orders, then Invoices, then Payments). Modular. You pay only for what you enable. The rest stays available on the platform for when you want to expand.
- What limitations does the connector have vs custom SAP implementation?
- The connector standardizes on the major SAP objects (BP, Items, Sales Order, AR Invoice, Goods Receipt, Incoming Payment, Price Lists). For exotic objects (complex Production Orders, custom MRP runs, full SAP CRM flows) we move into individual scoping. We cover 95% of distribution, retail and mid-market manufacturing needs.
- How much does the SAP connector cost separately from Azuvio?
- The SAP connector is included in the standard Azuvio subscription (from €12/user/month) — you don't pay separately. The incremental cost is only the implementation scoping (4–10 consultant days), presented as a fixed quote after the audit, with no surprises. No per-API-call license, no variable usage fee, no annual maintenance fee.
Related pages
Explore how Azuvio connects to the rest of your ecosystem and which modules run on top of SAP.
Want to see Azuvio on top of your SAP?
30-min live demo with a consultant who has done SAP integrations before. We show exactly what data flows, how, and how fast. No slides — only the product.