Show TOC

Analytical Applications Based on APFLocate this document in the navigation structure

APF supports a sophisticated user interaction paradigm that you can apply to your own APF-based analytical Web application. Users can perform a step-by-step analysis of KPIs by looking at them from different perspectives. For example, they can compare a KPI across different countries or customers, and they can examine tendencies over time. To cover these aspects, you can define different analysis steps that the users can then choose from in an analysis step gallery. Analysis steps consist of data that is depicted on the UI in various types of representations, such as charts or tables.

In each analysis step, the users can select data to filter the information provided in subsequent steps. By combining different analysis steps and applying filters, they interactively create their own flexible analysis paths.

To get an overview of how an APF-based app looks and how to use it, watch the following videos:



UI Overview

Creating an Analysis Path

Further Options for Analysis Paths

Filtering Data in Analysis Paths

Configured APF-Based Applications

A number of APF-based applications are available that are already configured and ready to be used.

APF-based applications that are shipped by SAP consist of a Business Server Page (BSP) application along with an app descriptor, the manifest.json file. This manifest.json file refers to the analytical content configuration file, also in JSON format. If you want to run an APF-based application without making any changes to it, the configuration can be read directly from the JSON files. You don't need the APF Configuration Modeler to use this scenario.

When you import the JSON file of a shipped application into the APF Configuration Modeler to enhance the application, the configuration is written into a table. For more information , see Import and Enhancing an APF-Based Application.

For information about shipped APF-based apps, see the documentation of the individual apps.


APF-based Web applications run in a Web browser and communicate with a server using OData service requests.

The architecture is depicted in the following figure: