SAP Fiori UI5 & CAPM on SAP BTP – Zero to Real Project- 2026

Explore SAP BTP's three-level architecture—global account, sub-accounts, and spaces—along with Cloud Foundry and Kyma environments, and learn deployment prerequisites and service entitlements.

Configure sub-accounts, destinations, and IAS trust within a SAP BTP global account; activate services and manage spaces and regions to deploy UFA and CAPM apps across dev, QA, and prod.

Explore how SAP BTP uses IaaS as the identity provider and XSUAA for app authentication, JWT token validation, and OpenID tokens for CAPM, Node.js, and OData apps.

Learn how to configure trust between IAS and XSUAA on SAP BTP, using IDP, roles, and XS QAA to control access for CAPM apps in a B2B SAP account.

Explore SAP Fiori architecture and app types, including transactional, analytical, and fact sheets, and learn how Fiori launchpad, UEFI, OData, Gateway, and CAPM fit into a unified launch environment.

Learn to consume OData services in SAPUI5 by wiring a table control with columns, items, and properties like id and title, and manage lifecycle events from onInit to onExit.

Master the four SAPUI5 data binding types—property, element, aggregation, and expression—and bind json models to controls, using setData and setModel to display employee names and countries.

Explore element and aggregation binding in SAPUI5, using form controls and tables, with property binding vs element binding, expression binding for conditional styling, and binding modes in JSON and OData.

Learn to implement routing and navigation in SAPUI5 apps by creating view2, wiring a button to navigate from view1 to view2, and configuring routes and targets in manifest.json.

Explore sapui5 app structure with component.js, manifest.json, and the controller, view, and the model layers, plus data from plain odata services.

Create a SAP Fiori UI5 app from a template, connect to Northwind v2 OData, and deploy on SAP BTP with Fiori Launchpad, configuring deployment and trust for build work zone.

Learn to build, test, and deploy a UI5 app to SAP Fiori on SAP BTP, configure cloud identity services, trust, IAS tenant, and publish to Launchpad as an MTAR-based tile.

deploy a SAP Fiori app to Launchpad by building the mta project, generating an mtar, and deploying via cloud foundry to SAP BTP, including login steps, spaces, and error checking.

Debug SAP Fiori apps in the browser using Chrome DevTools, breakpoints, and network tab to inspect UI elements and OData calls; explore project structure like web app folder, manifest.json, index.html.

Explore how to query the orders entity set, navigate to related order details, and use $expand with the OData model to fetch header and line items in SAP Fiori UI5.

Understand odata query options explained, including dollar expand, filter, select, and order by, with examples on products and order details and capm integration.

Explore the SAP CAPM basics, including CDS data modeling, Node.js runtime, service definitions and handlers, and how CAPM auto exposes OData v4 for cloud back-end apps.

Model a books entity in CAPM with id, title, author, price, published date, and availability, then expose an OData service via CDS for SAP BTP with test data.

Explore CAPM data modeling with CDS to define entities, keys, data types, associations, and compositions, master header-to-item relationships, and automatic UUID generation and OData navigation for backend design.

Create a composition between sales order header and items, link item details as navigation, and enable deep insert with auto header id and dependent item deletion.

explains header and item data modeling in capm through deep insert, creating sales orders and items, and compares composition versus association with cascading delete.

Create a CAPM project and apply the managed aspect to add auto generated IDs, created by and modified by fields, and leverage common aspects like language and code lists.

Learn how CAPM annotations empower data modeling in SAP Fiori, configuring selection fields, line items, and header information for sales order sets, with OData v4 generation.