Development
Learn SAPUI5 offline
Master SAPUI5 Development — covering MVC architecture, bindings, custom controls, manifest configuration, component.js, and OData CRUD.
- 34 lessons
- 15 chapters
- 5 levels
- ~6 h of study
- 170 quiz questions
- 102 interview questions

Syllabus
What you will learn in SAPUI5
01SAPUI5 Core Architecture
- SAPUI5 MVC Concept
- Core Bootstrapping & Resources Layout
02Views & Controllers
- XML Views Configuration
- Controller Lifecycle & Event Handlers
03Data Binding Principles
- One-Way, Two-Way, and One-Time Bindings
- Property & Element Binding Syntax
04Models in SAPUI5
- JSON & Resource Models
- OData Model V2/V4 Configuration
05SAPUI5 Controls
- Standard Control Library sap.m
- Layout Controls & Responsiveness
- Accessibility & Keyboard Support in Controls
06Fragments & Dialogs
- Reusable UI Fragments
- Dialogs & Popovers Control
07Routing & Navigation
- Router Configuration in manifest.json
- Dynamic Routing & Parameter Passing
08Expression Binding & Formatting
- Formatters & Expression Binding Syntax
- Custom Formatter Coding
09UI5 Tooling & Development
- Local Development with UI5 CLI
- Project Structuring & manifest.json
- TypeScript in SAPUI5 Projects
10Component-Based Architecture
- Component.js Layout
- Routing inside Component.js
11Custom Controls Development
- Creating Custom UI5 Controls
- Extending Standard UI5 Controls
12Connecting to OData CRUD
- Executing Create, Read, Update, Delete (CRUD)
- Batch Request Handling
- Message Handling & Validation
13Testing in SAPUI5
- Unit Testing with QUnit
- Integration Testing with OPA5
14Localization & Globalization
- i18n Properties File Management
- Handling Languages & Number Formatting
15Performance & Deployment
- UI5 Application Cache Buster
- Minification, Build, and ABAP Upload
- Deprecated APIs & Preparing for UI5 2.x
Free sample
Try a lesson: SAPUI5 MVC Concept
Build a small SAPUI5 screen from an XML view, a controller and a JSON model, and explain what each part of the MVC pattern is responsible for.
You will be able to
- Explain the responsibilities of the model, the view and the controller in a SAPUI5 app
- Write an XML view that binds a list to a JSON model and wires events to controller methods
- Write a controller with sap.ui.define, onInit and an event handler that changes model data
- Trace how a change in the model updates the view through data binding
Key concepts
- XML view
- A declarative view file that defines controls, their properties, bindings and event handlers. It is the recommended view type for new SAPUI5 development.
- Controller
- A JavaScript module extending sap.ui.core.mvc.Controller that holds lifecycle hooks such as onInit and the event handlers referenced in the view.
- JSONModel
- A client-side model that holds JavaScript object data and notifies bound controls when the data changes. Its default binding mode is two-way.
Real business example
A distributor's in-house team built a SAPUI5 app for sales clerks to flag urgent orders. The first version read the selected order from the table control, changed the cell text directly and sent the update with a separate AJAX call. When the team added a phone layout with a list instead of a table, flagging stopped working on phones and the two layouts often showed different statuses.
A senior developer refactored the app to follow MVC. Both layouts were bound to the same model, the press handler changed only the model through the item's binding context, and the save logic moved into a separate module called from the controller. From then on the table and the list always showed the same status, and adding a third layout for tablets needed only a new view, not new logic.
Quick quiz
In a SAPUI5 XML view, what does press=‘.onOrderPress’ mean?
Show answer
B. Call the onOrderPress method of the view's controller
The leading dot tells SAPUI5 to resolve the handler on the controller named in controllerName. Without the dot, older code could resolve global functions, which is exactly what modern apps avoid.
Interview question
Explain how MVC is implemented in SAPUI5.
Show model answer
The model holds the data. Common types are JSONModel for client data, the OData V2 and V4 models for back-end services and ResourceModel for i18n texts. The view, usually an XML view, declares controls and binds their properties and aggregations to model paths; it contains no business logic. The controller, a module defined with sap.ui.define and extending sap.ui.core.mvc.Controller, has lifecycle hooks like onInit and the event handlers referenced in the view with a leading dot. Data binding connects model and view, so the controller changes the model and the UI updates automatically. Shared models are declared in manifest.json and created by the component.
That was 1 of 34 lessons. Get the rest in the app.
T-codes
Key SAPUI5 T-codes
SAPUI5: common questions
How long does it take to learn SAPUI5?
The SAPUI5 module in Learn SAP has 34 lessons totalling about 6 hours of reading. At two or three lessons a day, most learners finish it in four to eight weeks, plus time for hands-on practice in a real system.
Can a beginner learn SAPUI5?
Yes. The module starts at beginner level and builds up over 5 levels (14 intermediate, 13 advanced, 7 beginner lessons). Each lesson explains the concept, shows a real business example and ends with a quiz.
Is the SAPUI5 course free?
The free version of Learn SAP includes the first half of the levels in every module, including SAPUI5. Premium unlocks every level, the Interview and Certification Centers and the full T-code and table libraries.
Does the SAPUI5 module work offline?
Yes. Every lesson, quiz and reference table is stored on your phone, so you can study without an internet connection.
Keep going
More SAP modules
Learn SAP is an independent educational app. It is not affiliated with, endorsed by or sponsored by SAP SE, and it is not official SAP training. SAP, S/4HANA, Fiori, ABAP and other SAP product names are trademarks or registered trademarks of SAP SE in Germany and other countries.