SAPUI5

An SAPUI5 app is a set of files that the browser loads and runs. The main building blocks are:

1. Component — the app's entry point, which the SAP Fiori Launchpad or another container instantiates.
2. App descriptor (manifest.json) — declares data sources, models, routing, dependencies and navigation inbounds.
3. Views — usually XML, declaring which controls appear on screen, mostly from libraries such as sap.m.
4. Controllers — JavaScript or TypeScript code that reacts to user events.
5. Models — OData V2 or V4 models for backend data, JSON models for local state, resource models for translated texts.

Data binding connects controls to model properties, so a field updates when the data changes without hand-written plumbing. Themes such as SAP Horizon style every control consistently. SAPUI5 is therefore an application framework, not just a widget library: it prescribes how an app is structured, loaded and connected to data.

SAPUI5 runs in the UI applications layer, inside the user's browser. Above it, the SAP Fiori Launchpad or SAP Build Work Zone provides the shell, navigation and roles. Below it, OData services built with the ABAP RESTful application programming model, SAP Gateway or other backends deliver the data and enforce business rules.

Both main development approaches produce SAPUI5 apps. SAP Fiori elements generates the UI at runtime from OData annotations, using SAPUI5 controls underneath. A freestyle SAPUI5 app is written by hand with the same controls. The SAP Fiori Design Guidelines describe the intended user experience; SAPUI5 is one of the technologies that implements it in code. SAPUI5 is the common runtime underneath both SAP Fiori elements apps and freestyle apps, whichever way the app was built.

The main difference is the license. OpenUI5 is open source under the Apache 2.0 license and developed publicly on GitHub. SAPUI5 is delivered as part of SAP products such as SAP BTP and the ABAP platform.

The core runtime and the most used control libraries, for example sap.m, sap.ui.layout and sap.ui.unified, are identical in both. SAPUI5 adds further libraries: charts (sap.viz, sap.chart, sap.suite.ui.microchart), smart controls that configure themselves from OData annotations (sap.ui.comp), SAP Fiori elements (sap.fe) and the launchpad shell (sap.ushell). The list changes per release; in SAPUI5 1.154, no library ships only with OpenUI5. Technical names and APIs are shared, so code written for OpenUI5 runs on SAPUI5 when the runtime is switched. Version numbers can differ at patch level, because the SAPUI5 distribution bundles an OpenUI5 core.

For teams building on SAP products, SAPUI5 is the relevant distribution; OpenUI5 matters for open-source tooling and for apps that must run without an SAP license.

The answer depends on the deployment option:

• SAP BTP: SAP describes SAP BTP as the primary channel for SAPUI5. Several versions are available on the content delivery network, and each app chooses its version when it bootstraps. New minor versions appear roughly monthly, and versions are removed from the network at the latest one year after their release; check the version overview for the status of long-term maintenance versions.
• On-premise and Private Edition: SAPUI5 ships with the UI technology component of the ABAP platform. Each SAP Fiori front-end server release brings one long-term maintenance version; for example, front-end server 2023 corresponds to SAPUI5 1.120 and front-end server 2025 to SAPUI5 1.136.
• SAP S/4HANA Cloud Public Edition: SAPUI5 comes with the product, and its maintenance follows the product's documentation rather than the SAP BTP strategy.

Decision criterion: develop and test against the lowest SAPUI5 version among the systems the app will run on. The technical information dialog (Ctrl+Alt+Shift+P) shows the version actually loaded. Knowing the SAPUI5 version is the first step in every compatibility question.

1. Building against a newer version than production runs. A feature available on SAP BTP may not exist in the on-premise front-end server. Check the version overview before using a new control or API.
2. Relying on deprecated APIs. Synchronous loading and other legacy patterns still work but are deprecated; SAP's modernization guide lists their replacements, and the UI5 linter detects them.
3. Pinning SAP BTP apps and forgetting them. An app tied to a version that leaves the content delivery network stops loading. Schedule version upgrades like any other maintenance task.
4. Hard-coding texts. Labels belong in resource models, otherwise translation becomes a code change.
5. Writing everything freestyle by habit. SAP's own guidance recommends SAP Fiori elements wherever a floorplan fits and freestyle code where it does not.

Most SAPUI5 problems are lifecycle problems — versions, deprecations and ownership — rather than coding problems.