SAP Fiori examples
These Fiori examples show the modern SAP user experience in practice, using standard apps, and the building blocks of a custom app (UI5, OData, CDS).
The Fiori example shows the modern stack: a CDS view entity over I_PurchaseOrderItemAPI01 exposed with @OData.publish, then a Fiori Elements list report and object page generated from its annotations with little hand-coding. Most needs are met by standard apps found in the Fiori apps reference library; go Fiori Elements on CDS before freestyle UI5.
- Watch out: Freestyle builds where Fiori Elements fits.
- Worked examples: using standard fiori apps, a custom app, conceptually, what it teaches.
Using standard Fiori apps
Most needs are met by standard apps, for example "Manage Purchase Orders", "Create Sales Order", or analytical apps showing live KPIs. The Fiori apps reference library lists each app and how to enable it (OData service, role, catalog).
A custom app, conceptually
" CDS view (backend) exposed as OData
@OData.publish: true
define view entity Z_C_OpenPO as select from I_PurchaseOrderItemAPI01 { ... }
" UI5/Fiori Elements app binds to the OData service
" list report + object page generated from annotationsWhat it teaches
The example shows the modern stack: a CDS view exposed as OData, consumed by a Fiori Elements app with little hand-coding. Prefer standard apps, then Fiori Elements on CDS, before freestyle UI5, keeping close to standard and clean-core.
Common pitfalls
- Freestyle builds where Fiori Elements fits.
- Inactive OData service breaking the app.
- Missing role/catalog, no tile.