SAP Fiori Elements: List Report vs Object Page Explained

Fiori Elements ships with a small set of floorplans, and picking the right one — or the right combination — is the first design decision for any new app.

List Report

The List Report is a searchable, filterable table: think "find the record I need out of thousands." It's driven almost entirely by @UI.lineItem (columns) and @UI.selectionField (filter bar fields).

@UI.lineItem: [{ position: 10 }]
@UI.selectionField: [{ position: 10 }]
CustomerId,

@UI.lineItem: [{ position: 20 }]
OrderDate,

@UI.lineItem: [{ position: 30 }]
NetAmount,

Good List Report design means picking a small number of columns that let a user recognize the right row without opening it — resist the urge to show every field as a column just because it exists.

Object Page

The Object Page is the detail view for a single record: think "now show me (and let me edit) everything about this one thing." It's organized into facets, driven by @UI.fieldGroup, @UI.identification, and @UI.facet.

@UI.facet: [
  { id: 'GeneralInfo', type: #IDENTIFICATION_REFERENCE, label: 'General Information', position: 10 },
  { id: 'Items', type: #LINEITEM_REFERENCE, targetElement: '_Items', label: 'Items', position: 20 }
]

@UI.identification: [{ position: 10 }]
Description,

@UI.identification: [{ position: 20 }]
OverallStatus,

A facet of type #LINEITEM_REFERENCE targeting an association (_Items above) is how you get a table of related child records embedded in the Object Page — the same @UI.lineItem annotation mechanism as the List Report, just applied to the child entity.

How They Connect

By default, clicking a row in the List Report navigates to the Object Page for that record — this wiring is automatic once both views exist and the service binding includes both. You don't configure the navigation manually; it comes from the semantic key and the standard List Report → Object Page pattern built into Fiori Elements.

When You Only Need One

• Object Page only — apps with a single, well-known record (e.g. "my profile," a singleton configuration record) skip the List Report and jump straight to a fixed Object Page.
• List Report only — read-only reference/reporting apps sometimes stop at the List Report with no drill-down, especially with an Analytical variant showing charts instead of row detail.

Common Mistake: Designing the Object Page Like a Form Dump

The most common Fiori Elements complaint from end users is an Object Page with 40 fields in one facet and no grouping. Use multiple @UI.fieldGroup entries to cluster related fields, and multiple facets to separate concerns (general info vs. items vs. attachments) — the framework supports this natively, it just requires deliberate annotation design rather than accepting the default single-group layout.

Check the Fiori Elements Feature Matrix for the full annotation-to-feature mapping across both floorplans, and the CDS Annotation Reference for exact syntax of @UI.facet and @UI.fieldGroup.