SAP UI5 and Fiori on BTP: The Experience Layer of S/4HANA

SAPUI5 is still how most humans touch S/4HANA. Fiori elements, freestyle UI5, OData V2 and V4, launchpad service on BTP, spaces and pages, business roles, catalogs, and the fight with custom CSS that will not survive a theme upgrade. Clean core means the UI moves to BTP. A CodePen UI5 developer is not a launchpad developer. SR Soft staffs the latter.

The unique challenge is not “pretty tiles.” It is $select and $expand instead of SELECT *, batch instead of chatty chatter, draft handling that RAP already gave you, authorization that matches the DCL, and accessibility a Fortune 500 brand will sign. Freestyle is earned when Fiori elements cannot express the process. Most teams freestyle first and pay later.

Every S/4 cell we run includes a UI5 lead. Future: Joule-aware floors, UI5 web components, CAP/RAP backends. We are hiring that mix.

Elements, freestyle, and the launchpad as an operating system

Fiori elements exist so you do not invent a table, a filter bar, and a draft every time RAP already gave you the floor. Freestyle is for the process elements cannot express — a planning board, a mass-change that is actually a process, a plant-floor display. Most teams freestyle because someone likes control. Then the theme upgrade breaks 40 apps and accessibility fails a brand review. We require a written reason for freestyle. Spaces and pages map to jobs, not modules. A tile dump is not a workplace.

OData chat is the silent killer. $select, $expand, batch, and a performance budget the PO owns. Authorization must match DCL. A UI that shows buttons the user cannot execute is a finding. We staff a UI5 lead on every S/4 cell so this is not an afterthought in SIT.