Lesson 3 of 6
Working in a list report
9 min
A large share of Fiori apps follow the same pattern, called a list report. Manage Sales Orders, Manage Purchase Orders, Manage Customer Line Items and many others look and behave alike: a filter bar at the top, a results table below, and a details page when you select a row. Learn one well and you can use hundreds.
Anatomy of a list report
- View selector (top left): the name of the current view, such as "Standard." Views are SAP’s name for saved variants.
- Filter bar: fields such as Sales Organization, Sold-to Party, Created On. Adapt Filters adds or removes fields.
- Go: runs the selection. Many apps do not load data until you select it.
- Table toolbar: actions such as Create, plus settings for columns, sort and group, and Export to Spreadsheet.
- Rows: select a row to open its object page with the full details.
A worked example
Dana wants every open order for sales organization 1710, distribution channel 10, created this month, sorted by requested delivery date. In Manage Sales Orders she does the following.
- Set filtersSales Organization 1710, Distribution Channel 10, Created On this month.
- Select GoThe table fills with matching orders.
- Adjust the tableIn table settings, add the Requested Delivery Date column and sort ascending.
- Save as a viewName it "1710 open orders – this month." Choose whether it is default.
- Export if neededExport to Spreadsheet for a one-off analysis.
Views (variants)
A view stores your filter values and table layout so you can apply them again with one click. It does not store the data itself; each time you apply it, the app reads the current data. Open the view selector and choose Save As to create one. The Save View dialog offers a few options worth knowing:
| Option | What it does | When to use it |
|---|---|---|
| Set as Default | This view opens automatically when you start the app | For the selection you use most days |
| Public | Everyone who can use the app can choose the view | For a shared team or test view; check your company’s naming rules first |
| Apply Automatically | The selection runs immediately, without selecting Go | Only when the selection is small and fast |
Options in the Save View dialog of a typical list report
Manage Views in the same menu lets you rename, delete, mark favorites, and change your default. You can only change views you created; key users can manage public views. If you change filters without saving, the view name shows an asterisk to warn you that what you see differs from what is saved.
Why views matter for testing
A shared, public view is one of the simplest ways to make a test repeatable. If the test step says "Open Manage Sales Orders with view UAT – 1710 fleet orders," every tester starts from the same selection, sees the same columns, and checks the same values. It also helps daily work after go-live: the same view used in testing becomes the view users rely on.
What would you do?
Contoso’s UAT lead wants all five sales testers to check the same set of fleet orders every day of the test cycle. What is the best way to set this up in Manage Sales Orders?
- List reports share one pattern: view selector, filter bar, Go, table, object page.
- A view stores filters and layout, never the data; Save As creates one, Manage Views maintains them.
- Set as Default, Public and Apply Automatically control how a view behaves.
- Shared public views make tests repeatable; record view name, filters, result count and document numbers.
Check your understanding · not graded
Lesson check
1. What does a saved view in a list report store?
2. Which Save View option makes a view visible to everyone who uses the app?
3. What does an asterisk next to the view name mean?