Most businesses with an SAP ERP have some form of customer-facing portal. It might be SAP’s standard NetWeaver Business Client, a legacy portal bolted onto an older SAP release, or a basic web form that submits requests into SAP via email. In most cases, it was built years ago, looks dated, requires IT maintenance to change, and delivers a customer experience that the business is quietly embarrassed about.
The gap between what these legacy portals provide and what customers now expect — from consumer apps and B2C digital experiences — has widened to the point where it is a commercial problem. Customers who cannot self-serve escalate to your service team. Customers who find the portal confusing call your inside sales team instead of placing orders digitally. Customers who cannot get real-time information about their orders lose confidence in your operational reliability.
SAP BTP changes what is possible. A customer portal built on BTP — integrated natively with SAP ERP and SAP Service Cloud — can deliver a modern, real-time, personalized self-service experience that the legacy portal generation was technically incapable of providing. This blog explains what that looks like in practice, and what it took to build it.
Why Legacy ERP Portals Fall Short
The limitations of legacy SAP portals are not primarily about design or user experience — they are architectural. The portal technology that most companies are running was built for a different era of enterprise software, and its constraints are structural rather than cosmetic.
Real-time data is not available
Legacy portals typically query SAP data through batch processes or scheduled synchronization. A customer checking their order status in the morning sees data from the overnight batch run — not from this morning’s picking and packing activity. For customers who need real-time visibility into fulfillment, this latency is not acceptable. It generates service calls that a real-time portal would have prevented.
The user experience is SAP’s, not yours
Standard SAP portal interfaces expose SAP’s internal transaction model to end users — screens designed for trained SAP users, not customers. Customizing these interfaces requires ABAP development and carries all the upgrade risk of core modifications. The result is a portal that is either standard and unusable or customized and unmaintainable.
Mobile and modern device support is limited or absent
Legacy portal technologies were built for desktop browsers in a specific era of web standards. Responsive design, mobile-first interfaces, and modern browser capabilities are either unavailable or require significant additional development that the underlying portal architecture does not support well.
Every change requires IT involvement
Adding a new field, changing a label, adding a new section, updating the navigation — every change to a legacy portal requires a developer, a transport, and a deployment cycle. Business teams that want to evolve the portal experience to match changing customer needs are constrained by IT change management processes designed for ERP configuration, not digital experience iteration.
The commercial cost of a poor portal experience:
Every customer interaction that the portal fails to self-serve generates a service or sales team touchpoint. In businesses with large customer bases and high transaction volumes, the aggregate cost of these avoidable touchpoints — in headcount, in response time, in customer satisfaction — is material. The portal is not just a digital experience problem. It is an operational cost problem.
What a BTP-Built Customer Portal Can Actually Do
A customer portal built on SAP BTP using the Cloud Application Programming (CAP) model and SAP UI5 framework, integrated with S/4HANA through standard APIs and with SAP Service Cloud for service interactions, delivers capabilities that are architecturally impossible in the legacy portal generation.
| Capability | SAP Standard Portal / NetWeaver | Custom Portal on SAP BTP |
|---|---|---|
| Order placement | Form-based ordering with manual product lookup. No real-time pricing or availability. | Guided product search with real-time pricing from ERP pricing engine and live ATP inventory check at line level. |
| Order tracking | Batch-updated order status. Customers see yesterday’s data. | Real-time order status from S/4HANA — picking, packing, goods issue, shipment, delivery — updated as ERP events occur. |
| Invoice & account management | Limited invoice history. No self-service payment or dispute capability. | Full invoice history, account statement, payment status, and self-service dispute initiation — all pulling live from SAP FI. |
| Service requests | Email form submission. No case tracking or resolution visibility. | Integrated service request creation, real-time case status, agent communication, and resolution history via SAP Service Cloud. |
| Product catalog | Static catalog synchronized on a schedule. Does not reflect real-time availability. | Dynamic catalog from SAP material master with customer-specific pricing, availability, and product recommendations. |
| Mobile experience | Desktop-only or poorly adapted mobile experience. | Responsive, mobile-first design built on modern UI5 standards. Full functionality on any device. |
| Personalization | Generic experience for all users. No role or account-based customization. | Every change requires an ABAP developer and transport cycle. |
| Portal changes | Every change requires an ABAP developer and a transport cycle. | Role-based access, account-specific catalogs, and personalized dashboards based on purchase history and account profile. |
SNJYA: What ASAR Digital Built on SAP BTP
ASAR Digital designed and built SNJYA — a customer self-service portal deployed on SAP BTP and integrated with SAP ERP and SAP Service Cloud. SNJYA demonstrates what the BTP portal architecture delivers in a production environment, not just in concept.
What SNJYA enables customers to do
- Search and browse a live product catalog with real-time pricing and availability drawn directly from the SAP material master and pricing engine
- Place orders digitally with immediate ERP confirmation — no manual order entry, no processing delay
- Track orders and fulfillment in real time as S/4HANA processes each stage of the order lifecycle
- Create and track service requests integrated with SAP Service Cloud — with full case visibility and communication history
- Access account history, invoices, and account status without contacting the service team
How it was built
SNJYA was built using SAP’s Cloud Application Programming model on BTP — a structured development framework that enforces clean architecture patterns and generates OData services automatically from the data model. The frontend is built on SAP UI5 with a responsive design that works across desktop, tablet, and mobile.
All data access to SAP ERP is through published standard APIs — no direct database access, no ABAP modifications, no core changes. The portal is completely independent of the SAP ERP release cycle. ERP upgrades do not require portal changes. Portal updates do not require ERP transports.
The integration with SAP Service Cloud is handled through SAP Integration Suite on BTP — events and data flow between the portal, the ERP, and the service platform through managed integration flows rather than point-to-point connections.
What this architecture means for the business
SNJYA is not a demonstration or a prototype. It is a production portal serving real customers. Its architecture reflects the design principles that apply to any customer portal built on SAP BTP — and it is the reference point ASAR Digital uses when scoping customer portal engagements.
The key characteristic of this architecture is that the portal is a business capability, not an IT project. Business teams can define what the portal shows and how it behaves. IT manages the platform and the integration layer. The portal evolves at the speed of business requirements, not at the speed of ERP change management.
The architectural principle behind SNJYA:
SAP ERP is the system of record. BTP is the experience layer. Integration Suite is the connection between them.
None of these three layers modifies the others. Each evolves independently. The customer sees a unified, real-time experience. The SAP core remains clean and upgradeable.
The Business Case for a BTP Customer Portal
The investment case for a BTP-built customer portal is built on four measurable drivers — and most organizations underestimate how significant each one is until they measure their current state carefully.
Service team capacity reallocation. Every routine customer inquiry — order status, invoice copy, product availability — that a portal self-serves is a touchpoint removed from your service team’s queue. In businesses with high transaction volumes, this reallocation is substantial. Service teams freed from routine inquiry handling can focus on complex cases, escalations, and proactive customer engagement that genuinely requires human judgment.
Order accuracy improvement. Orders placed through a BTP portal connected to the SAP pricing engine and ATP inventory check are accurate at the moment of placement. The order correction rate — orders that require manual intervention after placement due to pricing errors, unavailable inventory, or catalog mismatches — drops significantly compared to manual ordering or legacy portal ordering.
Customer satisfaction and retention. The relationship between digital self-service quality and customer retention is direct and measurable. Customers who can manage their own account — orders, invoices, service requests — without friction are more satisfied and less likely to evaluate alternatives. The portal is not just a cost reduction tool. It is a retention investment.
Scalability without headcount. A well-designed self-service portal scales with transaction volume without proportional increases in service team headcount. As the business grows, the portal absorbs the volume increase that would otherwise require additional service capacity. This is the compounding return of portal investment — it gets more valuable as the business gets larger.
What It Takes to Build a Portal That Delivers
The gap between a portal that works technically and a portal that actually changes customer behavior is significant — and it is almost entirely an implementation discipline question, not a platform question.
Start with the customer journey, not the SAP data model. Portal design that starts from what SAP can expose produces a portal that mirrors SAP’s internal model — which customers do not understand. Portal design that starts from what a customer is trying to accomplish — check my order, pay my invoice, report a problem, find a product — produces a portal that customers actually use.
Invest in the integration layer before the UI layer. The most common cause of portal underperformance is unreliable data. Portals that show stale, inconsistent, or incorrect information train customers not to trust them — and customers who do not trust the portal call the service team anyway. The integration architecture needs to be solid before the UX design begins.
Design for adoption, not for go-live. A portal that goes live is not a portal that customers use. Customer onboarding, communication, incentive design, and ongoing feature development are the capabilities that drive adoption from go-live rates to habitual usage. These are business change management activities, not technical ones — and they need to be planned as part of the portal program, not added after launch.
The Bottom Line
The customer portal is the digital face of your commercial relationship. In an era where every customer’s baseline expectation is set by the best consumer digital experience they have encountered, a legacy ERP portal is not just a UX problem — it is a signal about how much the business values the customer’s time.
SAP BTP removes the architectural constraints that made modern portal experiences impossible on legacy SAP technology. The combination of BTP’s Cloud Application Programming model, SAP UI5, Integration Suite, and standard S/4HANA APIs enables a portal experience that is real-time, personalized, mobile-first, and operationally connected in ways that the previous generation of portal technology could not support.
SNJYA is ASAR Digital’s proof that this architecture delivers in production — not just in architecture diagrams. It is the reference point for every customer portal engagement we take on, and it reflects the design principles that separate portals customers use from portals customers avoid.
ASAR Digital’s portal practice:
We have designed and built production customer portals on SAP BTP — including SNJYA, a live portal integrated with SAP ERP and SAP Service Cloud. Our portal engagements start with the customer journey and the integration architecture before any UI work begins. If you are planning a customer portal initiative, talk to us before your architecture decisions get locked in.
Planning a customer or partner portal on SAP BTP?
ASAR Digital brings production portal experience to every engagement — from architecture design through customer adoption. Talk to our BTP team about your specific portal requirements before scope gets defined.