Fiori & UI5 Modernisation

Assess a real UI5/Fiori estate, know when to rebuild with Fiori Elements vs keep freestyle, migrate OData V2 to V4 without the common breakage, and read a front-end readiness check with the same discipline as an ABAP one.

1. 1
   Lesson

   Your Fiori Apps Have a Technical Debt Problem Too

   Lesson 1 — Every migration project fixates on ABAP remediation and forgets the UI5 layer sitting on top of it. Deprecated libraries don't get security patches and won't render under the current theme — and that risk compounds exactly the way ABAP debt does. Here's what's actually at risk, and how to see it in your own estate.

2. 2
   Lesson

   OData V2 to V4: What Actually Changes

   Lesson 2 — 'OData V2 to V4' gets said like a version bump. It isn't one — the data-access API, the HTTP verbs, the date types, and the query syntax all change underneath your app. Here's what actually breaks, and what doesn't.

3. 3
   Lesson

   Fiori Elements vs Freestyle: Picking the Right Tool

   Lesson 3 — Once your OData is V4, the next real decision is what to build the UI in. Most teams pick by habit, not by heuristic. Here's how Fiori Elements actually works, the five official floorplans, and the one real, official link to Clean Core that isn't marketing.

4. 4
   Lesson

   Reading a UI5/Fiori Readiness Check

   Lesson 4 — You already know this pattern from the ABAP side: a readiness check scans against rules and classifies findings by severity. Here's what a UI5/Fiori check actually looks at, the real official tool behind it, and how to read the output the same disciplined way.

5. 5
   Lesson

   Capstone: Modernising One App, Start to Finish

   Lesson 5, the capstone — Four lessons, four separate skills: spotting the debt, understanding OData V2 to V4, choosing Fiori Elements vs freestyle, reading a readiness check. Here's how they combine into one real modernisation pass, start to finish.