abap2UI5

Appearance

Technology Overview ​

From ITS to abap2UI5

This page traces the evolution of web development in the ABAP ecosystem — from early server-rendered interfaces like ITS and Web Dynpro to modern client-side SPAs with UI5 Freestyle and RAP — and ends by comparing them to abap2UI5.

Internet Transaction Server ​

Bringing SAP GUI to the Web (2000+) (SAP)

The Internet Transaction Server (ITS) was SAP's first step toward bringing SAP GUI screens (Dynpro) to the web. ITS Mobile converts classic Dynpro screens into basic HTML pages.

  • Pure Server-Side Rendering (SSR): the server builds HTML for every interaction
  • Optimized for basic mobile devices (e.g., warehouse scanners)
  • Reuses existing Dynpro logic for web and mobile use cases
  • Still used today for specific legacy use cases

Business Server Pages ​

Embedded HTML in ABAP (2001+) (SAP)

Business Server Pages (BSP) introduced HTML-based web development inside the ABAP stack.

  • Developers write HTML and JavaScript, with embedded ABAP for logic
  • Also server-side rendering, but with more control over layout and styling
  • Used widely in early CRM and SRM web applications
  • Technically obsolete, but still present in some legacy environments

Web Dynpro ​

Structured Web Applications (2003+) (SAP)

Web Dynpro introduced a component-based UI framework for web applications.

  • Developers create UI definitions in ABAP (Views, Context, Controllers)
  • Still Server-Side Rendering: UI is built on the server, rendered as HTML in the browser
  • Fits transactional business applications
  • More structured and modular than ITS, but limited for modern UX

UI5 Freestyle ​

Full Client-Side SPAs (2010+) (SAP)

With the rise of smartphones and richer web experiences, SAP introduced UI5 Freestyle.

  • Based on JavaScript, XML Views, and UI5 Controls
  • Follows a Single-Page Application (SPA) architecture
  • Full control over frontend behavior and look and feel
  • Enables highly customized, interactive applications
  • Needs dedicated frontend expertise

RAP / Fiori Elements ​

Standardized Backend-Driven SPA (2019+) (SAP)

The RESTful Application Programming Model (RAP) and Fiori Elements standardize application development.

  • Developers define CDS annotations in ABAP that describe UI behavior
  • The UI5 Fiori Elements runtime in the browser renders the app as a SPA
  • Simplifies UI development with predefined floorplans and templates
  • Still SPA complexity (OData metadata handling, UI5 runtime in browser)

abap2UI5 ​

UI5 Over-the-Wire (2023+) (Open Source)

abap2UI5 brings the simplicity of Over-the-Wire to SAP UI5 development.

  • The ABAP backend defines UI5 XML Views and JSON ViewModels
  • A static UI5 frontend dynamically renders these definitions
  • No custom JavaScript needed
  • Combines backend-driven development with UI5 flexibility
  • Lines up with SAP's cloud strategy