Explaining Templates for Fiori Elements

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.

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.

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.

The overview page (OVP) is a data-driven SAP Fiori app type and floorplan that provides all of 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 cards 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 need 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.

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 of 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 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 users to identify spikes, deviations, and abnormalities faster, and allows them 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

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.