Show TOC

Creating Navigation TargetsLocate this document in the navigation structure

Users can use the Open In… button in the footer of an APF-based runtime application to navigate to other applications. The context of the current analysis path including start filters and other filters such as selections made in the charts up to the active analysis step are handed over to the other application.

When the user navigates back to the APF-based application, the analysis path is reloaded in exactly the same status as it was when navigating to the other application, that is, all analysis steps and all selections made are retained.

The following video shows an introduction to navigation targets and how to configure them:

The following types of navigation targets exist:

  • Navigation targets that are relevant for all analysis steps

    Choose this type if the navigation target is always available no matter which analysis steps are added to the analysis path.

  • Step-specific navigation targets

    Choose this type if the navigation target is relevant only in the context of a specific dimension or selection. For example, navigating to a customer fact sheet is useful only when a customer has been selected. A step-specific navigation target is displayed in the Open In… dialog only if the step to which it is assigned is the active one.

Step-specific navigation targets can be assigned to multiple analysis steps. To assign a previously created navigation target to an analysis step, proceed in one of the following ways:

  • Select the navigation target and add the analysis step in the Step Assignments field.

  • Select the analysis step and add the navigation target in the Navigation Target Assignment section in the Step-Specific field.

You can define multiple navigation targets for each configuration. To create a navigation target, click Start of the navigation path Add Next navigation step New Navigation Target End of the navigation path and enter the following:

Basic Data



Semantic Object

Semantic object as defined in the corresponding target mapping configured in the Fiori launchpad designer.


As soon as you enter a semantic object, the value help for the action is filled with all actions that are available for this target mapping and that you are authorized for. The Action field is prefilled with the first action in this list.

Navigation Target Title

Taken over from the description in the target mapping.

Assignment to Steps



Assignment Type

Choose one of the following:

  • Assign to All Steps

    The navigation target is available in all analysis steps at runtime.

  • Assign to Specific Steps

    The navigation target is available only in the specified analysis steps.

Step Assignments

If you are creating a step-specific navigation target, assign one or more analysis steps to it. If you leave this field empty, you can still save the navigation target and assign it to steps at a later point in time.

Context Mapping

If a certain property is required for launching the navigation target, you can define a request for it. This ensures that the property is available as a context when navigating to this navigation target at runtime. The result of the context mapping request is a list of values for the specified property. If you have selected more than one property, the result is a list of value tuples. The results are added to the existing context that is handed over to the navigation target.




Path to the OData service root. If you use ABAP CDS views or BW OData queries, select a service from the value help. If you use calculation views, you must enter the service manually.

Entity Set

Entity set that corresponds to the SAP HANA view.

Mapped Properties

Select one or more properties from the list of properties that are available for the selected entity set.

Filter Formats

APF hands over the cumulative filter of the current analysis path using the CrossApplicationNavigation service of the unified shell.

The app state contains two different properties that hand over the filter in two different formats:

  • Property sapApfCumulativeFilter:

    Filter object in the format of sap.ui.model.Filter

  • Property selectionVariant:

    Filter object in selectOption format

    If the filter is too complex to transform it into a selectionVariant, an empty selectionVariant containing a technical error text is returned.


The type information of a property is included in none of the filters. If the consuming application requires the type information, it can be derived from the metadata.

The consuming application can read the app state as follows:

Source Code
sap.ushell.Container.getService("CrossApplicationNavigation").getAppState(oInject.instances.component, crossAppStateKey).done(function(appContainer) {
                              containerData = appContainer.getData();
                              if (containerData && containerData.sapApfCumulativeFilter) {
// your code

At runtime, the navigation targets are displayed in the Open In… menu. Step-specific navigation targets appear at the top of the list. Navigation targets that are relevant for all analysis steps appear at the bottom of the list so that this part of the Open In… menu is stable for all steps.

Navigation targets are displayed in the same order as they appear in the tree structure. You can change the order of the navigation targets by moving them up or down the tree structure using the arrow icons.

The list of navigation targets in the Open In… menu can be different from user to user. Whether a navigation target is visible for a user depends on the following:

  • The user is authorized for the target mapping of the navigation target. This is the case if the user has a role to which the catalog is assigned which contains the target mapping.

  • The navigation target supports the form factor the user is currently using: desktop, tablet, or smartphone. This is also configured in the target mapping.