Insights

abap2UI5 is a framework for building UI5 apps purely in ABAP: one class is one app. These 42 short essays explain how it works and why, one idea each. Some take on an everyday problem, others step back to the idea behind it: what happens when the ABAP server sends the screen instead of only the data.

New here? Start with#5 Hello World: A Classrun for the Browser, #6 UI5 Over-the-Wire: The Server Sends the View, #7 One Click, One Request and #17 The Client API: What the Client Can Do.

When the screen is decided

  1. UI5 Freestylebuild timea file in a frontend project
  2. RAP / Fiori Elementsactivation timeUI annotations on CDS
  3. abap2UI5request timea string from an ABAP class
Three ways to build a UI5 screen, by the moment after which its definition can no longer change.

Part 1 · Foundations

A whole app on one page first, then the three things it is built on: data whose type is only known at runtime, an app that is one class, and every UI5 control without a layer in between.

  1. #1The Cost of a Screen: A Whole App in One Classa whole application as one class, and what has to exist beside it
  2. #2Runtime-Typed Tables: Somewhere on the Way to UI5, We Lost RTTSa table whose structure is only known at runtime, drawn in UI5
  3. #3One Class, No Programming Modelevery API the system has, from BAPI to EML, behind one unchanged UI class
  4. #4Every UI5 Control, No Annotation in Betweenthe vocabulary is the UI5 control library, all of it
  5. #5Hello World: A Classrun for the Browserthe smallest app: one interface, one method, and it runs

Part 2 · How It Works

The mechanism under the app, one piece per article. Read this part from start to end if you want to know why something works before you use it.

  1. #6UI5 Over-the-Wire: The Server Sends the Viewevery request answered with two strings
  2. #7One Click, One RequestPBO, PAI, and the dispatch in main( )
  3. #8One Frontend for Every App: The Frontend Knows Nothingone shell for every app, and why it never needs a redeploy
  4. #9One Handler for Every Appno service per screen, and what the handler leaves to the apps
  5. #10Only the Changed Partthe view stays, the model updates
  6. #11A New Instance on Every Requestserialized state, and what that asks of the class
  7. #12Swapping the View at Runtimea different control, chosen in an IF
  8. #13Data Binding: Where the Selection Screen Wentthe variable and the field are one declaration again
  9. #14The View Builder: Four Verbs, Every Controlwhy the view builder knows no controls
  10. #15Where Your Own JavaScript Goesthree declared seams, no plugin system
  11. #16No Build, No Deploy, No Cachechange, activate, refresh — and where a BSP still enters

Part 3 · A Working Day

What an ABAP developer needs in the first week, and what each classic habit becomes: the client API, navigation, the URL, F4, messages, the LUW, locks, the long-running report, authorizations, the launchpad tile.

  1. #17The Client API: What the Client Can Dothe whole API an app calls, in one table
  2. #18Navigation: CALL SCREEN, LEAVE SCREENthe app stack, sub-apps and popups
  3. #19URL, Reload and Back: Where the URL WentF5, the back button and the bookmark
  4. #20Value Help: Where F4 Wentvalue help in three sizes
  5. #21Messages and Errors: MESSAGE Still Worksmessages, exceptions, translation
  6. #22Where the LUW Endsa rollback around main( ), and the commit that is yours
  7. #23The Lock Is Gone by the Next Clickenqueue in a stateless world
  8. #24Nothing Runs Between Two Clicksthe long report, the busy indicator, the timer and the job
  9. #25Who May Start Which Appone ICF node, authorization, CSRF, the CSP
  10. #26100 Rows, Four Hours, One Requestthe three numbers behind performance
  11. #27ABAP Unit for a Screentesting the class, linting the view
  12. #28When One Class Is Not Enoughthe four ways to split a larger app
  13. #29A Tile Like Any Other: The Fiori Launchpadinto the Fiori Launchpad

Part 4 · Where It Belongs in the Landscape

Releases, clean core, deployment shapes, and the technical criteria that decide between abap2UI5, RAP and UI5 Freestyle for a given screen.

  1. #30From ITS to abap2UI5twenty-seven years in one line
  2. #31One Codebase, 7.02 to ABAP Cloudwhy the release barely matters
  3. #32Cloud-Ready Is a Property of Your Appdecided in the SELECT
  4. #33When the API Is Not Releasedthe clean core levels, and the wrapper
  5. #34On-Stack or Side-by-Sidetwo places to run, one class
  6. #35One App, Many Systemsseveral S/4 systems behind one app, and the boundary the app draws
  7. #36RAP or abap2UI5?behavior against screen, and EML from an abap2UI5 app
  8. #37UI5 Freestyle or abap2UI5?the four cases where the browser has to be smart

Part 5 · Running It

What an architect asks before an installation goes productive: the threat model, where UI5 comes from, the sizing, the upgrade.

  1. #38What the Client Can Sendthe class, the draft id, the event, every bound value — and what is checked
  2. #39Where UI5 Comes Fromthe CDN, the system's own UI5, the launchpad's — one string in the exit class
  3. #40How Many Users: Sizing an Installationwork processes, draft rows, no server affinity, what the monitor measures
  4. #41Upgrading the Frameworkrelease tags, the stable contract, the frozen package, pull, pin, roll back

Part 6 · Afterword

One consequence that was not planned: why AI agents handle these apps well.

  1. #42Why AI Agents Handle abap2UI5 Apps Wellwhy one class in one language suits an agent