Skip to content
Home » Blog » Neptune DXP or native SAP Fiori: how to choose?

Neptune DXP or native SAP Fiori: how to choose?

In brief

  • Neptune DXP and SAP Fiori both produce SAPUI5 applications; the difference lies in tooling, data access and licensing.
  • Neptune speeds up development from ABAP, but adds a dependency on a third-party vendor.
  • Native Fiori relies on SAP standards (OData, RAP, CAP) and on the clean core approach recommended for S/4HANA.
  • Migration happens in batches: both technologies coexist in the launchpad during the transition.

Many SAP customers have modernised their screens with Neptune DXP, a low-code platform that produces Fiori-style applications. As S/4HANA and the clean core approach draw closer, one question keeps coming back: should you keep Neptune or move to native SAP Fiori applications? This comparison sets out the criteria to decide.

Two ways to build SAPUI5 applications

Neptune DXP, in its SAP edition, is installed as an ABAP add-on on your SAP system. Its App Designer lets you build applications by drag and drop on the SAPUI5 framework, and its data provider classes access SAP data directly, without going through the OData layer. The platform is designed offline first, with native mobile clients for Android and iOS.

SAP Fiori is the design system of the SAP user experience. Fiori applications are built with SAPUI5, either freestyle or with SAP Fiori elements, a template and metadata-based approach that greatly reduces user interface code. Data comes through OData services or APIs, exposed by ABAP RAP in S/4HANA or by CAP on SAP BTP.

The comparison at a glance

CriterionNeptune DXP (SAP Edition)Native SAP Fiori
Vendor and licensingNeptune Software product, with its own licence on top of SAP licencesStandard SAP technology, with no third-party vendor to license for the user interface
User interface technologySAPUI5, Fiori-style applicationsSAPUI5, Fiori elements or freestyle
Data accessNeptune ABAP classes, without an OData layerOData services and APIs (ABAP RAP, CAP)
DevelopmentLow-code in the App Designer, from ABAPSAP Fiori tools, SAP Business Application Studio or VS Code
Mobility and offlineBuilt in: designed offline first, Android and iOS clientsResponsive web; offline with SAP Mobile Services on SAP BTP
S/4HANA alignmentABAP add-on to install and maintain in every SAP systemSAP standard, in line with clean core rules
Available skillsNeptune profiles are scarcer on the marketLarge pool of SAPUI5 and Fiori developers
Long-term costNeptune licence, add-on maintenance and upgradesMaintenance of the application code only

When to keep Neptune DXP

  • Your application estate is recent, stable and maintained by a team trained on Neptune.
  • Your use cases rely heavily on offline work and field mobile devices.
  • You are staying on SAP ECC or on-premise S/4HANA, with no short-term cloud project.
  • The licence cost remains low compared with the productivity gains observed.

When to migrate to native Fiori

  • You are preparing S/4HANA, especially Private Cloud with RISE with SAP, and are aiming for a clean core.
  • You want to reduce the number of vendors and licences to manage.
  • Your applications are mostly display, entry or approval screens, which Fiori elements covers well.
  • You struggle to recruit or retain Neptune skills.
  • Maintaining the add-on slows down your SAP upgrades.

Migrating without disruption: a batch-by-batch approach

A successful migration is not done in one go. Neptune and Fiori coexist: Neptune applications can be embedded in the SAP Fiori launchpad, and vice versa, so you can switch application by application.

  1. Estate audit: inventory of applications, actual usage, criticality, dependencies and volumes.
  2. Mapping and scoping: choice between Fiori elements and freestyle SAPUI5, prioritisation and estimation by batch.
  3. Redevelopment: OData or RAP services, then a Fiori user interface as close as possible to business needs.
  4. Testing and cut-over: user testing, training and gradual go-live.

This is the approach of InRize, our solution for migrating from Neptune DXP to SAP Fiori. Each batch is validated with your teams before the next one.

Frequently asked questions

Is Neptune DXP a SAP Fiori application?

Not strictly speaking. Neptune produces SAPUI5 applications that follow Fiori design rules, but they rely on the Neptune Software platform and data provider classes. A native Fiori application uses standard SAP OData services or APIs and needs no third-party add-on.

Can we migrate only some of the applications?

Yes. Both technologies coexist in the SAP Fiori launchpad during the transition. We usually start with the most used or most expensive applications to maintain, then handle the rest in batches, with no service interruption for users.

How long does a migration from Neptune to Fiori take?

It depends on the number of applications and their complexity. An estate audit takes a few weeks; each migration batch then takes one to three months, testing included. Simple display applications, well served by Fiori elements, migrate faster than offline mobile applications.

Go further

Sources