SAP Business One is a capable ERP with a structural cost problem — every user who needs access needs a named licence. This is the pattern we use to put a fast, role-controlled web portal over SAP B1: full module access in the browser, live data through the DI API, and licence overhead cut for everyone doing routine work.
SAP Business One is a capable ERP with a structural cost problem: every user who needs access needs a named licence. This is the architecture pattern Axlume uses to put a fast, role-controlled web portal over SAP B1 — centralising every core module (Business Partners, Sales, Purchasing, Inventory, Financials) behind one browser interface, with live data through the DI API and licence overhead cut for everyone doing routine work.
It’s drawn from a delivered engagement; the client remains confidential. What’s shown here is the pattern itself — the way we structure a portal layer over SAP so it stays fast, maintainable and cheap to run.
The standard desktop client carries a licence problem: every user who needs access requires a named seat. For a growing organisation with cross-functional teams — finance, sales, purchasing, warehouse — those licence costs compound fast.
Worse, most of those users only need to read data or run a routine task. They were paying full-seat prices to sit in a heavy desktop client, while managers had no clean web view and reporting stayed manual.
The brief in plain terms: give every role the SAP data it needs, in the browser, without a per-seat licence for each of them.
Map who actually needs which modules, and what “access” really means per role — so the portal replaces seats where it can and defers to SAP where it must.
A clean Presentation / Business Logic / Data Access split over the DI API — so the portal scales, stays maintainable, and isolates the SAP integration from the UI.
Wire every core module — Business Partners, Sales, Purchasing, Inventory, Financials — through the DI API with real-time, two-way synchronisation.
SQL-level optimisation, server-side pagination and tight transaction scoping so the portal is faster than the desktop client on the workflows it covers.
Role-based access with permission tiers, so each role sees exactly the modules and actions it should — and nothing else.
One web interface across all five core SAP B1 modules — the whole ERP surface a routine user needs, without opening the desktop client.
Live, two-way synchronisation with SAP through the DI API — the portal reads and writes the same records the desktop client does, in real time.
Role-specific dashboards with filtering and export — the reporting the desktop client made painful, surfaced as a first-class view.
Four permission tiers, so a warehouse user and a finance lead see completely different portals built from the same system.
Indexing, server-side pagination and transaction handling — the difference between a portal that feels slower than SAP and one that feels faster.
Presentation, business logic and data access as separate concerns — so the SAP integration can change without touching the UI, and the whole thing stays maintainable.
SAP Business One stays the system of record. The portal sits in front of it: the browser talks to an ASP.NET MVC layer, which talks to a business-logic layer, which talks to SAP through the DI API. Reads and writes flow both ways in real time, so nothing forks away from SAP.
The stack is deliberately conventional — the value is in how the layers are structured and tuned, not in exotic technology.
| Frontend | ASP.NET MVC · Razor Views · Bootstrap |
| Backend | C# · .NET Framework |
| ERP Integration | SAP Business One DI API |
| Database | Microsoft SQL Server |
| Architecture | Layered — Presentation / Business Logic / Data Access |
| Access | Role-Based Access Control (RBAC) |
| Performance | SQL optimisation · server-side pagination · transaction handling |
What this pattern delivers:
Drawn from a delivered engagement; the client and commercial figures are confidential under NDA. We can walk a qualified prospect through the detail directly.
The SAP Business One DI API is not designed for high-frequency, high-volume web traffic. Point a busy portal at it naively and poorly-scoped calls create bottlenecks that make the web experience slower than the desktop client — which defeats the entire point.
The fix is three things working together: SQL-level query optimisation before data ever reaches the DI API layer, tight transaction scoping so connections don’t stay open under load, and server-side pagination to cap the data volume per request. Done properly, the portal outperforms the desktop client for the workflows it covers.
That’s the whole reason this is a reference architecture and not just “a web front-end for SAP”: the pattern is the performance discipline, not the screens.
You’ve seen our standard of engineering. Now, let’s build yours. From high-impact websites to complex enterprise applications, we specialize in transforming ambitious ideas into elite-grade digital reality. Whatever the platform, we bring the precision your vision demands.