SAP Meets the Modern Web

SAP has a reputation problem. It's powerful, battle-tested, and genuinely excellent at what it does — but the developer experience is decades behind. Here's what bridging it with a Next.js frontend actually looks like.

The gap is real

SAP's UI technologies — BSP, WebDynpro, Fiori — were built in different eras with different constraints. They work. They're not enjoyable. More importantly, they make it genuinely hard to build the kind of fluid, data-dense interfaces that modern enterprise users now expect after years of using consumer software.

The bridge pattern

The approach that worked was treating SAP as a pure data source via OData/REST APIs and building everything visual in Next.js. SAP handles the heavy lifting it's designed for — transactional integrity, authorization, workflow — and the frontend handles everything users actually see and touch.

The hard parts

Authentication is the first wall. SAP's auth model (SSO, certificates, SAML) doesn't map cleanly onto JWT-based web auth. We ended up building a thin .NET middleware layer that translates between them.

Data shapes are the second. SAP data comes back in formats shaped by ABAP conventions from the 1990s. CamelCase keys, nested structures, date formats that require parsing. A transformation layer is non-negotiable.

What it looks like at the end

When it works, it's genuinely impressive. Full SAP transactional power, live data, but a UI that feels like a modern product. The users don't know or care what's running underneath — which is exactly right.