Explaining Templates for Fiori Elements

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Identify the different templates of SAP Fiori Elements

Templates of SAP Fiori Elements

The current templates for SAP Fiori elements are as follows:

  • List Report
  • Object Page
  • Analytic List Page
  • Overview Page
  • Worklist Page

Let's look at each of these templates more closely.

List Report

With a list report, users can view and work with a large set of items. This floorplan offers powerful features for finding and acting on relevant items. It is often used as an entry point for navigating to the item details, which are usually shown on an Object Page .

Use the list report floorplan if:

  • Users need to find and act on relevant items within a large set of items by searching, filtering, sorting, and grouping.
  • You want to let users display the whole dataset using different visualizations (for example, as a table or as a chart), but no interactions are required between these visualizations. An example use case might be reporting.
  • Users need to work with multiple views of the same content, for example on items that are "Open", "In Process", or "Completed". You want to let users switch views using tabs, segmented buttons, or a select control.
  • Drilldown is rarely or never used, or is only available via navigation to another page, and not as free or flexible drilldown within the page itself.
  • Users work on different kinds of items.
Do not use the list page floorplan if:Use instead:
  • Users need to see or edit one item with all its details.
Object page floorplan
  • Users need to work through a comparably small set of items,.
Worklist floorplan
  • Users need to extract knowledge or insights from data, either to better understand the current situation, or to identify the root cause for a certain value.
  • Charts are not only used for visualization. Users need to switch between integrated chart and table views (hybrid view).
  • Users need to see the impact of their action on a KPI.
  • Users need to see not only the result, but also the impact of their filter settings directly in a chart representation
Analytical list page

From that, we can use the List Report as replacement of ALV in SAP GUI. Lots of ABAP queries created by SQVI and ALV based ABAP reports can be replaced by List Report.

Object Page

The object page floorplan is used to display and categorize all relevant information about an object. Categorized content can be accessed quickly using anchor or tab navigation, and users can switch from display to edit mode to change the content. To create a new object, users can switch to create mode.

The object page floorplan comes with a flexible, responsive layout and a dynamic page header that can be adapted to display simple and complex business objects. This allows you to adjust the layout to a wide range of use cases.

Use the object page floorplan if:

  • Users need to display, create, or edit an object.
  • Users need to get an overview of an object and interact with different parts of the object.
Do not use the object page floorplan if:Use instead:
  • Users need to edit several items at the same time.
  • Users need to find relevant items without knowing the exact item details.
List report floorplan
  • Users need to be guided through a series of steps when a new object is created.
  • The creation process for a new object is not linear, but can have different paths, depending on the information selected.
Wizard floorplan
  • Users need a way to analyze data step by step from different perspectives. They need to drill down to investigate a root cause and act on transactional content within one page.
  • Users need to interact with interdependent chart and table views (rather than using charts for visualization only).
Analytical list page

Overview Page

The overview page (OVP) is a data-driven SAP Fiori app type and floorplan that provides all the information a user needs in a single page, based on the user’s specific domain or role. It allows the user to focus on the most important tasks, and view, filter, and react to information quickly.

Each task or topic is represented by a card (or content container). The overview page acts as a UI framework for organizing multiple cards on a single page.

The overview page is based on SAP Fiori elements technology, and uses annotated views of app data, meaning that the app content can be tailored to the domain or role. Different types of card allow you to visualize information in an attractive and efficient way.

An Overview page is a data-driven SAP Fiori application built using SAPUI5 technology, OData services, and annotations for organizing large amounts of information.

Use the overview page if:

  • You want to provide an entry-level view of content related to a specific domain or role.
  • Users needs to filter and react to information from at least two different applications to complete their role-specific tasks.
  • You want to offer different information formats (such as charts, lists, and tables) on a single page.
  • You plan to have at least three cards. These cards should not all be of the same type
Do not use the overview page floorplan if:Use instead:
  • A high-level or birds-eye view of application content is sufficient
 
  • You just want the user to launch an application
SAP Fiori launchpad home page
  • You want to show information about one object only.
  • You just represent one application and less than three cards.
Object page floorplan

Analytical List Page

The analytical list page (ALP) offers a unique way to analyze data step by step from different perspectives, to investigate a root cause through drilldown, and to act on transactional content. All this can be done seamlessly within one page. The purpose of the analytical list page is to identify interesting areas within datasets or significant single instances using data visualization and business intelligence.

Visualizations help users to recognize facts and situations, and reduce the number of interaction steps needed to gain insights or to identify significant single instances. Chart visualization increases the joy of use, and enables users to spot relevant data more quickly.

The main target group are users who work on transactional content. They benefit from fully transparent business object data and direct access to business actions. In addition, they have access to analytical views and functions without having to switch between systems. These include KPIs, a visual filter where filter values are enriched by measures and visualizations, and a combined table/chart view with drill-in capabilities (hybrid view). Users can interact with the chart to dig deep into the data. The visualization enables them to identify spikes, deviations and abnormalities more quickly, and to take appropriate action right away.

Use the analytical list page if:

  • Users need to extract key information to understand the current situation or identify a root cause. The way the data is presented is crucial for giving them the insights they need to take the right action.
  • Users need a way to analyze data step by step from different perspectives, investigate a root cause through drilldown, and act on transactional content within one page.
  • In addition to the filtered dataset, users need to see the impact of their filter settings in a chart (visual filter).
  • Users need to switch between integrated chart and table views (hybrid view).
  • Users need to see the impact of their action on a global key performance indicator (KPI).
  • Users need to find and act on relevant items out of a large set of items by searching, filtering, sorting, grouping, drilling down, and slicing and dicing
Do not use the analytical list page floorplan if:Use instead:
  • Drilldown is rarely used, not used at all, or is only needed after navigating to another page, rather than as free or flexible drilldown within the page itself..
  • Users need different visualizations for the entire dataset (for example, as a table or chart), but don’t need to work with both visualizations on the same page (for example, in a reporting scenario).
  • Users need to find and act on relevant items from within a large set of items by searching, filtering, sorting, and grouping, without using drilldown or "slice and dice".
  • Users need to work with multiple views of the same content, for example on items that are "Open", "In Process", or "Completed". They want to be able to switch views using tabs, segmented buttons, or a select control. In this case, consider using a list report.
  • Users have a trivial use case that does require the use of a chart, but that do not involve identifying a root cause, analyzing data, or drilldown.
List report floorplan
  • Users need to find a specific item, and the item or an identifying data point is known to the user (such as a code). In this case, use the initial page floorplan.
  • The creation process for a new object is not linear, but can have different paths, depending on the information selected.
Initial Page floorplan
  • Users need to work through a comparably small set of items, one by one.
  • Users need to interact with interdependent chart and table views (rather than using charts for visualization only).
Worklist floorplan

Worklist Page

A worklist displays a collection of items a user needs to process. Working through the list usually involves reviewing details of the items and taking action. In most cases, the user has to either complete a work item or delegate it.

The worklist is a versatile floorplan that offers three main variants: a simple worklist (plain page with a table), a worklist with tabs, and a worklist with one or more KPI tags. These variants are based on different user needs and use cases.

Use the worklist floorplan if:

  • Users have numerous work items and need to decide which ones to process first.
  • You want to give users a direct entry point for taking action on work items.
  • Users need to work with multiple views of the same content (for example, items that are "Open", "In Process", or "Completed"). You want to offer tabs for switching between views.
Do not use the worklist page floorplan if:Use instead:
  • The items you are showing are not work items.
 
  • You want to show large item lists, or combine different data visualizations (charts or tables).
  • Users need to find and act on relevant items from within a large set of items by searching, filtering, sorting, and grouping.
List report floorplan

Save progress to your learning plan by logging in or creating an account