Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

SAP Fiori is SAP’s approach to business application design. Fiori elements uses annotations, or descriptive metadata, to decide how fields, tables and actions should appear.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Fiori is SAP’s design approach for business applications. SAPUI5 is a user-interface toolkit, and Fiori elements uses metadata to generate common application patterns.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for Fiori elements annotations: Presentation metadata is not backend validation
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

Fiori elements metadata and ABAP CDS UI annotations; term support and responsive behavior depend on OData version, floorplan, table type and UI5/backend release.

Primary documentation reviewed on 14 November 2026 using official indexed excerpts. Documentation review only; authored examples were not compiled or executed in an SAP system.

A MANUFACTURING EXAMPLE

Separate the factory screen from backend rules

Presentation and validation differ

Field: Requested quantity. UI annotation: Displayed prominently. Input example: -5. Backend validation: Separate rule
What to notice: Making a field visible or important does not by itself enforce a business validation.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Field
Requested quantity
UI annotation
Displayed prominently
Input example
-5
Backend validation
Separate rule

A REAL SCREEN TO RECOGNIZE

SAP’s Fiori elements feature showcase. The filter bar, table columns and row actions are distinct UI regions. Compare the region discussed in this guide with the corresponding service and metadata.

SAP’s Fiori elements feature showcase. The filter bar, table columns and row actions are distinct UI regions. Compare the region discussed in this guide with the corresponding service and metadata.

View the original SAP example ↗ · License

© 2021 SAP SE or an SAP affiliate company and project contributors. Apache-2.0. Reproduced unchanged for educational commentary. This is a source example, not a capture of your system.
Words you’ll meet in this guide
Binding
A connection between a screen control and data.
Metadata
Information describing data or how it should be used.
Service
A software interface that provides data or operations.
Backend
The system or service that provides business processing behind the interface.
ABAP
SAP’s programming language for business applications.
CDS
Core Data Services: reusable definitions of business data and relationships.
RAP
ABAP RESTful Application Programming Model: a way to build business objects and services.
OData
A standard for reading and updating data through a web API.
Fiori
SAP’s approach to business application design.
API
A defined interface through which programs exchange data or request actions.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Service fields → UI annotations → Rendered application. Conceptual diagram for Fiori elements annotations: Presentation metadata is not backend validation.
Apply the idea: A manufacturer configures the presentation of an operational Fiori elements application while its business validity rules belong in the backend contract.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Separate the factory screen from backend rules

    A manufacturer configures the presentation of an operational Fiori elements application while its business validity rules belong in the backend contract.

  2. Annotations describe the experience; the service owns business acceptance

    Fiori elements reads service metadata and annotations to build fields, tables, object pages and actions.

  3. Scope and prerequisites

    The example uses ABAP CDS UI annotations consumed by Fiori elements.

  4. Understand the metadata path before editing a screen

    A property originates in the exposed data/service model.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.